Documentation GUI generation with YAML: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
No edit summary
Line 8: Line 8:
** using templates
** using templates
* TODO: PetraForm, PetraModuleForm, etc
* TODO: PetraForm, PetraModuleForm, etc
* see also [[Development with Code Generation]]


== current features ==
== current features ==

Revision as of 09:06, 17 July 2009

general documenation

implementation

current features

  • yaml file can inherit from other yaml files; eg. the menu structure can be inherited
  • conventions: user control types by prefix: TODO
  • the first panel, user control, tab page, group box will be the main content control
  • Menu/Toolbarbutton order: AlwaysLast
  • labels are automatically prepared for translation (Catalog.GetString)
  • general functions go into a class derived from TFrmPetraUtils (eg. TFrmPetraModuleUtils)
  • manual code for a screen goes into a partial class (eg. PartnerEdit.ManualCode.cs)
  • See Documentation YAML for OpenPetra Forms for detailed documentation

TODO

  • short cut keys for menus
  • programmatically add to menu (recent partners)