[Grok-dev] progress on megrok.form
uli at gnufix.de
Wed Apr 29 12:13:26 EDT 2009
Santiago Videla wrote:
> I made some progress on megrok.form as we talked last week, you may
> want to take a look here:
Great, that you started that!
> I started with the z3c.widget issue and I think that it's almost
> fixed. But I found some other problems:
> 1. megrok.form depends on zc.datetimewidget and the last depends on
> zc.resourcelibrary. Using hurry.* to tinymce inclusion, there is a
> conflict between hurry.zoperesource and zc.resourcelibrary. I'm not
> css,... into megrok.form in order to use hurry.* ?
As supposed in another post I made a quick hack, converting
zc.datetimewidget to megrok.datetimewidget, which uses
hurry.zoperesource instead of zc.resourcelibrary.
The code (unreleased, of course) hangs around in
At least all original tests from zc.datetimewidget pass. But I would be
interested to know what happens, if you use this instead of
zc.datetimewidget with megrok.form (also skipping other includes of
To check this, you can do the following:
1) Checkout the sandbox code in the root of your local megrok.form.
2) Add 'megrok.datetimewidget' to the development line in buildout.cfg
3) Replace mentions of 'zc.resourcelibrary' with 'hurry.zoperesource'.
4) Replace mentions of 'zc.datetimewidget' with 'megrok.datetimewidget'.
5) Add 'megrok.datetimewidget' as a requirement in setup.py
6) Rerun buildout
Maybe you can even use ``includeDependencies`` in the configure.zcml
(that would be great) and skip all those nested includes.
I am almost sure, there are still some things to do in this
quick'n'dirty megrok.datetimewidget implementation.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090429/1d1e160a/attachment.bin
More information about the Grok-dev