Derek Richardson wrote:
Speaking for myself, I much prefer the textual genesis approach to agx.
Filling in Python in tagged values isn't my idea of a fun time. ;)
I haven't been following the Dexterity thread on plone-dev (too much
traffic!), so I don't know what it will eventually look like. But, there
is a good possibility that genesis will still be more efficient for
developers comfortable with text who don't want to write
lightly-customized boilerplate.
I think the DSL approach for Genesis is very interesting, though I'm a
bit worried at the prospect of relying on a parallel language being
maintained and kept up to date at all times.
Have you tried the ZopeSkel 'archetype' template and its local commands?
It's pretty nice to get the boilerplate done, and from then on the
Python you have to write is quite limited. That's not quite the same as
Genesis, of course.
My wish is/was that Genesis would provide a graphical editor that was
usable and slick. I don't know how far Vidar got with the Eclipse
Modelling Framework, though.
We also have genesis *now* - I don't know how far away 4.0 is, but it's
a while away, and, even once released, will take many of us a long time
to upgrade to it, if uptake on 3.0 is any indication of what 4.0 will be
like.
Dexterity probably won't be tied to 4.0 except in terms of focus and
effort. It's possible to build it today and release it as a set of
external packages for use with Plone 3.0. There's just a lot of work to
be done.
So, I think genesis fills an important niche, now and in the future. I
encourage you to keep working on it, if only for my sake. :) I'm
actually using quite a bit now.
Me too!
Derek, if you're using it, perhaps you could write a tutorial on
plone.org about how you use it?
In addition to the plea for continued development, I am stumbling across
a few minor things that I think need fixing. Do you mind if I check them
in? Or would you rather I create a 'derek-branch'? Currently, they are
tiny things (like changing the skin layer registration to all skins
rather than Plone Default, etc). I would, of course, create a branch for
anything bigger than a few line patch. And I'll accompany the ci's with
-m's that describe what I'm doing and why, so you can roll them back if
you disagree.
The typical policies for code in the Collective is:
- Fix bugs, but write tests for them
- Don't break any tests
- Use a branch for any refactoring that's more than just a direct bugfix
- Respect others who may be running from an svn checkout
- Respect the wishes of the maintainer - don't go changing things
without his/her involvement.
I'll let Vidar comment on Genesis in particular, though. ;-)
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
