We fixed issues of configuration, improved the FlexTasks script and refactor the commands to support the nomenclature of the generated applications
Supports one-to-one, one-to-many and many-to-one.
In one-to-one there doesn’t work update (it doesn’t update the record ), we don’t know why. If someone kwons or wants to check it is going to be of grear help for us.
GFS supports validations in FrontEnd from Grails’ constraint
CRUD’s views are generated from Grails Domain Class definition.
Once, first compilation via FlexTasks done, it is possible to Import the project into FlexBuilder (or Eclipse + FlexBuilder Plugin to support Grails too), that’s because FlexTasks generates Eclipse/FlexBuilder configuration property files. Obviously, FlexTasks generates an index.gsp that wraps the swf too.
Tip: “In order to debug flex application from FlexBuilder, it is necessary to modify the access url –>Open Debug’s configuration Dialog –> uncheck “Use Defaults” and remove main.html of three configurations.
We could not find any file of configuration that contains these parameters, that’s why the tip.”
Project Source: http://plugins.grails.org/grails-flex-scaffold
For more information about the use of GFS visit Official Docs (User Guide, Examples)
Bug reporting and versions’ status http://jira.codehaus.org/browse/GFS
Comming Soon GFSv0.2, to see the roadmap