Back to start Norwegian version of the blog
In this blog entry I am writing of this project at work. To learn about Rich Clients I have created a demo-application which use a dojo BorderContainer to layout the application. A sample is shown below, it's ugly but the goal is to find out how a can assemble a portal like application, with a header area (green), a menu area(grey), a footer area (turkise) and the client area ( white).
I have set up a pub/sub topic message queue to have the different regions to communicate is a loose style. So if I clicks on a link in header area, there vil be loaded an appropriate menu in the menu area. And a click on a menu item, will load a module into client area. Every module is separate and is loaded as a URL i.e /module1/index.html, /module2/index.html or /module3/index.html.
In my demo-application, I have seen that publishing messages from the loaded client in /module1/index.html is received in the main application, and that listener displays a context menu in the menu area. So the messageing is working fine.
So then I need to find a best practice to create som page flow.
Many modules will probably have just one page witch displays som data and may edit data from that page. That can be solved by 'inplace' editing, I guess. But sometimes I just have to go through several pages to get my transaction done. I'm not quite shure of how to tink in there scenatios. Tips are appreciated.