Documentation GUI generation with YAML: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
No edit summary
(Replaced content with "Deprecated: this only applied to the winforms client")
Tag: Replaced
 
Line 1: Line 1:
== general documenation ==
Deprecated: this only applied to the winforms client
* TODO: XAML, YML
* see also [[Development with Code Generation]]
 
== implementation ==
* TODO: PetraTools, codegeneration
** ymlparser
** using templates
* TODO: PetraForm, PetraModuleForm, etc
* see also [[Development with Code Generation]]
 
== 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)

Latest revision as of 20:46, 11 May 2022

Deprecated: this only applied to the winforms client

Retrieved from ‘https://wiki.openpetra.org/index.php?title=Documentation_GUI_generation_with_YAML&oldid=4895’