I'd think being able to name the tasks and have them generated discretely would be ideal. That way multiple combinations of them could be assemble din various menus (either manually or via generation) to suit different 'roles' of users
Patrik Nordwall wrote: > > In the gui meta model, both gui modules and tasks have a name. It is not > possible to assign this name from dsl right now. It should in theory be > possible to have several with different names for same backend > domainobject, but i'm only guessing, must be tried to understand the > implications. > > An alternative is to use the new feature of using non-persistent > valueobjects or DTOs in the gui, which Andreas has implemented recently. > > Then the services can expose different DTOs for different purposes. You > have to manually map DTOs to domainobjects in the services. Maybe this is > not what you are looking for, since it might result in a lot of > duplication if you only need to supress a few fields, but if you are > looking for completely different views it is a flexible solution. > > /Patrik > -- View this message in context: http://old.nabble.com/-Sculptor--Multiple-UI-tasks-per-%27task-type%27--tp28288008s17564p28326249.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
