P
Peter Judge
Guest
Since you can dynamically create widgets in ABL easily enough, would you consider storing the UI metadata somewhere? XML, JSON, db tables are all options. There’s code that shows doing this in Dynamics - github.com/.../rydynvcroi.i ; this is included in github.com/.../rydynviewp.p . If you want a wizard-style UI, then you can should have one window per ‘function’ (with read/write data). Once you have those pieces you can stich them together in multiple windows or in a single tabbed container or even a treeview potentially. I’d think that you always want some form of controller for the whole wizard flow – and that can then deal with hiding/view/kill/launch of the child frames (windows, tabs, etc). The controller can be a simple .P – it doesn’t have to be visual itself. The challenge is scope, I think. How complex and/or generic and/or extensible do you need this to be? Also, do you need a Windows/desktop UI? Can you do it via Web or API?
Continue reading...
Continue reading...