ArchGenXML thought

Hi,

I am starting to use ArchGenXML quite a bit. I'm quite keen on it's  
nurturing of best practices through constraints in the way various  
functionality is implemented. Coming from writing plenty of pure Zope  
products in the days before plone and then hand coded plone products  
as this has made ground, I'd like to really push consistency through  
my coding that follow best practices.  In this guise I would like to  
add support for building CMFFormController scripts. Since the  
ArchGenXML/UML modelling environment includes GUI pieces such as the  
<<action>> and <<view>> stereotypes, it might be nice to be able to  
represent all one's logic within that same modelling environment,  
including the chains through .cpt .cpy and .vpy defined by their  
associated .metadata files. I guess there could be a few flavours of  
development:

1) at least produce .cpt .cpy and .vpy and associated .metadata   
files with enough information that warnings are issued in the event log

2) define the above and expose the .metadata files so at least we can  
see them all in one environment

3) use state diagrams to define the .metadata chains

This is just my guess; but it is something I wouldn't mind implementing.

Of course there is this 'genesis' product which will at some point be  
the preferred method, perhaps I should be offering to contribute  
there. Personally, from a production environment mode I'll be  
following Archetypes in to Zope 3, but from an interest point of  
view, I have Zope 3 up and always keen to get my head around more of  
that.

cheers
Matt



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642