Nabble - Grok

Re: Grok application with Eclipse 3.2

2009-11-27T03:07:11Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martijn Faassen wrote:
> Hey,
>
> Hector Blanco wrote:
>> Does anyone know a good place where I can find an explanation in how to
>> use Eclipse to develop a Grok/Zope application?
>
> Looks like nobody knows of such a place! Have you made any progress?
>

pydev (http://pydev.org/) should have everything you need.

Regards
Michael

- --
http://blog.d2m.at
http://planetzope.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksPst4ACgkQl0uAvQJUKVbYqgCfRC1u1bP62pyQCMmOaOqTGnak
pocAnA/fuhrMcCvQlfLjGYk/6U6iw1jS
=1WHV
-----END PGP SIGNATURE-----

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: url() method on JSON component

2009-11-27T03:00:43Z

Jan-Wijbrand Kolman wrote:
> Now, what do I call these mixins?

I chose "ViewSupport". Is has been merged just now with the grok trunk
(and grokcore.view-1.13 and grokcore.view trunk). grokcore.view-1.13a2
has been released.

JSON, REST and XMLRPC components now gained url() and application_url()
methods and response and body properties.

regards,
jw

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Grok application with Eclipse 3.2

2009-11-27T02:40:33Z

Hey,

Hector Blanco wrote:
> Does anyone know a good place where I can find an explanation in how to
> use Eclipse to develop a Grok/Zope application?

Looks like nobody knows of such a place! Have you made any progress?

I was wondering whether some people who have experience developing with
another IDE such as WingIDE might have any ideas..

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: a grok.getApplication() implementation

2009-11-27T02:38:30Z

Christian Theune wrote:

> On 11/27/2009 02:22 AM, Kevin Teague wrote:
>> The grok.getApplication() has been discussed/proposed a few times in
>> the past, e.g.
>>
>> http://article.gmane.org/gmane.comp.web.zope.grok.devel/5521
>>
>> I'd really like this function available in Grok, so I put together an
>> implementation, and some tests for it, available on a branch:
>>
>> http://svn.zope.org/grok/branches/kteague-getapp/
>>
>> The implementation, in grok.utils, just looks like this:
>>
>> def getApplication():
>> """Get the application."""
>> site = grok.getSite()
>> if grok.interfaces.IApplication.providedBy(site):
>> return site
>> else:
>> # another sub-site is within the application, walk up
>> # the tree until we get to the application
>> parent = site.__parent__
>> while not grok.interfaces.IApplication.providedBy(parent):
>> parent = parent.__parent__
>> return parent
>>
>> Not sure if there is a better way to do this?
>
> There already is an implementation that acquires the application from a
> view to return its URL.
>
> In my projects I tend to complement that implementation with the same
> algorithm that just returns the object instead of getting the URL.

I think Kevin's looks like a reasonable implementation and it mirrors
getSite(), so I'm +1.

I don't find myself using application_url for some reason.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Migrating catalog indexes

2009-11-27T01:33:29Z

This looks very interesting! It addresses my biggest gripe with Grok
to date.

But how do you set the grok.context of the index? When defining a
grok.Index one can have the same catalog name for different contexts.
From your code example I don't see how I specify this. This is what a
typical catalog would look like for me:

class SiteSearchCatalog(grok.Indexes):
grok.site(BoardsportSource)
grok.context(IFeedItemSupport)
grok.name('feed_index')

tags = grok.index.Set()
feed_types = grok.index.Set(attribute='supportedFeedTypes')
search = grok.index.Text(attribute="fullTextSearch"

from boardsportsource.interfaces import IPublishDate
class SitePublishCatalog(grok.Indexes):
grok.site(BoardsportSource)
grok.context(IPublishDate)
grok.name('feed_index')

publish_datetime = Value(attribute='publish_datetime')

Mvh Sebastian

27 nov 2009 kl. 00.24 skrev Simon Jagoe:

> 2009/11/26 Kevin Teague <kevin@...>:
>> If you've got an Indexes, such as:
>>
>> class MyIndexes(grok.Indexes):
>> grok.site(MyApp)
>> grok.context(gsc.haystack.interfaces.IContent)
>>
>> created = grok.index.Field()
>>
>> And it gets grokked, then a catalog and a field index will be
>> created.
>> But then if you add a second field index:
>>
>> class MyIndexes(grok.Indexes):
>> grok.site(MyApp)
>> grok.context(gsc.haystack.interfaces.IContent)
>>
>> created = grok.index.Field()
>> modified = grok.index.Field()
>>
>> This index doesn't get created. Soooo ... what's the best way to
>> migrate a catalog when the indexes are updated after the initial
>> creation. Anyone got any tips here?
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev@...
>> https://mail.zope.org/mailman/listinfo/grok-dev
>>
>
> Hi Kevin,
>
> I may not be the best person to answer this as I was wondering the
> same thing recently. I decided to poke around in the debug console to
> see if I could come up with an answer.
>
> I am using the debug prompt (./bin/app-debug) of the grok environment
> for this experiment. I will write all of this with the assumption that
> we have this grok.Indexes subclass:
>
> class ResultIndexes(grok.Indexes):
> grok.site(App)
> grok.context(IResult)
> grok.name('my_catalog')
> name = index.Field()
> date = index.Field(attribute='get_date')
> is_verified = index.Field()
>
> and we want to end up with this:
>
> class ResultIndexes(grok.Indexes):
> grok.site(App)
> grok.context(IResult)
> grok.name('my_catalog')
> name = index.Field()
> date = index.Field(attribute='get_date')
> is_verified = index.Field()
> did_fall = index.Field()
>
> Start the app debug prompt:
>
> $ ./bin/app-debug
> Welcome to the interactive debug prompt.
> The 'root' variable contains the ZODB root folder.
>
> The 'app' variable contains the Debugger, 'app.publish(path)'
> simulates a request.
>
> # Assuming you have an app called 'app' instantiated already:
>>>> app = root[u'app']
>>>> local_site_manager = app.getSiteManager()
>
> # The name here is the value that was provided in the grok.name()
> # directive on the class. I guess empty if you did not name your
> # catalog.
>>>> from zope.app.catalog.interfaces import ICatalog
>>>> cat = local_site_manager.getUtility(ICatalog, name='my_catalog')
>
> # The catalog is a container with keys of the fields you declared in
> # your grok.Indexes subclass
>>>> print [f for f in c.keys()]
> [u'date', u'is_verified', u'name']
>
> # To add a did_fall index, assuming did_fall is a schema.Bool declared
> # on my IResult interface
>>>> cat[u'did_fall'] = FieldIndex(field_name=u'did_fall')
>
> # Not sure if this is required
>>>> import transaction
>>>> transaction.commit()
>
> # Now update the index to include the new value
>>>> cat.updateIndexes()
>
> Then to test that the catalog had updated, I wrote a unit test (I
> couldn't seem to use hurry.query in that debug prompt).
>
> Adding a view with the following render method allowed me to test the
> updated catalog. The result from this was [u'simon'], as expected. The
> data to be indexed was present in the application before updating the
> index.
>
> def render(self):
> from hurry.query.query import Query, Eq
> return str([r.__name__ for r in Query().searchResults(
> Eq(('slalom_result_catalog', 'did_fall'), True))])
>
> Hopefully this is coherent and useful, I wrote it up as I was
> experimenting with this. Maybe somebody can throw in some more useful
> comments (and perhaps how to turn this into a script that can be run
> stand-alone would be useful too).
>
> Regards,
> Simon
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Values from another document before rendering

2009-11-27T00:48:56Z

Hi Sebastian,

Thank you so much for such a quick response and for including an actual
code example!

I am on a 3 day conference at the moment, but will try this out as soon as
I can next week.

Kathy

Sebastian Ware wrote:
> This is what I do. I have a field defined in an interface:
>
> gallery_id = schema.Choice(title=u"Gallery", vocabulary=u"Published
NewProductGalleries")
>
> The vocabulary looks like this (it is a bit dirty, but it might help you
in the right direction):

>
>
> import grok
> from zope import schema
> from zope.schema.vocabulary import SimpleVocabulary
> from boardsportsource import interfaces
> from boardsportsource import workflow
> from hurry import query
>
> class NewProductGalleriesSource(grok.GlobalUtility):
> grok.implements(schema.interfaces.IVocabularyFactory)
> grok.name('Published NewProductGalleries')
> def __call__(self, context):
> terms = self.get_published_galleries(context)
> return SimpleVocabulary(terms)
>
> def get_published_galleries(self, context):
> hasItem = []
> if hasattr(context, 'gallery_id') and context.gallery_id is not

None:
> # I allways need to have the current value in my vocabulary
> # or choice widgets won't render.
> hasItem.append(context.gallery_id)
>
> # I use hurry.query to find the objects I want to use in
> # my vocabulary.
> theQuery = query.Eq(('workflow_catalog', 'workflow_state'),
workflow.PUBLISHED)
> theQuery = theQuery & query.Eq(('workflow_catalog',
'object_type'), 'new_product_gallery')
> dictResult = query.query.Query().searchResults(theQuery)
>
> theList = []
> for item in dictResult:
> theObj = interfaces.INewProductGallery(item)
> theList.append(SimpleVocabulary.createTerm(theObj.__name__,
theObj.__name__, '%s (%s)' % (theObj.title, 'default')))
> if theObj.__name__ in hasItem:
> hasItem.remove(theObj.__name__)
>
> for key in hasItem:
> # If the current value wasn't found in the search I add it here
> # with an appropriate message.
> if grok.getSite()['default'].has_key(key):
> theObj =
interfaces.IImageOfTheDayGallery(grok.getSite()['default'][key])
> theList.append(SimpleVocabulary.createTerm(key, key, '%s
(not published!)' % theObj.title))
> else:
> theList.append(SimpleVocabulary.createTerm(key, key, '%s
has been removed!' % key))

> return theList
>
> Mvh Sebastian
>
>
> 26 nov 2009 kl. 11.00 skrev Kathy Manwaring:
>
>> Firstly, thank you very much for your quick responses to my last query -
>> they put me on the right track. Now, I have another question...
>>
>> I have a class that needs to get values from another entry when it is
>> created or edited. So, when creating a Person, the list of values that I
>> can choose from for the type of Person are values that are editable on
>> another entry.
>>
>> It LOOKS like I should be able to use a dynamically calculated
>> SimpleVocabulary, but I can't get it to work - I think I need to use
>> self.context on the interface definition of the schema field, but self is
>> not defined.
>>
>> Alternatively, can I do it in setupWidgets before rendering? (Can't see
>> enough information about setupWidgets to answer the question).
>>
>> Any help would be appreciated.
>>
>> Kathy
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev@...
>> https://mail.zope.org/mailman/listinfo/grok-dev

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: a grok.getApplication() implementation

2009-11-26T22:18:03Z

On 11/27/2009 02:22 AM, Kevin Teague wrote:

> The grok.getApplication() has been discussed/proposed a few times in
> the past, e.g.
>
> http://article.gmane.org/gmane.comp.web.zope.grok.devel/5521
>
> I'd really like this function available in Grok, so I put together an
> implementation, and some tests for it, available on a branch:
>
> http://svn.zope.org/grok/branches/kteague-getapp/
>
> The implementation, in grok.utils, just looks like this:
>
> def getApplication():
> """Get the application."""
> site = grok.getSite()
> if grok.interfaces.IApplication.providedBy(site):
> return site
> else:
> # another sub-site is within the application, walk up
> # the tree until we get to the application
> parent = site.__parent__
> while not grok.interfaces.IApplication.providedBy(parent):
> parent = parent.__parent__
> return parent
>
> Not sure if there is a better way to do this?

There already is an implementation that acquires the application from a
view to return its URL.

In my projects I tend to complement that implementation with the same
algorithm that just returns the object instead of getting the URL.

Christian

--
Christian Theune · ct@...
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

a grok.getApplication() implementation

2009-11-26T17:22:02Z

The grok.getApplication() has been discussed/proposed a few times in
the past, e.g.

http://article.gmane.org/gmane.comp.web.zope.grok.devel/5521

I'd really like this function available in Grok, so I put together an
implementation, and some tests for it, available on a branch:

http://svn.zope.org/grok/branches/kteague-getapp/

The implementation, in grok.utils, just looks like this:

def getApplication():
"""Get the application."""
site = grok.getSite()
if grok.interfaces.IApplication.providedBy(site):
return site
else:
# another sub-site is within the application, walk up
# the tree until we get to the application
parent = site.__parent__
while not grok.interfaces.IApplication.providedBy(parent):
parent = parent.__parent__
return parent

Not sure if there is a better way to do this?

The tests are in src/grok/ftests/application/, they could maybe be
improved as my Site() zen is also not super great. Although this
feature is relatively simple, so perhaps it's good enough to be merged
to trunk?

(docs need to be updated to, I can do this post-merge)
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[off-topic] Who is grok?

2009-11-26T16:32:50Z

I've been on a low-carbohydrate diet recently, and came across this
health and lifestyle web site which promotes a "paleolithic
lifestyle":

http://www.marksdailyapple.com

So aside from being an interesting site for anyone who wants to inform
their lifestyle choices from the life of the cavemen, I found it even
more interesting that they've got a caveman mascot, and his name is
also Grok!

http://www.marksdailyapple.com/about-2/who-is-grok/

Their Grok is certainly a lot more fit than ours, but I think we've
got the much better logo. Their Grok just has a puny spear, we've got
a full-size club. :P
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Migrating catalog indexes

2009-11-26T15:26:42Z

> def render(self):
> from hurry.query.query import Query, Eq
> return str([r.__name__ for r in Query().searchResults(
> Eq(('slalom_result_catalog', 'did_fall'), True))])

Sorry that should have been edited to the catalog name 'my_catalog'.
I didn't check over it thoroughly enough before sending. Render method
would be:

def render(self):
from hurry.query.query import Query, Eq
return str([r.__name__ for r in Query().searchResults(
Eq(('my_catalog', 'did_fall'), True))])
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Migrating catalog indexes

2009-11-26T15:24:24Z

2009/11/26 Kevin Teague <kevin@...>:

> If you've got an Indexes, such as:
>
> class MyIndexes(grok.Indexes):
> grok.site(MyApp)
> grok.context(gsc.haystack.interfaces.IContent)
>
> created = grok.index.Field()
>
> And it gets grokked, then a catalog and a field index will be created.
> But then if you add a second field index:
>
> class MyIndexes(grok.Indexes):
> grok.site(MyApp)
> grok.context(gsc.haystack.interfaces.IContent)
>
> created = grok.index.Field()
> modified = grok.index.Field()
>
> This index doesn't get created. Soooo ... what's the best way to
> migrate a catalog when the indexes are updated after the initial
> creation. Anyone got any tips here?
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

Hi Kevin,

I may not be the best person to answer this as I was wondering the
same thing recently. I decided to poke around in the debug console to
see if I could come up with an answer.

I am using the debug prompt (./bin/app-debug) of the grok environment
for this experiment. I will write all of this with the assumption that
we have this grok.Indexes subclass:

class ResultIndexes(grok.Indexes):
grok.site(App)
grok.context(IResult)
grok.name('my_catalog')
name = index.Field()
date = index.Field(attribute='get_date')
is_verified = index.Field()

and we want to end up with this:

class ResultIndexes(grok.Indexes):
grok.site(App)
grok.context(IResult)
grok.name('my_catalog')
name = index.Field()
date = index.Field(attribute='get_date')
is_verified = index.Field()
did_fall = index.Field()

Start the app debug prompt:

$ ./bin/app-debug
Welcome to the interactive debug prompt.
The 'root' variable contains the ZODB root folder.

The 'app' variable contains the Debugger, 'app.publish(path)'
simulates a request.

# Assuming you have an app called 'app' instantiated already:
>>> app = root[u'app']
>>> local_site_manager = app.getSiteManager()

# The name here is the value that was provided in the grok.name()
# directive on the class. I guess empty if you did not name your
# catalog.
>>> from zope.app.catalog.interfaces import ICatalog
>>> cat = local_site_manager.getUtility(ICatalog, name='my_catalog')

# The catalog is a container with keys of the fields you declared in
# your grok.Indexes subclass
>>> print [f for f in c.keys()]
[u'date', u'is_verified', u'name']

# To add a did_fall index, assuming did_fall is a schema.Bool declared
# on my IResult interface
>>> cat[u'did_fall'] = FieldIndex(field_name=u'did_fall')

# Not sure if this is required
>>> import transaction
>>> transaction.commit()

# Now update the index to include the new value
>>> cat.updateIndexes()

Then to test that the catalog had updated, I wrote a unit test (I
couldn't seem to use hurry.query in that debug prompt).

Adding a view with the following render method allowed me to test the
updated catalog. The result from this was [u'simon'], as expected. The
data to be indexed was present in the application before updating the
index.

def render(self):
from hurry.query.query import Query, Eq
return str([r.__name__ for r in Query().searchResults(
Eq(('slalom_result_catalog', 'did_fall'), True))])

Hopefully this is coherent and useful, I wrote it up as I was
experimenting with this. Maybe somebody can throw in some more useful
comments (and perhaps how to turn this into a script that can be run
stand-alone would be useful too).

Regards,
Simon
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Migrating catalog indexes

2009-11-26T14:11:31Z

If you've got an Indexes, such as:

class MyIndexes(grok.Indexes):
grok.site(MyApp)
grok.context(gsc.haystack.interfaces.IContent)

created = grok.index.Field()

And it gets grokked, then a catalog and a field index will be created.
But then if you add a second field index:

class MyIndexes(grok.Indexes):
grok.site(MyApp)
grok.context(gsc.haystack.interfaces.IContent)

created = grok.index.Field()
modified = grok.index.Field()

This index doesn't get created. Soooo ... what's the best way to
migrate a catalog when the indexes are updated after the initial
creation. Anyone got any tips here?
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Values from another document before rendering

2009-11-26T07:03:59Z

This is what I do. I have a field defined in an interface:

gallery_id = schema.Choice(title=u"Gallery", vocabulary=u"Published
NewProductGalleries")

The vocabulary looks like this (it is a bit dirty, but it might help
you in the right direction):

import grok
from zope import schema
from zope.schema.vocabulary import SimpleVocabulary
from boardsportsource import interfaces
from boardsportsource import workflow
from hurry import query

class NewProductGalleriesSource(grok.GlobalUtility):
grok.implements(schema.interfaces.IVocabularyFactory)
grok.name('Published NewProductGalleries')
def __call__(self, context):
terms = self.get_published_galleries(context)
return SimpleVocabulary(terms)

def get_published_galleries(self, context):
hasItem = []
if hasattr(context, 'gallery_id') and context.gallery_id is
not None:
# I allways need to have the current value in my vocabulary
# or choice widgets won't render.
hasItem.append(context.gallery_id)

# I use hurry.query to find the objects I want to use in
# my vocabulary.
theQuery = query.Eq(('workflow_catalog', 'workflow_state'),
workflow.PUBLISHED)
theQuery = theQuery & query.Eq(('workflow_catalog',
'object_type'), 'new_product_gallery')
dictResult = query.query.Query().searchResults(theQuery)

theList = []
for item in dictResult:
theObj = interfaces.INewProductGallery(item)

theList.append(SimpleVocabulary.createTerm(theObj.__name__,
theObj.__name__, '%s (%s)' % (theObj.title, 'default')))
if theObj.__name__ in hasItem:
hasItem.remove(theObj.__name__)

for key in hasItem:
# If the current value wasn't found in the search I add
it here
# with an appropriate message.
if grok.getSite()['default'].has_key(key):
theObj =
interfaces.IImageOfTheDayGallery(grok.getSite()['default'][key])
theList.append(SimpleVocabulary.createTerm(key, key,
'%s (not published!)' % theObj.title))
else:
theList.append(SimpleVocabulary.createTerm(key, key,
'%s has been removed!' % key))
return theList

Mvh Sebastian

26 nov 2009 kl. 11.00 skrev Kathy Manwaring:

> Firstly, thank you very much for your quick responses to my last
> query -
> they put me on the right track. Now, I have another question...
>
> I have a class that needs to get values from another entry when it is
> created or edited. So, when creating a Person, the list of values
> that I
> can choose from for the type of Person are values that are editable on
> another entry.
>
> It LOOKS like I should be able to use a dynamically calculated
> SimpleVocabulary, but I can't get it to work - I think I need to use
> self.context on the interface definition of the schema field, but
> self is
> not defined.
>
> Alternatively, can I do it in setupWidgets before rendering? (Can't
> see
> enough information about setupWidgets to answer the question).
>
> Any help would be appreciated.
>
> Kathy
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Values from another document before rendering

2009-11-26T02:00:45Z

Firstly, thank you very much for your quick responses to my last query -
they put me on the right track. Now, I have another question...

I have a class that needs to get values from another entry when it is
created or edited. So, when creating a Person, the list of values that I
can choose from for the type of Person are values that are editable on
another entry.

It LOOKS like I should be able to use a dynamically calculated
SimpleVocabulary, but I can't get it to work - I think I need to use
self.context on the interface definition of the schema field, but self is
not defined.

Alternatively, can I do it in setupWidgets before rendering? (Can't see
enough information about setupWidgets to answer the question).

Any help would be appreciated.

Kathy

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: url() method on JSON component

2009-11-25T02:36:32Z

Martijn Faassen wrote:

> Jan-Wijbrand Kolman wrote:
>
>> Proposal:
>>
>> Not only the url() method is useful for JSON (and maybe even the REST)
>> components, but so are the application_url() method and the response
>> property.
>
> I think certainly we need them for the REST components too. It's very
> common one wants to generate a URL when writing a RESTful protocol.
>
>> The url() method and the response property is defined in
>> grokcore.view.View. We could split out these into a seperate baseclass.
>> grokcore.view.View will then inherit from this baseclass.
>>
>> In grok we will define a mixin class derived from this baseclass that
>> adds the application_url() method. The JSON and REST components can then
>> inherit from this mixin class.
>
> Sounds reasonable. We practically have that mixin class already in the
> form of components.View in grok. The only differences are that it's a
> mixin and doesn't have the flash() method.

Short (oh no, bikeshed alert..!) naming question:

I'm about to checkin some changes in grokcore.view and grok that will:

1) split off the response property and the url() and the redirect()
methods from grokcore.view.View into a separate "mixin" class.

2) split off the application_url() method from grok.component.View into
a separate "mixin" class.

That way JSON and XMLRPC and REST components can inherit from these
mixins and thus gain all the mentioned methods.

Now, what do I call these mixins?

So far I came up with "ViewCommonMixin" for the first. Ugh. And
ApplicationCommonMixin. Ugh Ugh. Anyone a better idea?

regards,
jw

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: grokproject broken

2009-11-23T15:00:20Z

And even more so…it may be an issue with our stupid corporate firewall. Don’t bother looking into this at this point.

From: Jeffrey D Peterson [mailto:bgpete@...]
Sent: Monday, November 23, 2009 4:56 PM
To: 'grok-dev@...'
Subject: RE: grokproject broken

After looking some more it may actually be a bigger issue, with pypi.

From: Jeffrey D Peterson [mailto:bgpete@...]
Sent: Monday, November 23, 2009 4:52 PM
To: 'grok-dev@...'
Subject: grokproject broken

For some reason I can’t do anything with grokproject.

zope@zope2a:~/internal$ virtualenv-2.5 grokenv2

New python executable in grokenv2/bin/python-2.5.4

Also creating executable in grokenv2/bin/python

Installing setuptools............done.

zope@zope2a:~/internal$ cd grokenv2/

zope@zope2a:~/internal/grokenv2$ source bin/activate

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install -U setuptools

Searching for setuptools

Reading http://pypi.python.org/simple/setuptools/

Best match: setuptools 0.6c9

Processing setuptools-0.6c9-py2.5.egg

setuptools 0.6c9 is already the active version in easy-install.pth

Installing easy_install script to /home/zope/internal/grokenv2/bin

Installing easy_install-2.5 script to /home/zope/internal/grokenv2/bin

Using /home/zope/internal/grokenv2/lib/python2.5/site-packages/setuptools-0.6c9-py2.5.egg

Processing dependencies for setuptools

Finished processing dependencies for setuptools

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install grokproject

Searching for grokproject

Reading http://pypi.python.org/simple/grokproject/

No local packages or download links found for grokproject

error: Could not find suitable distribution for Requirement.parse('grokproject')

(grokenv2)zope@zope2a:~/internal/grokenv2$

I went down this path because I am also having all sorts of issues with an existing grokproject install complaining about version_info_url when trying to create a new project.

Anyone know what’s up?

Jeffrey D Peterson

Webmaster

Crary Industries, Inc.

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: grokproject broken

2009-11-23T14:55:35Z

After looking some more it may actually be a bigger issue, with pypi.

From: Jeffrey D Peterson [mailto:bgpete@...]
Sent: Monday, November 23, 2009 4:52 PM
To: 'grok-dev@...'
Subject: grokproject broken

For some reason I can’t do anything with grokproject.

zope@zope2a:~/internal$ virtualenv-2.5 grokenv2

New python executable in grokenv2/bin/python-2.5.4

Also creating executable in grokenv2/bin/python

Installing setuptools............done.

zope@zope2a:~/internal$ cd grokenv2/

zope@zope2a:~/internal/grokenv2$ source bin/activate

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install -U setuptools

Searching for setuptools

Reading http://pypi.python.org/simple/setuptools/

Best match: setuptools 0.6c9

Processing setuptools-0.6c9-py2.5.egg

setuptools 0.6c9 is already the active version in easy-install.pth

Installing easy_install script to /home/zope/internal/grokenv2/bin

Installing easy_install-2.5 script to /home/zope/internal/grokenv2/bin

Using /home/zope/internal/grokenv2/lib/python2.5/site-packages/setuptools-0.6c9-py2.5.egg

Processing dependencies for setuptools

Finished processing dependencies for setuptools

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install grokproject

Searching for grokproject

Reading http://pypi.python.org/simple/grokproject/

No local packages or download links found for grokproject

error: Could not find suitable distribution for Requirement.parse('grokproject')

(grokenv2)zope@zope2a:~/internal/grokenv2$

I went down this path because I am also having all sorts of issues with an existing grokproject install complaining about version_info_url when trying to create a new project.

Anyone know what’s up?

Jeffrey D Peterson

Webmaster

Crary Industries, Inc.

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

grokproject broken

2009-11-23T14:51:54Z

For some reason I can’t do anything with grokproject.

zope@zope2a:~/internal$ virtualenv-2.5 grokenv2

New python executable in grokenv2/bin/python-2.5.4

Also creating executable in grokenv2/bin/python

Installing setuptools............done.

zope@zope2a:~/internal$ cd grokenv2/

zope@zope2a:~/internal/grokenv2$ source bin/activate

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install -U setuptools

Searching for setuptools

Reading http://pypi.python.org/simple/setuptools/

Best match: setuptools 0.6c9

Processing setuptools-0.6c9-py2.5.egg

setuptools 0.6c9 is already the active version in easy-install.pth

Installing easy_install script to /home/zope/internal/grokenv2/bin

Installing easy_install-2.5 script to /home/zope/internal/grokenv2/bin

Using /home/zope/internal/grokenv2/lib/python2.5/site-packages/setuptools-0.6c9-py2.5.egg

Processing dependencies for setuptools

Finished processing dependencies for setuptools

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install grokproject

Searching for grokproject

Reading http://pypi.python.org/simple/grokproject/

No local packages or download links found for grokproject

error: Could not find suitable distribution for Requirement.parse('grokproject')

(grokenv2)zope@zope2a:~/internal/grokenv2$

I went down this path because I am also having all sorts of issues with an existing grokproject install complaining about version_info_url when trying to create a new project.

Anyone know what’s up?

Jeffrey D Peterson

Webmaster

Crary Industries, Inc.

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: grokproject broken

2009-11-23T14:34:08Z

For some reason I can’t do anything with grokproject.

zope@zope2a:~/internal$ virtualenv-2.5 grokenv2

New python executable in grokenv2/bin/python-2.5.4

Also creating executable in grokenv2/bin/python

Installing setuptools............done.

zope@zope2a:~/internal$ cd grokenv2/

zope@zope2a:~/internal/grokenv2$ source bin/activate

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install -U setuptools

Searching for setuptools

Reading http://pypi.python.org/simple/setuptools/

Best match: setuptools 0.6c9

Processing setuptools-0.6c9-py2.5.egg

setuptools 0.6c9 is already the active version in easy-install.pth

Installing easy_install script to /home/zope/internal/grokenv2/bin

Installing easy_install-2.5 script to /home/zope/internal/grokenv2/bin

Using /home/zope/internal/grokenv2/lib/python2.5/site-packages/setuptools-0.6c9-py2.5.egg

Processing dependencies for setuptools

Finished processing dependencies for setuptools

(grokenv2)zope@zope2a:~/internal/grokenv2$ easy_install grokproject

Searching for grokproject

Reading http://pypi.python.org/simple/grokproject/

No local packages or download links found for grokproject

error: Could not find suitable distribution for Requirement.parse('grokproject')

(grokenv2)zope@zope2a:~/internal/grokenv2$

I went down this path because I am also having all sorts of issues with an existing grokproject install complaining about version_info_url when trying to create a new project.

Anyone know what’s up?

Jeffrey D Peterson

Webmaster

Crary Industries, Inc.

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Question re EditForm and ZPT

2009-11-23T06:21:23Z

Hey,

Christian Klinger wrote:
> yes i missuesd a grok.EditForm in other project.
> This was the way to fix this...

Ah, yeah, a misuse. We should always make sure that we mention that this
is a hack to avoid leading beginners astray.

If this is a useful hack, we could simply think about making 'applyData'
available on grok.View instead. I'm not sure whether that is a good
practice, though..

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Question re EditForm and ZPT

2009-11-23T02:16:16Z

Hi Martijn;

yes i missuesd a grok.EditForm in other project.
This was the way to fix this...

I am not sure if it makes sens in Kathys environment.

Christian

> Christian Klinger wrote:
>> yo can try this:
>>
>> class Edit(grok.EditForm):
>> ...
>> adapters = None
>> or
>> adapters = {}
>>
>> I hope this will fix your error.
>
> I don't understand why this should be necessary. Have you run into this
> before?
>
> Regards,
>
> Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Question re EditForm and ZPT

2009-11-23T01:55:03Z

Kathy Manwaring wrote:

[snip]

> As this is just a button, and it's defined based on EditForm, why does
> applyData give an error?
>
> Hoping someone can help, as this really has me stumped - all the
> documentation says that I've done it right...

It's definitely a strange error.

I see a few unusual things:

You have manually set your page template using 'template'. You ought to
be able to just leave the 'template' line out entirely and things should
still work. I don't see how this would be the cause of your problem,
however.

You haven't set form_fields. Normally if you use grok.EditForm you'd use
Grok's form system and you'd need to set form_fields using grok.Fields().

Finally, you try to handle a grok.EditForm during an 'update()'. When
you use grok.EditForm, you'll have to use all of it: generating form
fields from a schema, and validating the information using handlers that
say @grok.action(). Instead you try to handle the input manually and try
to do 'applyData' with information that's in your raw form.

You have two choices:

* stick with a hand-generated form but use a grok.View, not
grok.EditForm. The only bit you have missing would be 'applyData'. If
you are certain that you can simply put the fields on the contexts
without any further validation, you can easily implement applyData yourself:

def myApplyData(obj, **data):
for key, value in data.items():
setattr(obj, key, value)

* actually use Grok's high-level form machinery, including a schema and
form_fields and so on. For more information about that you can read the
developer's notes:

http://grok.zope.org/doc/current/grok_overview.html#forms

This also contains a bunch of tutorials:

http://grok.zope.org/documentation/phc_topic_area?topic=Forms

Note that at least the second tutorial "Automatic Form Generation"
currently has a problem as it depends on a library called z3c.widget
which won't install properly.

Briefly, you'd not implement your own 'update', you'd define a
form_fields and you'd use @grok.action() to define the submit button
handler.

Good luck!

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Question re EditForm and ZPT

2009-11-23T01:45:43Z

Christian Klinger wrote:
> yo can try this:
>
> class Edit(grok.EditForm):
> ...
> adapters = None
> or
> adapters = {}
>
> I hope this will fix your error.

I don't understand why this should be necessary. Have you run into this
before?

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Question re EditForm and ZPT

2009-11-23T00:04:08Z

Hi Kathy,

yo can try this:

class Edit(grok.EditForm):
...
adapters = None
or
adapters = {}

I hope this will fix your error.

Christian

> I have created a ZPT which has the following button present:
> <input type="submit" id="SubmitButton" name="SubmitButton" value="Save"
> class="button" />
>
> The relevant class has an update method that is triggered by the button:
> class Edit(grok.EditForm):
> grok.context(Person)
> template = grok.PageTemplateFile('people_templates/edit.pt')
>
> def update(self, SubmitButton=None, **data):
> # Check if the submit button was clicked.
> if SubmitButton == None:
> print 'SubmitButton empty'
> if SubmitButton != None:
> print 'SubmitButton is:' + SubmitButton + ':'
> if SubmitButton == 'Save':
> print 'you hit the Save button'
> # copy the new or updated information
> print self.context
> print self
> self.applyData(self.context, **data)
> print 'have set fields'
>
> Error: AttributeError: 'Edit' object has no attribute 'adapters'
>
> Information using debug.ini:
>
> URL: http://localhost:8080/my%20system/people/entryValue/edit
> Module paste.evalexception.middleware:306 in respond
> << try:
> __traceback_supplement__ = errormiddleware.Supplement,
> self, environ
> app_iter = self.application(environ, detect_start_response)
> try:
> return_iter = list(app_iter)>> app_iter =
> self.application(environ, detect_start_response)
> Module paste.translogger:68 in __call__
> << self.write_log(environ, method, req_uri, start, status,
> bytes)
> return start_response(status, headers)
> return self.application(environ, replacement_start_response)
>
> def write_log(self, environ, method, req_uri, start, status,
> bytes):>> return self.application(environ,
> replacement_start_response)
> Module zope.app.wsgi:55 in __call__
> << handle_errors = environ.get('wsgi.handleErrors', True)
>
> request = publish(request, handle_errors=handle_errors)
> response = request.response>> request = publish(request,
> handle_errors=handle_errors)
> Module zope.publisher.publish:133 in publish
> << publication.afterTraversal(request, obj)
>
> result = publication.callObject(request, obj)
> response = request.response
> if result is not response:>> result =
> publication.callObject(request, obj)
> Module grok.publication:89 in callObject
> << if checker is not None:
> checker.check(ob, '__call__')
> return super(ZopePublicationSansProxy,
> self).callObject(request, ob)>> return
> super(ZopePublicationSansProxy, self).callObject(request, ob)
> Module zope.app.publication.zopepublication:167 in callObject
> <<
> def callObject(self, request, ob):
> return mapply(ob, request.getPositionalArguments(), request)
>
> def afterCall(self, request, ob):>> return mapply(ob,
> request.getPositionalArguments(), request)
>
> <test.person.Edit object at 0x0313DB30>
>
>
> Module zope.publisher.publish:108 in mapply
> <<
> if __debug__:
> return debug_call(obj, args)
>
> return obj(*args)>> return debug_call(obj, args)
> Module zope.publisher.publish:114 in debug_call
> << def debug_call(obj, args):
> # The presence of this function allows us to set a pdb breakpoint
> return obj(*args)
>
> def publish(request, handle_errors=True):>> return obj(*args)
> Module grokcore.formlib.components:84 in __call__
> <<
> def __call__(self):
> mapply(self.update, (), self.request)
> if self.request.response.getStatus() in (302, 303):
> # A redirect was triggered somewhere in update(). Don't
> >> mapply(self.update, (), self.request)
>
> <bound method Edit.update of<test.person.Edit object at 0x0313DB30>>
>
>
> Module zope.publisher.publish:108 in mapply
> <<
> if __debug__:
> return debug_call(obj, args)
>
> return obj(*args)>> return debug_call(obj, args)
> Module zope.publisher.publish:114 in debug_call
> << def debug_call(obj, args):
> # The presence of this function allows us to set a pdb breakpoint
> return obj(*args)
>
> def publish(request, handle_errors=True):>> return obj(*args)
> Module test.person:127 in update
> << print self
> #self.adapters = []
> self.applyData(self.context, **data)
> print 'have set fields'
> # if this is a new entry, it will have 'tempentry' as part
> of the last name
> >> self.applyData(self.context, **data)
> Module grokcore.formlib.components:128 in applyData
> << def applyData(self, obj, **data):
> return formlib.apply_data_event(obj, self.form_fields, data,
> self.adapters, update=True)
>
> # BBB -- to be removed in June 2007
> >> self.adapters, update=True)
> AttributeError: 'Edit' object has no attribute 'adapters'
>
> As this is just a button, and it's defined based on EditForm, why does
> applyData give an error?
>
> Hoping someone can help, as this really has me stumped - all the
> documentation says that I've done it right...
>
> Kathy

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Question re EditForm and ZPT

2009-11-22T23:32:06Z

I have created a ZPT which has the following button present:
<input type="submit" id="SubmitButton" name="SubmitButton" value="Save"
class="button" />

The relevant class has an update method that is triggered by the button:
class Edit(grok.EditForm):
grok.context(Person)
template = grok.PageTemplateFile('people_templates/edit.pt')

def update(self, SubmitButton=None, **data):
# Check if the submit button was clicked.
if SubmitButton == None:
print 'SubmitButton empty'
if SubmitButton != None:
print 'SubmitButton is:' + SubmitButton + ':'
if SubmitButton == 'Save':
print 'you hit the Save button'
# copy the new or updated information
print self.context
print self
self.applyData(self.context, **data)
print 'have set fields'

Error: AttributeError: 'Edit' object has no attribute 'adapters'

Information using debug.ini:

URL: http://localhost:8080/my%20system/people/entryValue/edit
Module paste.evalexception.middleware:306 in respond
<< try:
__traceback_supplement__ = errormiddleware.Supplement,
self, environ
app_iter = self.application(environ, detect_start_response)
try:
return_iter = list(app_iter)>> app_iter =
self.application(environ, detect_start_response)
Module paste.translogger:68 in __call__
<< self.write_log(environ, method, req_uri, start, status,
bytes)
return start_response(status, headers)
return self.application(environ, replacement_start_response)

def write_log(self, environ, method, req_uri, start, status,
bytes):>> return self.application(environ,
replacement_start_response)
Module zope.app.wsgi:55 in __call__
<< handle_errors = environ.get('wsgi.handleErrors', True)

request = publish(request, handle_errors=handle_errors)
response = request.response>> request = publish(request,
handle_errors=handle_errors)
Module zope.publisher.publish:133 in publish
<< publication.afterTraversal(request, obj)

result = publication.callObject(request, obj)
response = request.response
if result is not response:>> result =
publication.callObject(request, obj)
Module grok.publication:89 in callObject
<< if checker is not None:
checker.check(ob, '__call__')
return super(ZopePublicationSansProxy,
self).callObject(request, ob)>> return
super(ZopePublicationSansProxy, self).callObject(request, ob)
Module zope.app.publication.zopepublication:167 in callObject
<<
def callObject(self, request, ob):
return mapply(ob, request.getPositionalArguments(), request)

def afterCall(self, request, ob):>> return mapply(ob,
request.getPositionalArguments(), request)

<test.person.Edit object at 0x0313DB30>

Module zope.publisher.publish:108 in mapply
<<
if __debug__:
return debug_call(obj, args)

return obj(*args)>> return debug_call(obj, args)
Module zope.publisher.publish:114 in debug_call
<< def debug_call(obj, args):
# The presence of this function allows us to set a pdb breakpoint
return obj(*args)

def publish(request, handle_errors=True):>> return obj(*args)
Module grokcore.formlib.components:84 in __call__
<<
def __call__(self):
mapply(self.update, (), self.request)
if self.request.response.getStatus() in (302, 303):
# A redirect was triggered somewhere in update(). Don't
>> mapply(self.update, (), self.request)

<bound method Edit.update of <test.person.Edit object at 0x0313DB30>>

Module zope.publisher.publish:108 in mapply
<<
if __debug__:
return debug_call(obj, args)

return obj(*args)>> return debug_call(obj, args)
Module zope.publisher.publish:114 in debug_call
<< def debug_call(obj, args):
# The presence of this function allows us to set a pdb breakpoint
return obj(*args)

def publish(request, handle_errors=True):>> return obj(*args)
Module test.person:127 in update
<< print self
#self.adapters = []
self.applyData(self.context, **data)
print 'have set fields'
# if this is a new entry, it will have 'tempentry' as part
of the last name
>> self.applyData(self.context, **data)
Module grokcore.formlib.components:128 in applyData
<< def applyData(self, obj, **data):
return formlib.apply_data_event(obj, self.form_fields, data,
self.adapters, update=True)

# BBB -- to be removed in June 2007
>> self.adapters, update=True)
AttributeError: 'Edit' object has no attribute 'adapters'

As this is just a button, and it's defined based on EditForm, why does
applyData give an error?

Hoping someone can help, as this really has me stumped - all the
documentation says that I've done it right...

Kathy

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: libraries to use with Grok

2009-11-20T12:39:07Z

A raw copy/paste from the mail i did to the mailing list, some time ago.
I need to add some to the list, but, it's there.
As for the megrok packages, I'll detail them when I have some time to
write a smal desc somewhere
note that the pypi pages SHOULD be clear enough with an intro and
everything to simply copy/paste it

Packages
========

http://pypi.python.org/pypi/dolmen.file
A Zope3/Grok File Representation package.
dolmen.file is a layer above zope.app.file.file.File, adding a notion
of filename, missing in the original implementation.

http://pypi.python.org/pypi/dolmen.blob
Dolmen zodb blob handlers (using ZODB >= 3.9.2)
dolmen.blob is a layer above dolmen.file, using the ZODB blobs as a
storage facility. It respects the zope.app.file IFile and the
dolmen.file INamedFile interfaces.

http://pypi.python.org/pypi/dolmen.storage
Dolmen pluggable and delegated storage
dolmen.storage defines a clear high-level API to deal with pluggable
storage components.

http://pypi.python.org/pypi/dolmen.relations
Dolmen relations
dolmen.relations is a thin layer above zc.relation, allowing a simple
and straightforward implementation of standalone relationships between
objects.

http://pypi.python.org/pypi/dolmen.thumbnailer
Dolmen thumbnailing library
dolmen.thumbnailer is package specialized in Thumbnail generation.
Using the dolmen.storage mechanisms, it allows a pluggable and
flexible thumbnail storage.

http://pypi.python.org/pypi/dolmen.widget.file
File widget for z3c.form, using Grok
dolmen.widget.file is a package that walks hand-in-hand with
dolmen.file. It provides a useable and pluggable way to render the
dolmen.file.FileField in a z3c.form.Form, using Grok (through
megrok.z3cform.base)

http://pypi.python.org/pypi/dolmen.widget.image
Image widget (with thumbnails) for z3c.form, using Grok
dolmen.widget.image is a thin layer above dolmen.widget.file providing
a widget suitable to fields implementing IImageField. It adds, thanks
to dolmen.thumbnailer a preview of the uploaded image in both input
and display mode.

We have also released the first version of megrok.z3cform.base, used
in the project
http://pypi.python.org/pypi/megrok.z3cform.base/0.1"

ENJOY !!
PS : please, let me know if you have any opinions/remarks/wishes/insults

2009/11/20 Martijn Faassen <faassen@...>:

> Steve Schmechel wrote:
>> I will be out of town for a few days, back for a day, and then gone
>> for the rest of next week.
>>
>> Please don't stop adding library suggestions to the list because you
>> don't see the page on the Grok site being updated.
>>
>> I will go through the list and find all the suggestions and compile
>> them for review when I return.
>
> Thanks for the heads up, and have a good set of trips!
>
> Regards,
>
> Martijn
>
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: Grok Menu

2009-11-20T12:35:53Z

Hey,

Souheil CHELFOUH wrote:

> I'm brainstorming since Cologne Sprint about the menu feature.
> Currently, i'm using megrok.menu, but it doesn't quite do what I want.
> I also had a look at z3c.menu.simple, but, it's not flexible enough.
> I'd like to know what are people's usecases and start something new.
>
> Ideally, a menu item could be anything. A view, a viewlet or anything else.
> Right now, I ran into problem with megrok.menu, since the grokker is
> registered for grok.View and I want non-grok.View components in my
> menu.
> I don't really know what would be the best implementation and the most
> flexible one.
>
> What about a class decorator that could register the component somehow ?

I think at this stage we'd still look at grokkers for this, as that's
how we register things in general. We'll likely turn to class decorators
(at least optionally) for Martian directives at some point, but Grok's
general idea is to do registration at a defined time that's not import-time.

That said, one idea is to extend Martian so it can grok things based on
the presence of interface declarations on the class instead of just base
classes. That might be useful here, perhaps.

> I need help, conceptually, on this one.
> Anyone's out there to provide a helping hand ? :)

You have a lot more experience doing menus with Grok than I have. I can
only be of conceptual help if you come up with a bit of material for me
to work with. And I'm quite interested in helping you make progress on this.

It'd help me if you could sketch out how megrok.menu and z3c.menu.simple
don't quite do what you want, and what your use cases are.

What would it mean to turn, say, a viewlet or a model into a menu item?

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: libraries to use with Grok

2009-11-20T12:30:54Z

Steve Schmechel wrote:
> I will be out of town for a few days, back for a day, and then gone
> for the rest of next week.
>
> Please don't stop adding library suggestions to the list because you
> don't see the page on the Grok site being updated.
>
> I will go through the list and find all the suggestions and compile
> them for review when I return.

Thanks for the heads up, and have a good set of trips!

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: libraries to use with Grok

2009-11-20T12:23:44Z

I will be out of town for a few days, back for a day, and then gone for the rest of next week.

Please don't stop adding library suggestions to the list because you don't see the page on the Grok site being updated.

I will go through the list and find all the suggestions and compile them for review when I return.

Keep up the momentum.

Regards,
Steve

--- On Fri, 11/20/09, Martijn Faassen <faassen@...> wrote:

> From: Martijn Faassen <faassen@...>
> Subject: Re: [Grok-dev] libraries to use with Grok
> To: grok-dev@...
> Date: Friday, November 20, 2009, 12:13 PM
> Kent Tenney wrote:
> > <snip>
> > - Seems a likely candidate for wiki, the main
> page listing the
> > - namespaces, each line has a list to a wiki page for
> that namespace.
> >
> > + each line consisting of a brief description (as
> provided by Martijn)
> > + and a link to a wiki page where notes and details
> could be added.
>
> I think that's overkill. I think a single page giving a
> description
> would be fine. It's not like these namespaces are *that*
> relevant, as I
> tried to say. They give a general idea of what might be in
> it, but far
> more important is just knowing about the package.
>
> Regards,
>
> Martijn
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: libraries to use with Grok

2009-11-20T10:13:05Z

Kent Tenney wrote:
> <snip>
> - Seems a likely candidate for wiki, the main page listing the
> - namespaces, each line has a list to a wiki page for that namespace.
>
> + each line consisting of a brief description (as provided by Martijn)
> + and a link to a wiki page where notes and details could be added.

I think that's overkill. I think a single page giving a description
would be fine. It's not like these namespaces are *that* relevant, as I
tried to say. They give a general idea of what might be in it, but far
more important is just knowing about the package.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Grok Menu

2009-11-20T07:33:57Z

Hello Grokkers,

I'm brainstorming since Cologne Sprint about the menu feature.
Currently, i'm using megrok.menu, but it doesn't quite do what I want.
I also had a look at z3c.menu.simple, but, it's not flexible enough.
I'd like to know what are people's usecases and start something new.

Ideally, a menu item could be anything. A view, a viewlet or anything else.
Right now, I ran into problem with megrok.menu, since the grokker is
registered for grok.View and I want non-grok.View components in my
menu.
I don't really know what would be the best implementation and the most
flexible one.

What about a class decorator that could register the component somehow ?

I need help, conceptually, on this one.
Anyone's out there to provide a helping hand ? :)
_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: libraries to use with Grok

2009-11-20T07:03:54Z

<snip>
- Seems a likely candidate for wiki, the main page listing the
- namespaces, each line has a list to a wiki page for that namespace.

+ each line consisting of a brief description (as provided by Martijn)
+ and a link to a wiki page where notes and details could be added.

>
> Looking at http://grok.zope.org/documentation, I see a Plone page
> using features I don't understand.
>
> So, I was going to try my hand at a "About namespaces" page, but
> it seems Grok doc is not aimed at wiki-style content additions from
> the community.
>
> Thanks,
> Kent
>
>>
>> Regards,
>>
>> Martijn
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev@...
>> https://mail.zope.org/mailman/listinfo/grok-dev
>>
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: libraries to use with Grok

2009-11-20T06:37:31Z

On Fri, Nov 20, 2009 at 2:51 AM, Martijn Faassen <faassen@...> wrote:

> Kent Tenney wrote:
>> On Thu, Nov 19, 2009 at 5:35 AM, Santiago Videla
>> <santiago.videla@...> wrote:
>>> Hey,
>>> I think that the list could become really large...
>>> megrok.*
>>> : http://pypi.python.org/pypi?:action=search&term=megrok&submit=search
>>> hurry.*
>>> : http://pypi.python.org/pypi?:action=search&term=hurry&submit=search
>>> dolmen.* http://pypi.python.org/pypi?:action=search&term=dolmen&submit=search
>>
>> I would welcome a brief description of the namespace collections, who is
>> behind them, a bit of history, target niche etc.
>> hurry, megrok, dolmen, zc, z3c, zope, repoze, lazr ...
>
> It'll have to go into another document, but here goes some sketch:
>
> First a general disclaimer: the namespace doesn't really *mean* all that
> much. The goal of having a namespace is to make it easier to create a
> package of some name without conflicting with another package. I.e. if
> we had no namespaces if I made a package 'resource' there'd be a good
> chance someone else would want to do the same thing, and what would we
> do then?
>
> zope.*: the namespace used originally by the Zope 3 project. Now the
> namespace of the Zope Toolkit. Generally core framework packages, though
> there's a lot of stuff that isn't.
>
> zope.app.*: the idea was to make the Zope 3-specific things reside here,
> the more general things in zope.*. This wasn't maintained very well, as
> nobody quite agrees on what is what anyway. Now it is a mostly
> deprecated namespace that contains the old Zope 3 ZMI user interface
> code. We've been moving more general stuff out of it into zope.*
>
> grokcore.*: bits of Grok that we've split out of it into more reusable
> libraries. The five.grok project uses the same libraries to enable Grok
> support in Zope 2.
>
> grokui.*: user interfaces for Grok. The admin UI and the introspector
> end up here.
>
> megrok.*: "Module Extension Grok". Extension code for Grok. Often
> depends on Grok itself, but note that due to Grok's splitting up into
> pieces this code only needs to depend on grokcore.* packages, and could
> be seen as more generally reusable.
>
> zc.*: a space for Zope Corporation to create packages in. There's a
> diverse collection of stuff in there.
>
> z3c.*: a space where the Zope 3 community started to place packages. A
> diverse colletion of stuff.
>
> hurry.*: I started using this for some Zope 3 extensions back in 2005 or
> so. I've continued to use this namespace in the last few years as well
> for some more code I've written. Again, a diverse collection of stuff.
>
> dolmen.*: Souheil has been using this namespace. Much of it, I
> understand, is to support CMS-like applications on top of Grok. Designed
> also be more generally reusable.
>
> repoze.*: the Repoze project is working in its own repository and
> generally Repoze-related libraries are in there. Contains WSGI-related
> packages and the BFG framework, and other diverse stuff.
>
> plone.*: some packages developed by the Plone project. Much of this
> relies either on Zope 2 and/or Plone, but some of it is designed to be
> more generally useful.
>
> collective.*: a general namespace used by the Plone community. Again,
> some of it is designed to be more generally useful, a lot of it ties
> into Plone, however.
>
> lazr.*: a namespace used by Launchpad developers at Canonical. Some of
> it is designed to plug into Zope Toolkit applications.
>
> five.*: generally used as a namespace to place in compatibility code, to
> help use Zope Toolkit or Grok related libraries in Zope 2.
>
> Can someone clean this up and create a document on grok.zope.org out of
> this?

Seems a likely candidate for wiki, the main page listing the
namespaces, each line has a list to a wiki page for that namespace.

Looking at http://grok.zope.org/documentation, I see a Plone page
using features I don't understand.

So, I was going to try my hand at a "About namespaces" page, but
it seems Grok doc is not aimed at wiki-style content additions from
the community.

Thanks,
Kent

>
> Regards,
>
> Martijn
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: meta class in megrok.resource?

2009-11-20T03:50:09Z

Souheil CHELFOUH wrote:
> I understand your point and I have no dogma in this.
> We ca neasy restaure the thing how it was before.
> The point of using the metaclass was simply to avoid grokking the
> package simply to set a name

Okay, but now we have a scary metaclass just to set the name. :)

> I'm very much in favor to simply use name = "". The use of grok.name
> must be to "help and serve" not to constrain us.

That's true. But it's also a matter of consistency: grok.name() has
everywhere been setting the name under which things have been
registered. Here we need '.name' as a library, hurry.resource, needs the
library name. We should definitely be open to the idea that we can
change hurry.resource.

> Here, I felt the grokker was "way" too expensive just to set and attribute.
> But, I did some work more yesterday that makes me feel like I did a
> mistake on this
> Trying to classProvides made me realize that this won't work, since
> classProvides does not work with the subclasses.
> Therefore, we'll have to directlyProvides(cls, ILibrary) in a grokker,
> to make it work properly.

Ah, yeah, I hadn't realized that. Makes sense.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

Re: meta class in megrok.resource?

2009-11-20T03:07:43Z

I understand your point and I have no dogma in this.
We ca neasy restaure the thing how it was before.
The point of using the metaclass was simply to avoid grokking the
package simply to set a name
I'm very much in favor to simply use name = "". The use of grok.name
must be to "help and serve" not to constrain us.
Here, I felt the grokker was "way" too expensive just to set and attribute.
But, I did some work more yesterday that makes me feel like I did a
mistake on this
Trying to classProvides made me realize that this won't work, since
classProvides does not work with the subclasses.
Therefore, we'll have to directlyProvides(cls, ILibrary) in a grokker,
to make it work properly

2009/11/20 Martijn Faassen <faassen@...>:

> Hi there,
>
> hurry.resource needs a 'name' attribute to be present on an ILibrary
> object.
>
> The idea in megrok.resource is to make its Library class have this name
> attribute (not just instances of it), as it needs to provide the
> ILibrary interface. Note that it'd be the *class* providing an ILibrary
> interface, not the instance.
>
> The simplest way for a class to get a name attribute would be to do this:
>
> class Library(object):
> name = 'foo'
>
> Unfortunately we want to use grok.name() instead.
>
> In a previous implementation a Grokker was used to do this. Souheil in a
> checkin declared this operation as "WAY too expensive" and instead made
> the Library class derive from a meta class that takes care of setting
> the name business. I am wary of this as a metaclass introduces potential
> run-time complexity that a grokker doesn't.
>
> One nice thing about grokkers is exactly that metaclass wizardy can be
> kept to a minimum. So I'd like to understand why a grokker is considered
> to be too expensive. After all, another grokker will grok Library anyway
> as it subclasses DirectoryResource. During run-time the expense is now
> larger (though still minimal).
>
> If it's not desired to use a grokker, another option would be for
> hurry.resource.ResourceInclusion to try to adapt the incoming Library
> object to ILibrary first. The adapter could then do whatever it wants
> (and it could simply set '.name' in its __init__). The ILibrary
> interface is after all, really easy to satisfy (just a name is
> necessary). Though perhaps this option is a bit more complex as it'd be
> nicer to be able to directly let the Library class provide ILibrary, so
> taht the ILibraryUrl adapter can adapt the class.
>
> Regards,
>
> Martijn
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev