Nabble - Grok

Re: generic directoryresource in grokcore.view

2008-10-15T16:02:20Z

On Oct 10, 1:09 am, "Jan-Wijbrand Kolman" <janwijbr...@...>
wrote:
>
> sometimes you expect the "static" thing to point to a particular
> directory of resources where it cannot find it. This is not really to
> do with skinning, but with, for example, having a layout macro defined
> in one package being used by templates in another package. Where the
> layout macro then finds its resources can be confusing.
>

Well, I just found myself faced with same problem (and started
creating an icky workaround this morning until I realized that this
thread was about the problem I was trying to solve ...). So I'll at
least find this will be useful :)

Is there plans to make this available as part of the grok API, e.g.
grok.DirectoryResource?

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

Re: generic directoryresource in grokcore.view

2008-10-15T12:34:42Z

Sylvain Viollon wrote:
> I am fine with that as well. I will update five.grok so that still
> work/provides the same features.
>
> Please tell me when you merged,

I just merged the jw-generic_directory_resource branch. I'm about to
make a 1.2 release as well.

kind regards,
jw

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

Re: Grok runs on Python 2.6

2008-10-15T11:37:38Z

Philipp von Weitershausen wrote:
> Thanks to Sidnei's heroic efforts during the last few days of fixing
> various Zope packages and releasing them, too, Grok actually runs on
> Python 2.6 and all tests pass!

Yay Sidnei!!!

regards,
jw

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

Grok runs on Python 2.6

2008-10-15T09:21:47Z

Thanks to Sidnei's heroic efforts during the last few days of fixing
various Zope packages and releasing them, too, Grok actually runs on
Python 2.6 and all tests pass!

Yes, there are a few deprecation warnings here and there. And when I
compiled the ZODB egg under Python 2.6 it reported a syntax error in
some module (that seems to be unused in Grok, though). So you might not
want to do this in production just yet ;). But certainly it's good to
see that all tests pass and we have an actual list of things to work on.

Anybody who'd like to replicate the result and perhaps improve the
situation of the deprecation warnings and syntax errors just needs to
override the following versions in buildout.cfg:

[versions]
mechanize = 0.1.9
zope.app.appsetup = 3.8.0
zope.app.component = 3.5.0
zope.app.container = 3.6.1
zope.app.form = 3.6.3
zope.app.publisher = 3.5.1
zope.app.testing = 3.5.6
zope.testbrowser = 3.5.1

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

Re: Naming of grok.provides

2008-10-15T09:14:33Z

On Oct 15, 2008, at 12:18 AM, Thomas Lotze wrote:

> Philipp von Weitershausen wrote:
>
>>> But even with clearer documentation it's still somewhat confusing?
>>> Maybe
>>> grok.registers is clearer?
>>
>> Or grok.register_for(). Consider this example::
>>
>> class FooBar(grok.GlobalUtility):
>> grok.implements(IBar, IFoo)
>> grok.register_for(IFoo)
>
> I like 'register_for' better as well. How to proceed on this now?
> Discuss,
> write a proposal, just implement it, what about deprecation of the
> provides directive? I'm willing to implement the new name if there's
> general consent about it.
>

+1.

I like 'register_for', it's less confusing terminology.

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

Re: Naming of grok.provides

2008-10-15T05:17:55Z

Thomas Lotze wrote:

> Philipp von Weitershausen wrote:
>
>>> But even with clearer documentation it's still somewhat confusing? Maybe
>>> grok.registers is clearer?
>> Or grok.register_for(). Consider this example::
>>
>> class FooBar(grok.GlobalUtility):
>> grok.implements(IBar, IFoo)
>> grok.register_for(IFoo)
>
> I like 'register_for' better as well. How to proceed on this now? Discuss,
> write a proposal, just implement it, what about deprecation of the
> provides directive? I'm willing to implement the new name if there's
> general consent about it.

If there's a general concensus, I suggest renaming grok.provides to
grok.register_for (this actually has to be done in grokcore.component,
Grok just imports it from there) while keeping it around under the old
name for one or two releases.

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

five.grok and grokcore.viewlets

2008-10-15T01:38:56Z

Hello,

I started to work on viewlets in a branch five.grok for one of my
projects. As soon as this work, I will be able to check what we can put
in a grokcore.viewlet, and build that extension.

I think it will be like for grokcore.form, with a
ViewletManagerBase, and ViewletBase, which can be reused in
grokcore.viewlet to build the real ViewletManager and Viewlet
components, and reused in five.grok to build the Five version.

If your interested or want to help, you are welcome.

Best regards,

Sylvain Viollon.

--
Sylvain Viollon -- Infrae
t +31 10 243 7051 -- http://infrae.com
Hoevestraat 10 3033GC Rotterdam -- The Netherlands

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

signature.asc (194 bytes) Download Attachment

Re: generic directoryresource in grokcore.view

2008-10-15T01:19:59Z

Hello,

On Tue, 14 Oct 2008 09:39:24 +0200
Philipp von Weitershausen <philipp@...> wrote:

> Good work! I see nothing wrong with it. However, you've renamed
> grokcore.view.meta.static to grokcore.view.meta.directoryresource.
> That's fine, of course, but the authors of five.grok should be made
> aware that this happened because they might load this module
> individually (Sylvain split up grokcore.view.meta for this reason).

I am fine with that as well. I will update five.grok so that still
work/provides the same features.

Please tell me when you merged,

Sylvain,

--
Sylvain Viollon -- Infrae
t +31 10 243 7051 -- http://infrae.com
Hoevestraat 10 3033GC Rotterdam -- The Netherlands

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

signature.asc (194 bytes) Download Attachment

Re: Naming of grok.provides

2008-10-15T00:18:15Z

Philipp von Weitershausen wrote:

>> But even with clearer documentation it's still somewhat confusing? Maybe
>> grok.registers is clearer?
>
> Or grok.register_for(). Consider this example::
>
> class FooBar(grok.GlobalUtility):
> grok.implements(IBar, IFoo)
> grok.register_for(IFoo)

I like 'register_for' better as well. How to proceed on this now? Discuss,
write a proposal, just implement it, what about deprecation of the
provides directive? I'm willing to implement the new name if there's
general consent about it.

--
Thomas

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

Re: grokproject error

2008-10-14T06:31:47Z

I am getting a strange error. Everything seems to be created (bin/
buildout works as expected), but grokproject exits with an error:

sebastian-wares-dator:groksandbox jhsware$ bin/grokproject --svn-
repository=file:///Users/jhsware/svn_code_repository --user=seb --eggs-
dir=/Users/jhsware/groksandbox/eggs SprintReport

Committed revision 320.
Checked out revision 320.
Downloading info about versions...
Downloading zc.buildout...
Invoking zc.buildout...
Develop: '/Users/jhsware/groksandbox/SprintReport/.'
Installing eggbasket.
Traceback (most recent call last):
File "/Users/jhsware/groksandbox/bin/grokproject", line 7, in ?
sys.exit(
File "/Users/jhsware/groksandbox/lib/python2.4/site-packages/
grokproject-0.9-py2.4.egg/grokproject/main.py", line 49, in main
exit_code = runner.run(option_args + ['-t', 'grok', project]
File "/Users/jhsware/groksandbox/lib/python2.4/site-packages/
PasteScript-1.6.1.1-py2.4.egg/paste/script/command.py", line 213, in run
result = self.command()
File "/Users/jhsware/groksandbox/lib/python2.4/site-packages/
PasteScript-1.6.1.1-py2.4.egg/paste/script/create_distro.py", line
156, in command
self.add_svn_repository(vars, output_dir)
File "/Users/jhsware/groksandbox/lib/python2.4/site-packages/
PasteScript-1.6.1.1-py2.4.egg/paste/script/create_distro.py", line
209, in add_svn_repository
egg_info_dir = pluginlib.egg_info_dir(output_dir, vars['project'])
File "/Users/jhsware/groksandbox/lib/python2.4/site-packages/
PasteScript-1.6.1.1-py2.4.egg/paste/script/pluginlib.py", line 127, in
egg_info_dir
for dir_extension in ['.'] + os.listdir(base_dir):
OSError: [Errno 2] No such file or directory: './SprintReport'

sebastian-wares-dator:groksandbox jhsware$ ls ./SprintReport/
bin bootstrap.py buildout.cfg develop-eggs parts setup.py src
versions.cfg

Mvh Sebastian

11 okt 2008 kl. 04.41 skrev Reed O'Brien:

> On Oct 10, 2008, at 6:02 PM, Martijn Faassen wrote:
>
>> Hey,
>>
>>> Setup script exited with error: Setup script exited with error:
>>> Setup
>>> script exited with error: Setup script exited with error: Setup
>>> script
>>> exited with error: Setup script exited with error: Setup script
>>> exited
>>> with error: Setup script exited with error: Setup script exited with
>>> error: Setup script exited with error:
>>
>> No idea what the cause is, but I just read this:
>>
>> http://blog.vrplumber.com/index.php?/archives/2204-Where-did-that-dependency-come-from.html
>>
>> Which sounds like the same error. A clue, perhaps?
>
> We were seeing this at the plone conference in a buildout; at least
> three of us. It would stall while making a develop-egg then fail
> with the recursive error and : File name too long
>
> Someone suspected archetypes.schemaextender, I was suspicious of
> buildout.eggtractor injecting the egg names (in a loop) into
> buildout the eggs it found to develop.
>
> Removing the <name-of-egg>.egg-info from the develop egg(s) seemed
> to fix it. Then something else failed, possibly unrelated. Then I
> didn't have another chance to look at it.
>
> At least two of the three people I am sure had the same error (and
> partial fix) were on OSX 10.5.x
>
> That is all the details I have....
>
> ~ro_______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> http://mail.zope.org/mailman/listinfo/grok-dev

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

Re: Naming of grok.provides

2008-10-14T01:47:39Z

:) My confusion acctually has to do with the grok.provides()
directive, which I find difficult to relate to the providedBy() method.

I don't understand why I use grok.provides for an adapter and
interface.implements on an object. Then I use providedBy to check if
the object belongs to a class that implements... in the docstring it
does say something like implementedBy(MyClass) and
providedBy(MyObject) so I think I get how I am supposed to use it (it
works anyway), but it is really related the grok.provides directive I
am struggeling.

Mvh Sebastian

14 okt 2008 kl. 09.58 skrev Philipp von Weitershausen:

> Sebastian Ware wrote:
>> I find the difference between implements/provides confusing too.
>> And it gets more complicated when trying to understand the
>> difference between IMyInterface.providedBy(obj) and
>> IMyInterface.implementedBy(obj).
>
> Well, this difference is one of the corner stones of zope.interface
> and not about to change :). I think the difference is pretty clear,
> it just needs to be documented well.

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

Re: Naming of grok.provides

2008-10-14T01:11:28Z

On Tue, Oct 14, 2008 at 10:02, Philipp von Weitershausen
<philipp@...> wrote:
> Kevin Teague wrote:
>> Explicitly specify with which interface a component will be
>> looked up. If a class declares that it implements several
>> interaces,
>> :func:`grok.provides` can be used to disambiguate which interface
>> will be
>> registered with the Zope Component Architecture.
>
> That's a pretty good definition. Thanks!

Yeah, that's how I understood it too. I got very confused now when it
was claimed that the zope definition is that a class implements and an
object provides. But I have the feeling that this is just plain wrong,
as I just a couple of days ago set a provides(ISomething) on a class.
:)

--
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: Naming of grok.provides

2008-10-14T01:02:53Z

Kevin Teague wrote:

> On Oct 12, 2008, at 11:19 PM, Thomas Lotze wrote:
>
>> We recently noticed that the grok.provides directive is not well-
>> named:
>>
>> The documentation states that "if the local utility implements
>> more than one interface or if the implemented interface cannot be
>> determined, grok.provides() is required to disambiguate for what
>> interface the local utility will be registered."
>>
>> OTOH, in zope.interface terminology, the term "provides" has a clear
>> meaning in contrast to "implements": if a class, for instance,
>> implements a certain interface, its instances are said to provide it.
>>
>> We feel that something should be done about this contradiction of
>> terminologies as it confuses not only newcomers to Grok. Beyond a
>> documentation improvement, what would be an acceptable fix given that
>> this directive is rather close to Grok's core?
>>
>
> Yeah, the text in the Grok Reference docs is even more confusing (and
> wrong ... although I think I wrote that.). I've just updated that text
> to read:
>
> :func:`grok.provides` -- disambiguate which interface is registered
> ===================================================
>
> .. function:: grok.provides(interface)
>
> Explicitly specify with which interface a component will be
> looked up. If a class declares that it implements several
> interaces,
> :func:`grok.provides` can be used to disambiguate which interface
> will be
> registered with the Zope Component Architecture.

That's a pretty good definition. Thanks!

> But even with clearer documentation it's still somewhat confusing?
> Maybe grok.registers is clearer?

Or grok.register_for(). Consider this example::

class FooBar(grok.GlobalUtility):
grok.implements(IBar, IFoo)
grok.register_for(IFoo)

> Since any class implements many
> interfaces that is used to create a component, that component is going
> to provide many interfaces - it's just used to state which interface
> is registered with the CA that it's interested in as providing for the
> CA among the many it provides.

Right. I think we chose the name grok.provides() initially because the
keyword parameter of the registrations functions in zope.component is
called "provides". That's a poor excuse, of course.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: Naming of grok.provides

2008-10-14T00:58:16Z

Sebastian Ware wrote:
> I find the difference between implements/provides confusing too. And
> it gets more complicated when trying to understand the difference
> between IMyInterface.providedBy(obj) and
> IMyInterface.implementedBy(obj).

Well, this difference is one of the corner stones of zope.interface and
not about to change :). I think the difference is pretty clear, it just
needs to be documented well.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: generic directoryresource in grokcore.view

2008-10-14T00:39:24Z

Jan-Wijbrand Kolman wrote:

> Jan-Wijbrand Kolman wrote:
>> Grok views by default have access to a "static" directory for resources.
>> They're a special kind of the more general DirectoryResource feature of
>> Zope.
>>
>> Since the resource "static" is always registered for the IDefaultBrowser
>> layer and I wanted to be able to skin resources too (in some case
>> leading to hard to debug error messages) I thought it would be nice to
>> have the more generic DirectoryResource feature available in Grok too.
>>
>> I'm working on implementing the more general 'DirectoryResource' on a
>> branch of grokcore.view:
>>
>> http://svn.zope.org/grokcore.view/branches/jw-generic_directory_resource/
>>
>> I still need to add functional tests though, esp. concerning skinning.
>>
>> Questions:
>>
>> 1) Do people feel this is useful to intergrate in grokcore.view?
>> 2) Could someone have a quick look at the implementation?
>
> I have finished this feaure and I'm ready to merge. If there's any
> interest in it of course.
>
> For your reviewing-convenience I pasted the diff between the trunk and
> the branch here:
>
> http://jw.pastebin.com/f5a357f40

Good work! I see nothing wrong with it. However, you've renamed
grokcore.view.meta.static to grokcore.view.meta.directoryresource.
That's fine, of course, but the authors of five.grok should be made
aware that this happened because they might load this module
individually (Sylvain split up grokcore.view.meta for this reason).
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: Naming of grok.provides

2008-10-13T22:44:33Z

On Oct 12, 2008, at 11:19 PM, Thomas Lotze wrote:

Yeah, the text in the Grok Reference docs is even more confusing (and
wrong ... although I think I wrote that.). I've just updated that text
to read:

:func:`grok.provides` -- disambiguate which interface is registered
===================================================

.. function:: grok.provides(interface)

Explicitly specify with which interface a component will be
looked up. If a class declares that it implements several
interaces,
:func:`grok.provides` can be used to disambiguate which interface
will be
registered with the Zope Component Architecture.

But even with clearer documentation it's still somewhat confusing?
Maybe grok.registers is clearer? Since any class implements many
interfaces that is used to create a component, that component is going
to provide many interfaces - it's just used to state which interface
is registered with the CA that it's interested in as providing for the
CA among the many it provides.

(I think that makes sense? not quite sure - I've been travelling all
day after the PloneConf and am quite tired.)

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

Re: generic directoryresource in grokcore.view

2008-10-13T13:16:28Z

Jan-Wijbrand Kolman wrote:

> Grok views by default have access to a "static" directory for resources.
> They're a special kind of the more general DirectoryResource feature of
> Zope.
>
> Since the resource "static" is always registered for the IDefaultBrowser
> layer and I wanted to be able to skin resources too (in some case
> leading to hard to debug error messages) I thought it would be nice to
> have the more generic DirectoryResource feature available in Grok too.
>
> I'm working on implementing the more general 'DirectoryResource' on a
> branch of grokcore.view:
>
> http://svn.zope.org/grokcore.view/branches/jw-generic_directory_resource/
>
> I still need to add functional tests though, esp. concerning skinning.
>
> Questions:
>
> 1) Do people feel this is useful to intergrate in grokcore.view?
> 2) Could someone have a quick look at the implementation?

I have finished this feaure and I'm ready to merge. If there's any
interest in it of course.

For your reviewing-convenience I pasted the diff between the trunk and
the branch here:

http://jw.pastebin.com/f5a357f40

kind regards,
jw

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

Re: ZODB and storing, retrieving, deleting, use of ID

2008-10-13T07:09:37Z

You might try the python uuid module. I tend to use uuids for RDBMS work, why not use them with the ZODB?

Regards,

Robert Moskal

Laurence Rowe wrote:

John de la Garza wrote:
> I'm making an app that has polls for voting... When I make a Poll
> object to I have to create an ID so I can find it again. I'm comming
> froma RDBMS background and am wondering if there are any articles
> that would helpl me transistion. For example should the ID be the
> last object id + 1? I saw some sample code that kept the objects in
> a list then just got the length of the list, but if items are deleted
> then using the len as the ID could be trouble (not unique).... any
> feed back would be apprecitated. I've read intro to ZODB (Jim
> Fulton) but it doesn't mention deleting

* Randomised keys have better efficiency when filling a B-Tree. You need
to check that the randomly generated key does not already exist.

* Store the length with a BTrees.Length.Length and increment/decrement
as you add/delete.

Laurence

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

Re: Naming of grok.provides

2008-10-13T06:02:54Z

I find the difference between implements/provides confusing too. And
it gets more complicated when trying to understand the difference
between IMyInterface.providedBy(obj) and
IMyInterface.implementedBy(obj).

Mvh Sebastian

13 okt 2008 kl. 08.19 skrev Thomas Lotze:

> We recently noticed that the grok.provides directive is not well-
> named:
>
> The documentation states that "if the local utility implements
> more than one interface or if the implemented interface cannot be
> determined, grok.provides() is required to disambiguate for what
> interface the local utility will be registered."
>
> OTOH, in zope.interface terminology, the term "provides" has a clear
> meaning in contrast to "implements": if a class, for instance,
> implements a certain interface, its instances are said to provide it.
>
> We feel that something should be done about this contradiction of
> terminologies as it confuses not only newcomers to Grok. Beyond a
> documentation improvement, what would be an acceptable fix given that
> this directive is rather close to Grok's core?
>
> Thomas
>
> --
> Thomas Lotze · tl@...
> 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@...
> http://mail.zope.org/mailman/listinfo/grok-dev

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

Re: newbie question: Handling file uploads with zope.app.file

2008-10-13T03:39:48Z

I would suggest that you take a look at some of the basic sample apps
found here:

http://grok.zope.org/about/what-does-grok-code-look-like

I think you will find all your answers there.

Mvh Sebastian

13 okt 2008 kl. 08.42 skrev muli:

>
> I have started 1 week ago so please apologize my stupid question. I
> worked
> thru the tutorial and most parts of the Developer notes so that i
> think that
> i understand general what happens in the HowTo but...
> i have made a file called FileContainer.py and a app.py looking like
> this:
>
> class Test(grok.Application, grok.Container):
> pass
>
> class Index(grok.View):
> pass
>
> How can i display the Form in a Browser?
>
> AddForm is a special kind of View so i tried this:
>
> class Test(grok.Application, grok.Container):
> pass
>
> class Upload(grok.AddForm):
> grok.context(Test)......
>
> But it didn't work!
>
> so please help me.
> muli
> --
> View this message in context: http://www.nabble.com/newbie-question%3A-Handling-file-uploads-with-zope.app.file-tp19949577p19949577.html
> Sent from the Grok mailing list archive at Nabble.com.
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> http://mail.zope.org/mailman/listinfo/grok-dev

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

newbie question: Handling file uploads with zope.app.file

2008-10-12T23:42:26Z

I have started 1 week ago so please apologize my stupid question. I worked thru the tutorial and most parts of the Developer notes so that i think that i understand general what happens in the HowTo but...
i have made a file called FileContainer.py and a app.py looking like this:

class Test(grok.Application, grok.Container):
pass

class Index(grok.View):
pass

How can i display the Form in a Browser?

AddForm is a special kind of View so i tried this:

class Test(grok.Application, grok.Container):
pass

class Upload(grok.AddForm):
grok.context(Test)......

But it didn't work!

so please help me.
muli

Naming of grok.provides

2008-10-12T23:19:40Z

We recently noticed that the grok.provides directive is not well-named:

The documentation states that "if the local utility implements
more than one interface or if the implemented interface cannot be
determined, grok.provides() is required to disambiguate for what
interface the local utility will be registered."

OTOH, in zope.interface terminology, the term "provides" has a clear
meaning in contrast to "implements": if a class, for instance,
implements a certain interface, its instances are said to provide it.

We feel that something should be done about this contradiction of
terminologies as it confuses not only newcomers to Grok. Beyond a
documentation improvement, what would be an acceptable fix given that
this directive is rather close to Grok's core?

Thomas

--
Thomas Lotze · tl@...
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@...
http://mail.zope.org/mailman/listinfo/grok-dev

signature.asc (196 bytes) Download Attachment

Re: Moving a Zope3 app to Grok

2008-10-12T18:03:21Z

> The server fails to start because it found that I am importing pyparsing
> in one of my files. Now of course pyparsing is in my default eggs
> directory.
> ~snip~
> ImportError: No module named pyparsing

It doesn't look like pyparsing is getting picked up in your list of
eggs? This project is listed in your eggs config in your [app] section
or within the install_requires field of your setup.py file? And you've
re-run ./bin/buildout after editing this? You should see pyparsing
listed in parts/app/runzope once it's being properly picked up ...

After for automagically merging them, I'm not aware of anyway to do
this other than manual reviewing the buildout.cfg and copying the
approriate bits over.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: ZODB and storing, retrieving, deleting, use of ID

2008-10-10T20:15:19Z

When doing autogeneration of primary keys in a relational database,
there is usually a separate Sequence object which tracks the value of
the next id to use, when a new record is inserted the Sequence object
is updated by one. It's possible to implement this directly in Grok,
but Laurences suggestions of randomised keys for efficiency may be
preferable.

Note that there is a subtle difference between a database id and a key
name (available as the __name__ attribute on a Grok model object) when
storing data in the ZODB using Grok. A database id is a unique
identifier that is user-friendly for inclusion in SQL statements. A
name is used a unique identifier that is user-friendly for inclusion
in a URL.

When composing a URL in Grok, names are not allowed to start with the
+ or @ characters, not contain the / character (you can store objects
in the ZODB with key names that don't obey these rules, but then when
you want to publish that key name using the normal Grok behaviour you
will have to do some form of messy "fuggling" to get it to work).
Names are often made more human-readable, although what "more human-
readable" is may depend on the type of app you are writing, but in a
CMS, a URL such as:

http://example.com/using-name-choosers.html

Is more human-readable than:

http://example.com/4876598465876497.html

I just put a note about using the INameChooser interface in this
recent article:

http://grok.zope.org/documentation/how-to/uploading-file/view

However, a full discussion on implementing INameChoosers to implement
your desired naming policies (randomized, length based, human-readable-
style.html, etc.) and potentially some packages which have useful
NameChoosers) doesn't exist, but would be good to have ...
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: grokproject error

2008-10-10T19:41:45Z

On Oct 10, 2008, at 6:02 PM, Martijn Faassen wrote:

> Hey,
>
>> Setup script exited with error: Setup script exited with error: Setup
>> script exited with error: Setup script exited with error: Setup
>> script
>> exited with error: Setup script exited with error: Setup script
>> exited
>> with error: Setup script exited with error: Setup script exited with
>> error: Setup script exited with error:
>
> No idea what the cause is, but I just read this:
>
> http://blog.vrplumber.com/index.php?/archives/2204-Where-did-that-dependency-come-from.html
>
> Which sounds like the same error. A clue, perhaps?

We were seeing this at the plone conference in a buildout; at least
three of us. It would stall while making a develop-egg then fail with
the recursive error and : File name too long

Someone suspected archetypes.schemaextender, I was suspicious of
buildout.eggtractor injecting the egg names (in a loop) into buildout
the eggs it found to develop.

Removing the <name-of-egg>.egg-info from the develop egg(s) seemed to
fix it. Then something else failed, possibly unrelated. Then I didn't
have another chance to look at it.

At least two of the three people I am sure had the same error (and
partial fix) were on OSX 10.5.x

That is all the details I have....

~ro

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

smime.p7s (3K) Download Attachment

Re: Grok documentation review request

2008-10-10T19:38:53Z

Hello, I've added you to the Documentation group, so you should be
able to publish and edit published docs now by yourself.

However, I also made some edits to improve the text ...

... and I also updated the section on filenaming to mention that you
can't expose filenames with URLs that start with + or @ or contain /
in Grok by changing the example to use the default INameChooser
implementation. However, I haven't tested these changes, so please
feel free to correct them if you spot a typo or mistake!

It might also be nice to give an example of how to provide a Grok View
to override the default view supplied by the zope.app.file package.

Cheers,

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

Grok documentation review request

2008-10-10T15:03:47Z

Hello,

I wrote a small how-to in grok website.
If someone in the document team have time, please review it.

Best regards,
--
Yusei TAHARA <yusei@...>
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: grokproject error

2008-10-10T15:02:14Z

Hey,

> Setup script exited with error: Setup script exited with error: Setup
> script exited with error: Setup script exited with error: Setup script
> exited with error: Setup script exited with error: Setup script exited
> with error: Setup script exited with error: Setup script exited with
> error: Setup script exited with error:

No idea what the cause is, but I just read this:

http://blog.vrplumber.com/index.php?/archives/2204-Where-did-that-dependency-come-from.html

Which sounds like the same error. A clue, perhaps?

Regards,

Martijn

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

Moving a Zope3 app to Grok

2008-10-10T13:34:42Z

Hi All,

I am moving a Zope3 an application development platform to Grok in order
to provide an easier path for new developers to get started. This
application is in the very early stages of development so I do not
envision this being a big deal. Most of my code isn't even hooked up to
the Zope3 machinery yet.

The original project was started using zopeproject. But of course over
time I have added several dependencies in my buildout.cfg

I installed Grok and started the server and all was great.

I then did a clean svn export of the code and copied into a subdirectory
of the <project>/src/<project> directory. I didn't overwrite any of the
Grok config files. Actually there are a couple of subdirs but that
doesn't matter.

When I try to start the Zope server now i see that Martian is doing some
introspecting in the code it found. This is actually a good thing I
suppose. :-)

The server fails to start because it found that I am importing pyparsing
in one of my files. Now of course pyparsing is in my default eggs
directory.
Traceback is:

File
"/home/tim/.buildout/eggs/martian-0.11-py2.5.egg/martian/scan.py", line
191, in resolve
__import__(used)
File "/home/tim/grok/oship/src/oship/atbldr/adl_1_4.py", line 16, in
<module>
from pyparsing import *
zope.configuration.xmlconfig.ZopeXMLConfigurationError: File
"/home/tim/grok/oship/parts/app/site.zcml", line 4.0-4.27
ZopeXMLConfigurationError: File
"/home/tim/grok/oship/src/oship/configure.zcml", line 6.2-6.27
ImportError: No module named pyparsing

*******************************************************************

My real question is; is there an "automagic" way to do this merge?
Maybe some kind of analysis script I do not know about yet? Or is this
just going to be a tedious hand editing process for the buildout.cfg and
ZCML files?

Thanks,
Tim

--
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Skype ID == timothy.cook
**************************************************************
*You may get my Public GPG key from popular keyservers or *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************

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

signature.asc (196 bytes) Download Attachment

Re: generic directoryresource in grokcore.view

2008-10-10T01:09:46Z

On Fri, Oct 10, 2008 at 10:03 AM, Jan-Wijbrand Kolman
<janwijbrand@...> wrote:
snip
> (..) (in some case leading to hard to debug error messages) (..)

Uhm, this remark is not exactly correct - what I meant is that
sometimes you expect the "static" thing to point to a particular
directory of resources where it cannot find it. This is not really to
do with skinning, but with, for example, having a layout macro defined
in one package being used by templates in another package. Where the
layout macro then finds its resources can be confusing.

regards,
jw
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

generic directoryresource in grokcore.view

2008-10-10T01:03:51Z

Hi,

Grok views by default have access to a "static" directory for resources.
They're a special kind of the more general DirectoryResource feature of
Zope.

Since the resource "static" is always registered for the IDefaultBrowser
layer and I wanted to be able to skin resources too (in some case
leading to hard to debug error messages) I thought it would be nice to
have the more generic DirectoryResource feature available in Grok too.

I'm working on implementing the more general 'DirectoryResource' on a
branch of grokcore.view:

http://svn.zope.org/grokcore.view/branches/jw-generic_directory_resource/

I still need to add functional tests though, esp. concerning skinning.

Questions:

1) Do people feel this is useful to intergrate in grokcore.view?
2) Could someone have a quick look at the implementation?

kind regards,
jw

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

Re: grokproject error

2008-10-09T08:44:26Z

With a new virtualenv I now got this error:

Setup script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: Setup script exited with error: Setup
script exited with error: /tmp/easy_install-06iNh-/PasteDeploy-1.3.2/
temp/easy_install-SIRxj5/Paste-1.7.1/temp/easy_install-tqaOUZ/
PasteDeploy-1.3.2/temp/easy_install-fwWmV_/Paste-1.7.1/temp/
easy_install-hRiedb/PasteDeploy-1.3.2/temp/easy_install-vptgQQ/
Paste-1.7.1/temp/easy_install-Pd17pD/PasteDeploy-1.3.2/temp/
easy_install-PaGlk3/Paste-1.7.1/temp/easy_install-gqkBfv/
PasteDeploy-1.3.2/temp/easy_install-EsPAve/Paste-1.7.1/temp/
easy_install-6EAaJ6/PasteDeploy-1.3.2/temp/easy_install-_GvVe5/
Paste-1.7.1/temp/easy_install-NDSz7a/PasteDeploy-1.3.2/temp/
easy_install-LvWgo4/Paste-1.7.1/temp/easy_install-kOU1pw/
PasteDeploy-1.3.2/temp/easy_install-rJ9STs/Paste-1.7.1/temp/
easy_install-2SfUEc/PasteDeploy-1.3.2/temp/easy_install-UPhWS3/
Paste-1.7.1/temp/easy_install-Acofjj/PasteDeploy-1.3.2/temp/
easy_install-nZFZm8/Paste-1.7.1/temp/easy_install-WTrFSd/
PasteDeploy-1.3.2/temp/easy_install-FRvdma/Paste-1.7.1/temp/
easy_install-t7kf2j/PasteDeploy-1.3.2/temp/easy_install-NLDDNW/
Paste-1.7.1/tests/urlparser_data/find_file/dir with spaces/test
4.html: File name too long

This is on Mac OS X.

juh
--
Business: http://hasecke.com --- Private: http://hasecke.eu --- Blog:
http://www.sudelbuch.de --- History: www.generationenprojekt.de ---
Europe: www.wikitution.org

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

smime.p7s (3K) Download Attachment

Re: grokproject error

2008-10-09T07:21:59Z

Previously Philipp von Weitershausen wrote:

> El 9 Oct 2008, a las 15:49 , Jan Ulrich Hasecke escribió:
> > Am 09.10.2008 um 14:33 schrieb Philipp von Weitershausen:
> >>> No module named schemaless
> >>> This is an old acquaintance.
> >>
> >> Yes. You probably still have an older version of ZConfig sitting in
> >> your Python's site-packages. Try creating the virtualenv with
> >>
> >> virtualenv.py --no-site-packages
> >
> >
> > I did this, but maybe it is due to the fact that in this virtualenv
> > I already created a Plone installation.
>
> Quite possibly.
>
> > Not too familiar with virtualenv, the question for me is. Must I
> > have one virtualenv for only each zope instance?
>
> You don't *have to*, but it doesn't hurt, either. Creating virtualenvs
> is cheap. In this case, it would definitely have been a good idea due
> to the suspected influence of that Plone installation.

I don't see how a Plone installation can inject a ZConfig in the
environment for grok though. Plone's ZConfig is contained inside the
Zope2 instance which grok won't see.

Wichert.

--
Wichert Akkerman <wichert@...> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: grokproject error

2008-10-09T06:55:21Z

El 9 Oct 2008, a las 15:49 , Jan Ulrich Hasecke escribió:

> Am 09.10.2008 um 14:33 schrieb Philipp von Weitershausen:
>>> No module named schemaless
>>> This is an old acquaintance.
>>
>> Yes. You probably still have an older version of ZConfig sitting in
>> your Python's site-packages. Try creating the virtualenv with
>>
>> virtualenv.py --no-site-packages
>
>
> I did this, but maybe it is due to the fact that in this virtualenv
> I already created a Plone installation.

Quite possibly.

> Not too familiar with virtualenv, the question for me is. Must I
> have one virtualenv for only each zope instance?

You don't *have to*, but it doesn't hurt, either. Creating virtualenvs
is cheap. In this case, it would definitely have been a good idea due
to the suspected influence of that Plone installation.

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

Re: grokproject error

2008-10-09T05:42:42Z

On Oct 9, 2008, at 8:23 AM, Jan Ulrich Hasecke wrote:

> While installing a new grokproject with 0.14 in a virtualenv I got
> this error:
>
> While:
> Installing.
> Getting section app.
> Initializing section app.
> Loading zc.buildout recipe entry zc.zope3recipes>=0.5.3:application.
>
> An internal error occured due to a bug in either zc.buildout or in a
> recipe being used:
>
> ImportError:
> No module named schemaless
>
> This is an old acquaintance.
>
> juh

IIRC this happens when you have an oldr version of Zope3 on your path.

Did you use the --no-site-packages flag when creating the virtualenv

~ro

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

smime.p7s (3K) Download Attachment