| Re: [riena-dev] Shared view between subapplications? |
| Hi Todd, you can do many things :-) - use the same view class in multiple assemblies but that is really a no-brainer :-) - create instances of the same assembly in multiple part of your application so an assembly is really something like a template a part of a navigation tree that is predefined and only when you create a navigation node, you can either use as parentType Id the one specified in the assembly or in some (or all) cases define depending on your code a different own. How is that done. Creating a new navigationId (and therefore a part of the tree structure) is either done by getNavigationNode().create(new NavigationNodeId("something"), new NavigationArgument(.....)), or by using the navigate method with the same argument. create just creates it, navigate also jumps there (activates it). The NavigationArgument is optional and can contain a parameter (any object that the target view controller can make sense of) and the parentTypeId (again optional). if the NavigationArgument has a parentTypeId the new nodeid (using the assembly definition from the extension) is created and added where parentTypeId defines it. So at runtime you will get this large DOM-like tree where you have application at top and below your subapplications, modulegroups, modules and submodules. The assemblys can be used like LEGO stone to add predefined subtrees anywhere into this large application model. The parentTypeId in the extension is the default but can be overwritten at runtime. Makes sense ? if not let me know christian Am 29.04.2009 um 16:28 schrieb Todd Lee:
|