Hey Matthew,

2012/7/11 Matthew Sherborne <[email protected]>:
> I've made an initial plan:
> https://github.com/matiu2/witty-codegen/blob/master/README.md

I believe this is really a good idea. Development often starts by
'copying' an existing project, and a code generator should be able to
do that better.

It will also save people time by setting a number of annoying things
correctly (build, deployment path structure, etc..).

Here are some of my suggestions, which mainly reflect preferences more
than anything substantial:

1) We tend to organize code in at least the following sub directories:

src/model (Model classes: business logic, storage, anything that is
not user-interface)
src/model/db (Dbo classes)
src/ui (User interface: widgets, main application, etc...)

2) c++-11 initially seems like the way forward (but be aware of compiler bugs)

3) layout style: there are use-cases for either desktop-like (W*Layout
based) or web-like (CSS based) layout, and they are often mixed. In
the end, this needs to be an option ?

4) gen form: instead of parsing the code, you could run a utility that
links against the code (or at least the model classes) and uses
Dbo-based introspection to derive the schema, or some other form. We
could even provide something in Wt::Dbo that dumps the model in some
standardized form, since a Wt::Dbo::Session has that information
internally.

I really believe that even with only a subset of your complete feature
list, such a tool would be very useful.

Regards,
koen

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to