Documentation GUI generation with YAML: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
Line 16: Line 16:
* general functions go into a class derived from TFrmPetraUtils (eg. TFrmPetraModuleUtils)
* 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)
* manual code for a screen goes into a partial class (eg. PartnerEdit.ManualCode.cs)
* See [[Documentation YML for OpenPetra Forms]] for detailed documentation
* See [[Documentation YAML for OpenPetra Forms]] for detailed documentation


== TODO ==
== TODO ==
* short cut keys for menus
* short cut keys for menus
* programmatically add to menu (recent partners)
* programmatically add to menu (recent partners)

Revision as of 08:59, 17 July 2009

general documenation

  • TODO: XAML, YML

implementation

  • TODO: PetraTools, codegeneration
    • ymlparser
    • using templates
  • TODO: PetraForm, PetraModuleForm, etc

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)