Hi Ian,
There will be some guidelines in the new documentation, which is currently not yet available.
Here some very short tipps:
- Use an assistance class for each component, which should hold the current data and where you can place central methods. Placing methods in external classes is better than putting them into the component controller, because there is less overhead and more functionality (e.g. optional parameters and exceptions).
- Hold your current data in the assistance class and only put them into the context if needed (e.g. via supply functions).
- Call your business logic from the assistance class during event handling. Then you have the opportunity to do navigation or not depending on the output of the business logic.
- You could use any other class for this purpose, but the assistance class is easier, because it is instantiated by the framework and you can access it via wd_assist-> instead of wd_this->my_class-> .
- Do not create a model component, because this is just overhead and no advantage. In earlier states of the WD project, we thought, a model component would be a good idea, but we changed our minds
- Use context mapping, where it is needed, e.g. if you use the same context in different views.
- It is quite well to call the assistance class from the views.
- Be careful, if you store any references to component parts in your assistance class. Some references may change during runtime, especially those of context nodes placed in a deep hierarchy.
Hope this helps, and more tipps will follow in the documentation or weblogs.
Ciao, Regina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.