[Grok-dev] Re: megrok.form 0.1
faassen at startifact.com
Tue Feb 26 10:15:32 EST 2008
Dirceu Pereira Tiegs wrote:
> Hi Martijn,
> On Mon, Feb 25, 2008 at 11:58 AM, Martijn Faassen
> <faassen at startifact.com> wrote:
>> Dirceu Pereira Tiegs wrote:
>> > Hello,
>> > I've just released megrok.form on cheeseshop, hope it helps someone:
>> > http://pypi.python.org/pypi/megrok.form/0.1
>> This is great news! Thank you! I hope to get to play with this soon; I
>> think some of this would be immediately useful in some of my work.
> Nice! :-)
I actually played with it a little bit yesterday to test the
z3c.autoinclude functionality. It works! Now to use megrok.form, you
just list it in your project's setup.py, rerun buildout, and off you go.
>> What are your plans for evolving this package forward? Any other things
>> you think would be good to add?
> Yes, there are some things (they're on TODO.txt), like:
> - Create a widget for zope.interface.schema.Time (based on
> - Create / find a field for Reference (take a look at zc.relation,
> zc.relationship and lovely.relation)
I've been doing a lot of work on this topic recently and have a
reference field implementation based on zc.relation (which is the most
recent incarnation). I'm not entirely satisfied yet with the approach
but will be pushing this to the outside world in the future so other
people can review it. The focus was to have a relation field that is
easy to use; I couldn't find an implementation of that exactly in the
[snip other projects]
I think this would be a great task for volunteers. Just finding an
existing widget and having it included in megrok.form is a reasonably
simple task. Writing new fields and widgets is harder, but we now have
some examples. Proposals and discussions please on this list!
>>> The source code is at http://svn.zope.org/Sandbox/dirceu/megrok.form.
>> > Should I move it do the root directory?
>> Yes, please do! It's good for it to have visibility for people browsing
>> svn.zope.org, and it also makes clear that other people are invited to
>> help out. If anyone has more ideas for what can be added, let's please
>> discuss it here.
> Done. :-)
More information about the Grok-dev