Steve McMahon wrote:
On Thu, May 29, 2008 at 3:37 AM, Daniel Nouri <[EMAIL PROTECTED]> wrote:
...
Propose: Add a section "Forms", pull out PloneFormGen, zope.formlib and
z3c.form out of the their current sections and put them all there, side
by side....
I see Daniel's point, and would go a bit further: I'd say that
PloneFormGen, per se, doesn't belong on a developer's tech list at
all. It's aimed at being a versatile tool for content managers and
integrators.
To be an integrator you have to get into the code. We are kidding
ourselves if we think otherwise. So this cheatsheet is really an
integrator cheatsheet. Its for people that want to put togeather
customized solutions and that in my experience involves combining off
the shelf products and custom code. Even doing themeing now involves
coding (bad but true).
So there is
- developers/integrators (we should call them developers. everyone else
does)
- end users
- core developers.
my 2c anyway.
However, adding new field and action types to PFG might be a very
reasonable topic, and is -- I think -- roughly on the level of
developing new content types with Archetypes.
______________________________________________________
Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
