Am Mon, 09 Mar 2009 09:17:35 +0900 schrieb Martin Aspeli:
> Jens W. Klein wrote:
>
>> And last but not least: Like in past any help is very appreciated!
>> Contact me (jensens) or Robert (rnix) at IRC (#plone, OPN/freenode) for
>> more info on how you can help.
>
> This is great news! Thanks for picking this up - it is long overdue, and
> not a small task!
Indeed, but we start with manageable amount of work. After this first
step AGX will evolve, then we may refactor agian. Important is to chnage
the architecture - and keep it simple.
> Could we maybe rename it?
No. And a deny any naming discussion. I better put my energy in
developing AGX than in renaming it.
> Once upon a time, we called this 'genesis'.
Genesis was a complete different idea: Genesis followed the idea of model-
tranformation.
> What happened to that?
Indeed a good question with a simple answer: It was too complex. A
project doesnt make much sense if an average programmer needs 3 weeks to
read about concepts of model-tranformation and into frameworks used (even
if Coral is still a very good base).
> :) ArchGenXML is a pretty terrible name, because
> (a) it doesn't generate XML, it reads XML and (b) it doesn't work only
> with Archetypes. If we're no longer calling it 'genesis', how about just
> using the well-known acronym, 'AGX'?
The official name will be still ArchGenXML and we will use as often as
possible the acronym AGX (so done already in Archetypes SVN). Also the
namespace for eggs is archgenxml for the core and agx.* for all addons,
such as the generators.
> Also, I am very interested in having this stuff work with non-Archetypes
> (Zope 3 style) content and other schemata. That basically means we need
> to be able to describe a schema using zope.schema.
Exact. After the refactoring settled down the goal is to exchange the
archetypes generator or the other generators. For 3.0 our goal is to make
it work again, prepared for changes. In 3.1 then we may have it fully
pluggable.
> I've created a package called plone.supermodel which can do two-way
> (read/write) XML representations of an interface with zope.schema
> fields. This is used in Dexterity to support certain use cases. One of
> those uses cases was always meant to be code generation. If you have an
> XML file called myschema.xml, then you can do:
[.. details ...]
> The point of all this is that zope.schema is the de-facto way to
> describe any "schema" *except*, of course, Archetypes schemata. For
Indeed.
> example, using the newly-developed plone.app.memberschema (which builds
> on ore.member), you can get custom member preferences forms and custom
> member schemata based on zope.schema easily. I also hope that the very
> new plone.registry will evolve into something of a standard place to
> store configuration settings, and again it descries its records using
> zope.schema.
Sounds good.
> Thus, I think that this AGX replacement needs to think of zope.schema as
I dont think its an AGX replacement. AGX deals with having a graphical UI
(UML) to visualize complex structures and to lower the barrier for non-
programmers. As far as I understand Supermodel is more about having a XML
and maybe TTW experience for single flat datastructures.
Greetz, Jens
--
Jens W. Klein, BlueDynamics Alliance,
http://bluedynamics.com------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H_______________________________________________
Archetypes-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/archetypes-users
