Yeah I was going to say... not to be off topic :)
Couple of Quick Suggestions:
- *Best Practice Structure* - This may have more to do with the
sampleapplicationtemplate itself, but why not include the best practice as
the default build structure? That is to not have the config, controller, and
model exposed to the webroot by default? Instead move the views, css, etc
into it's own folder?
- *Prompt for ORM* - Prompt to see if the user wants to include a
database -> include transfer/reactor and only generate those settings in the
base setup.
- In our script we prompt for inclusion of specific actionpacks/helpers.
This is probably too specific for but it might be interesting to include
'import helpers from:' or import 'actionpacks from', but that's prob just
fluf.
After Project Build
Have a build script that would actually generate:
- New Controllers
- Switch settings for:
- orm development
- init=true
- debug
- scaffolding
- manually init true the project perform init=true (so you can have
eclipse auto-build when you save in controller/model folders) - this one is
especially useful
Thanks,
Roy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "model-glue" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/model-glue?hl=en
For more about Model-Glue, check http://www.model-glue.com .
-~----------~----~----~----~------~----~------~--~---
