From: Nando D. <na...@de...> - 2011-05-08 07:39:30
|
> A) Allow a SQL template to be associated with any type of object, > not only tables (allow collections and database nodes as well) > (partly done). - Add overrides of getTypeName() for > "TABLE_COLLECTION" and the like. - Split conf files: template > caption, menu position and object name/type filter should go with the > template in a read-only .conf file, persistent params should go in a > different .conf file in some user-writable folder. - In any case stop > writing .conf files in the template folders, which may not be > writable. Done. > B) Streamline default/sample templates currently provided under > sql-templates, and have the menu contain user templates as well. Done. > G) Support non-SQL templates for database-driven code generation. > Actually already supported in practice, just needs to be made > easier. - Allow other file extensions (at least .txt or anyway a > single extension that means "not SQL"; maybe .template?). Done. Still TODO for this release: C) Create documentation about the available template commands and their params, for different types of templates (at least SQL templates). - Basic command documentation is currently in the source code. -- Nando Dessena |