gmane.comp.web.zope.grok.devel

grokui.admin pack

Jasper Spaans — 2008-12-02T23:19:43

Hi Uli, I created a zodb pack thing for grokui.admin on a branch[1], can you take a look at it and tell me if it is ready to be merged into the trunk? Groet,

Grokker to remove development code?

Sebastian Ware — 2008-12-02T15:02:41

I often have the odd class here and there that is mainly intended for development purposes. It would be great if I could mark them somehow in order to exclude them from being registered on the production server. Could this be easily achieved with a custom grokker? Is there any other best practice for this use case? Mvh Sebastian

meet the Grok 1.0 release team

Martijn Faassen — 2008-12-02T12:51:26

Hi there, Since people volunteered (thank you!) I put together a list: Release manager - Jan-Wijbrand Kolman JW has been doing this for a while, so this should go well. I'll assist him in this. We'll tweak the list of release dates as we go forward. Documentation release manager - Carlos de la Guardia I've boldly put Carlos in charge of this, as I know he's very interested in our documentation efforts. Carlos, you should definitely seek the help of Kevin Teague as he's done a lot for our website and documentation efforts. Uli Fouquet has also done a lot of work surrounding the Sphinx tools to generate our official docs. Bug manager - Todd Matsumoto I know Todd from Infrae. Todd, your job is that our launchpad bug list is complete (given what goes on here on grok-dev and whatever else comes up), and to monitor what these bugs actually are. If any of them look important to you (or you're told by the devs that they are), I'd be good if you gave us a, say, weekly update email with the status. Todd, I think we still need to give you access to the Grok launchpad, right? PR lead - Jan Ulrich Hasecke Jan Ulrich has a lot of PR experience and has been involved in Grok for a long time. I'll help Jan Ulrich flesh out the technical details of our PR announcements. We'll do our best together to communicate the Grok vision to the world. Docstring project - Brandon Craig Rhodes Brandon is going to make sure our grokcore.* and grok and martian codebases are supplied with copious docstrings. General nag - Martijn Faassen I'll nag everybody to make sure things keep making progress and I'll help with cooperation. My hope is that I don't need to do anything. :) Others not in this list: please do volunteer and don't assume we'll do everything. The people in this list need all the help they can get! Regards, Martijn

About plugged templates... bug or coming soon feature??

Santiago Videla — 2008-12-01T18:03:25

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

Problems serving iepngfix.htc for transparent PNG in IE6

Sebastian Ware — 2008-12-01T16:38:13

I need to use the PNG-transparency fix which involves using a .htc file that is executed by IE5.5&6. I want to place iepngfix.htc in the static folder in order to avoid having to create a specific rewrite rule for nginx. However, I have been trying to get this to work and it seems as though Grok won't deliver the .htc-file out of the static folder in a way that works with IE. Question: 1 Has anyone succesfully used the iepngfix.htc solution with Grok? 2 How did you do it? Mvh Sebastian

a Grok 1.0 release plan

Martijn Faassen — 2008-11-28T16:08:29

Hi there, I think we should consider calling the next release of Grok Grok 1.0. I would like to put us through an alpha and beta phase however, for two reasons: * we have a number of potentially disruptive changes we'd like to get some feedback on before we release. * 1.0 pre-releases for 1.0 are good marketing. We should announce these loudly to get people to think about Grok. The bigger changes I'm aware of are: * new grokproject that uses paster and WSGI. This is done, but needs to be tested heavily. Existing documentation needs to be modified and we need 'best practices' documentation that describe how you'd actually use all the WSGI goodness in your application. This change is by far the biggest one to land in a 1.0 release. Opinions on how to manage this? * grokcore.viewlet extraction - the extraction is done but the core isn't modified yet, correct? Sylvain, what's the status of that work? * refactoring grokcore.view to support improved view inheritance. JW and I have been working on this. I propose the following release plan: monday december 15: Grok 1.0 alpha Features: all of the above. Documentation doesn't need to be ideal yet for WSGI, but basic tutorial and dev notes should have been adjusted. wednesday january 7: Grok 1.0 beta Features: improved documentation, bugfixes based on issue tracker and alpha feedback. wednesday january 21: Grok 1.0rc1 release Features: documentation on grok.zope.org is up to date with 1.0 stuff. This will be identical to the release if we can get away with it. wednesday january 28: Grok 1.0 release Hopefully practically identical to rc1. We will then continue with Grok 1.x development - things that I want to publish soon is megrok.rdb and the hurry.resource javascript/css resource handling framework. We need volunteers in various roles: * release manager. I'm hoping JW will step up again in this role. * documentation release manager: I'd like a separate role where someone prepares the documentation on grok.zope.org and grok/trunk/doc for the release. This would be mostly a documentation editing role. * bug manager. I'm hoping someone will step up who watches the mailing list, irc, and makes sure we have bug reports in launchpad, and then shepherds the developers to actually do something about the bugs so we can close them. * PR lead: It'd be great if we had someone to write press releases and send them to various places. I volunteer in the role of General Nag during the release process to make sure everything stays on track. :) Feedback? Opinions? Changes to the release plan? Some inside information for those who read as far as this: a small group is also going to gather in late january at my place to consider larger low-level changes that I'll dub "Grok 2.0". We'll do our best to see about introducing these changes gradually in Grok 1.x releases instead, though, but the idea is to open up the floor for some radical rethinking of some low-level bits to make the insides of Zope 3 and Grok simpler and easier to understand. Less firmly planned is that we're also hoping to gather in a bigger sprint sometime next year. Regards, Martijn

Changing the name of a deployed application

rmoskal — 2008-11-26T22:52:37

I'm in the middle of deploying my first grok application to a production box. I've been letting the users work on another machine for the last few weeks, under a deployed app named "beta". I can move the app to the production box no problem, and the beta app is nicely deployed. But now I want to change the app to something likee "prod" or probably something more descriptive. Is there anyway I can change the name of a deployed app? Thanks and regards, Robert Moskal

Plugging new template language

Santiago Videla — 2008-11-26T15:56:02

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

Bike hero

Peter Bengtsson — 2008-11-21T14:29:35

The next time we have a guitar hero sprint (aka. grok sprint) I want to try the bicyle level http://www.break.com/index/bike-hero.html

regarding gadfly database

gaurav kashyap — 2008-11-20T10:59:52

Hi all, I am using zope. Wherein using some application i can create database ,then tables and i can enter the data into those tables.These transactions appear in mysql(when i see the databases). There is a gadfly folder in var in zope instance where some files are created corresponding the above database creation. What i want to do now is:- I already have some mysql database and i want to use it in the zope application(not like creating a database and then tables and so on like above.) How can this be achieved Any suggestions.

martian scan "bug" (feature?)

Chris McDonough — 2008-11-19T13:53:24

When martian scans packages (via the ModuleGrokker), eventually it winds up scanning modules that are defined via .pyc and .pyo file representations that do not have a corresponding .py source file. This, at least in my configuration, leads to errors because these are typically modules left over after, e.g. a module rename, where the "old" .pyc file sticks around even though its source file has changed names and has new content. I *think* what I'd like to do is change martian to (either unconditionally or optionally) skip modules that only have a .pyc or .pyo representation without a corresponding .py source. Below is a strategy to do so, if folks agree. One strategy to do so would be to use the "inspect.getsourcefile(module)" in places that try to use "dir(module)" to obtain a list of members of a module. For example, we might change ModuleGrokker's "grokkers" method to do: def grokkers(self, name, module): grokker = self._grokker # get any global grokkers for t in grokker.grokkers(name, module): yield t # try to grok everything in module if inspect.getsourcefile(module) is None: raise StopIteration for name in dir(module): The inspect.getsourcefile trick works as so: With module foo1.py: import foo2 import inspect print 'sourcefile ', inspect.getsourcefile(foo2) With module foo2.py print 'foo' If you run foo1.py via "python foo1.py" when foo2.py exists and no foo2.pyc exists, we get: foo2 sourcefile /Users/chrism/projects/martian/src/martian/foo2.py If you run foo1.py via "python foo1.py" when foo2.py does not exist but foo2.pyc does exist, we get: foo2 sourcefile None If you run foo1.py via "python -O foo1.py" when foo2.py exists and no foo2.pyo exists, we get: foo2 sourcefile /Users/chrism/projects/martian/src/martian/foo2.py If you run foo1.py via "python -O foo1.py" when foo2.py does not exist but foo2.pyo does exist, we get: foo2 sourcefile None Comments? - C

subdirectories of static do not usegc.v.component.DirectoryResource

Jan-Wijbrand Kolman — 2008-11-18T22:00:31

Hi, grokcore.view.component implements DirectoryResource and DirectoryResourceFactory classes, subclassing those from zope.app.publisher.browser.directoryresource for use in the "static" directory resource available in views. It does this for two reasons: 1) To override the security checker on the DirectoryResource instances and 2) to override the resource factories for *.pt and *.html files. However, the resource factory for *subdirectories* of the static directory is not overriden and thus for these subdirectories the z.a.p.b.directoryresource.DirectoryResource implementation is used. Fortunately, there's a recent release for zope.app.publisher that provides hooks for properly overriding these factories and with these hooks this bug is easily fixed. I'd like to update the version of zope.app.publisher in grokcore.view from the current 3.4.1 to the recently released 3.5.1 version to be able to checkin the fix. The tests for grokcore.view do pass with this version, but what possible implications should I look for? How do we decide to up the version requirement of a dependency? regards, jw

z3c.autoinclude hiding configuration conflict errors(?)

Jan-Wijbrand Kolman — 2008-11-18T16:18:16

Hi, Today I noticed something strange. z3c.autoinclude appears to swallow ConfigurationConflictError errors. Say I have a grok project (created with grokproject-0.9) called foobar. In the app.py that is created I add a skin definition like so: class ISomeLayer(grok.IBrowserRequest): grok.skin('foo') Then I create, again with grokproject, a project called qux. In the app.py modules of the qux project I also add a skin definition, *identical* to the one I added in foobar's app.py. Then I add foobar as a dependeny to qux, by way of qux's setup.py and develop directive in qux's buildout.cfg. Grokproject generated a configure.zcml for qux like so: The important part here is the directive that will make sure the configure.zcml of foobar is included and thus that foobar is grokked too. Now, running "qux/bin/zopectl fg" starts Zope with no complaint. *However* zope *should have* complained, as registering multiple skins with the same name should really raise a ConfigurationConflictError. And indeed, if you'd change qux's configure.zcml to... ...trying to start zope with "qux/bin/zopectl fg" won't work, indeed complaining with a configuration conflict! I did have a quick look into z3c.autoinclude but cannot find an obvious culprit... Anyone an idea here? Who wrote z3c.autoinclude? Can he/they help? regards, jw

Grokcore.viewlet released.

Sylvain Viollon — 2008-11-17T13:17:13

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

ImportError: No module named schemaless

Sven Dehmlow — 2008-11-16T20:35:42

Hi, I'm experiencing trouble while creating a new grok project. The error message is attached below. After googling a bit, I found a bug report for ubuntu (https://bugs.launchpad.net/zc.buildout/+bug/133462). The last advice in this report is to remove zope3 - however, I guess I need zope3 to run grok ... ;) Well, is there already a known fix for this issue? Thanks in advance Sven error message: sven< at >grisu:~/grok$ grokproject Sample Enter user (Name of an initial administrator user): grok Enter passwd (Password for the initial administrator user): Downloading info about versions... Downloading zc.buildout... Invoking zc.buildout... Develop: '/home/sven/grok/Sample/.' Updating eggbasket. 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: Traceback (most recent call last): File "/tmp/tmpou7FmY/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1477, in main File "/tmp/tmpou7FmY/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 346, in install File "/tmp/tmpou7FmY/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 857, in __getitem__ File "/tmp/tmpou7FmY/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 938, in _initialize File "/tmp/tmpou7FmY/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 901, in _install_and_load File "/usr/lib/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resources.py", line 277, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resources.py", line 2180, in load_entry_point return ep.load() File "/usr/lib/python2.4/site-packages/setuptools-0.6c9-py2.4.egg/pkg_resources.py", line 1913, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "/home/sven/.buildout/eggs/zc.zope3recipes-0.7.0-py2.4.egg/zc/zope3recipes/recipes.py", line 21, in ? import ZConfig.schemaless

Zope Objects Question

thorstenz — 2008-11-16T09:38:00

Hi. I am a bit confused in how to organise zope objects, so I can implement the following (and I hope somebody can help me with this): I have a kind of a poll. I want questions for this poll being editable (at any stage of the poll, even while it is running), therefore: Question(grok.Model), which I store in a Container, Questions(grok.Container) Then I want different containers where I select, which questions of the whole Question-Container are relevant for this container, I thought, this could be Poll(grok.Container) containing references to the Question-Container, I selected. And on the top of the Poll(grok.Container).QuestionReference(grok.Container???) I would like the answer: Choices(grok.Container) Again: Many Polls have many Questions within that Poll each of the many questions has many choices questions are always the same. If they change, they change in past, present and future polls. I don't know, how I can achieve this QuestionReference. Have you any clues? thx, thorsten.

problem with zope.app.testing during installation Grok on Windows XP

Roger Erens — 2008-11-12T22:54:53

I'm trying to install Grok on a freshly installed Windows XP Home system. When running the grokproject command, I get an error with zope.app.testing. Two others have reported this error to me as well. Any advice? IGetting distribution for 'zope.app.testing==3.4.3'. Traceback (most recent call last): File "", line 1, in File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 1671, in main File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 1659, in with_ei_usage File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 1675, in File "c:\python25\lib\distutils\core.py", line 151, in setup dist.run_commands() File "c:\python25\lib\distutils\dist.py", line 974, in run_commands self.run_command(cmd) File "c:\python25\lib\distutils\dist.py", line 994, in run_command cmd_obj.run() File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 211, in run File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 427, in easy_install File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 476, in install_item File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\c ommand\easy_install.py", line 626, in install_eggs File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\a rchive_util.py", line 67, in unpack_archive File "C:\virtualgrok\lib\site-packages\setuptools-0.6c9-py2.5.egg\setuptools\a rchive_util.py", line 174, in unpack_tarfile File "c:\python25\lib\tarfile.py", line 1148, in open return func(name, "r", fileobj) File "c:\python25\lib\tarfile.py", line 1213, in gzopen gzip.GzipFile(name, mode, compresslevel, fileobj)) File "c:\python25\lib\tarfile.py", line 1192, in taropen return cls(name, mode, fileobj) File "c:\python25\lib\tarfile.py", line 1084, in __init__ self.firstmember = self.next() File "c:\python25\lib\tarfile.py", line 1808, in next buf = self.fileobj.read(BLOCKSIZE) File "c:\python25\Lib\gzip.py", line 227, in read self._read(readsize) File "c:\python25\Lib\gzip.py", line 279, in _read uncompress = self.decompress.decompress(buf) zlib.error: Error -3 while decompressing: invalid literal/lengths set An error occured when trying to install zope.app.testing 3.4.3.Look above this m essage for any errors thatwere output by easy_install. While: Installing eggbasket. An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "c:\docume~1\roger\locals~1\temp\tmpu8be5d\zc.buildout-1.1.1-py2.5.egg\zc \buildout\buildout.py", line 1477, in main File "c:\docume~1\roger\locals~1\temp\tmpu8be5d\zc.buildout-1.1.1-py2.5.egg\zc \buildout\buildout.py", line 462, in install File "c:\docume~1\roger\locals~1\temp\tmpu8be5d\zc.buildout-1.1.1-py2.5.egg\zc \buildout\buildout.py", line 1060, in _call File "c:\eggs\z3c.recipe.eggbasket-0.4.0-py2.5.egg\z3c\recipe\eggbasket\downlo ader.py", line 81, in install os.unlink(temp_tarball_name) WindowsError: [Error 32] Het proces heeft geen toegang tot het bestand omdat het bestand door een ander proces wordt gebruikt: 'c:\\docume~1\\roger\\locals~1 \\temp\\tmpdx5f75'

slideshare.net

Jan Ulrich Hasecke — 2008-11-08T10:35:25

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

Conflict between megrok.kss and megrok.form?

Douglas Cerna — 2008-11-07T20:43:21

Hi everybody. I've been trying KSS and I like it :) I started with the example in the "Adding AJAX to Grok with KSS" tutorial on grok.zope.org (http://grok.zope.org/documentation/how-to/adding-ajax-with-kss-to-grok) and it worked well. (I added megrok.kss to my setup.py and run buildout for this) But then I added features like dates and tried to use the zc.datetimewidget for my date fields. I know megrok.form gives this widget in an easy way. So I added megrok.form to my setup.py too and run buildout. And then my kss functionality stop working :( telling me: exceptions.TypeError: There isn't enough context to get URL information. This is probably due to a bug in setting up location information. I googled for an answer and the closest I got was: http://mail.zope.org/pipermail/grok-dev/2008-June/005744.html Then I tried to install only zc.datetimewidget the same way megrok.form does it (using directives in my configure.zcml), but I get an configuration conflict error when I include the zc.datetimewidget's overrides.zcml file. Does anyone know how to solve this problem? Maybe using the kss svn checkouts will solve this but I don't know how to do it. Thanks. Douglas "... allí es cuando te das cuenta que las cosas malas pueden resultar bastante buenas..." - Lionel Messi Por favor, evite enviarme adjuntos de Word, Excel o PowerPoint. Vea http://www.gnu.org/philosophy/no-word-attachments.es.html

Problem with z3c.autoinclude of eggs in the Productsnamespace

Vincent Fretin — 2008-11-06T12:29:58

Hi, I have two eggs myproject.policy and Products.myproject. I use z3c.autoinclude in my plone buildout like this: [buildout] versions = versions eggs = [...] z3c.autoinclude myproject.policy develop = src/myproject.policy src/Products.myproject [versions] z3c.autoinclude == 0.2.2 [instance] zcml = z3c.autoinclude-meta myproject.policy If I put Products.myproject in eggs section. All works fine. But I don't want to put it in the buildout, but in setup.py of myproject.policy. In src/myproject.policy/myproject/policy/configure.zcml, I put: I want myproject.policy to depend of Products.myproject, so I put in install_requires=['Products.myproject'] in src/myproject.policy/setup.py I start the zope instance. The product myproject is shown and installable in Plone control panel. But doesn't appear in ZMI Control_Panel/Products, the result is that factories for the various types in myproject product are not created. I think z3c.autoinclude blocks the normal Five machinery to take place. Any idea of the problem? Maybe you can just deactivate autoinclusion of eggs in the Products namespace in the next version?

Deploying into production - site.zcml with credentials

Ivo van der Wijk — 2008-11-06T09:30:50

Hi, My customer wants to deploy my grok application into production. I've provided a rather default buildout.cfg with a admin/admin username/password for a main manager account. Of course my customer wants to change this. However, as soon as I provide an update, any changes to buildout.cfg or site.zcml will be undone and the old 'admin/admin' u/p will be setup. I also can't provide a buildout.cfg without site.zcml credentials - you need them for the first time deployment. The only alternative option I can thing of is providing two buildouts, one with (for first time deployment) and one without site.zcml. How do you guys usually solve this problem? In the Zope2/Plone buildout world this is not an issue - there you only define a inituser which can be changed in the ZODB (acl_users) which buildout won't modify after updates. Regards Ivo