First off, thanks for your elaborate answer and apologies for this long mail.
> If you prefer, we can discuss the details of this functionality > using my personal email. I'm fine with this public mailing list, as our discussion could help others if they try the same thing. So unless you have reasons not to, I'll continue the discussion here. > Could you please send me a brief description about your project and what are > you planning to achieve? I can, although I just realised that it's not really brief anymore :) I want to build a wizard-like, one-way workflow. I have uploaded scans of my mockup into that album: http://imgur.com/a/vM4mP Now to the actual description of those images: The program should start with step 0. Then the user can choose between one of two "paths" in the workflow: A1 or B1. let's skip path A, as path B is simpler and enough to understand what I mean. - B1 (3rd picture): * You can see that the tab has been added that wasn't there before. * Also, a "Back" button has been added. I guess it will be impossible to add a button into the tab-bar, but maybe I can somehow trick it into that, maybe using a fake plugin or whatever. * Note that it should only be possible to go back. When going back, it will be as in step 0 again, thus deleting the tab of B1. - B1->B2 (4th picture): * A progressbar and all calculations that are going on. * Would be nice if you wrote a quick wiki article on how to show (modal) progressbars, or is there any of the example plugins that does it? * this is just a step between B1 and B2, can be part of any of those, no need for a new plugin/tab. - B2 (5th picture): * Again, a new tab has appeared. "Wizard-like" because the next step is always dependent on what was chosen in the previous step. "one-way" because the user should always be able to go "back" and _only back_, back should delete the current tab. Or he can click onto the first tab ("home") which is like clicking back as often as possible, thus deleting all other tabs. I am aware that maybe not all of this is possible, this is just the ideal goal to work torwards. > For example, if the current step is Marching Cubes and the output is a > surface mesh, > depending on the number of components, next step can be a extract main > surface or go > directly to mesh editing. Yeah, that is good example. > it could be included in the GIMIAS-1.4.1 stable version. That sounds great, I would be very thankful for it :) > Related to workflow navigation, why don't you use the Workflow Navigation > widget? I hope you could see in my GUI mockup that there is not really a good place to put it. I will use it if there is no other choice though. > We could add a feature that hides the "future" steps of the workflow. That would be helpful. Also an option that "back" destroys the current step would be good. > You can also test another way to create a new plugin tab page is using plugin > perspective. I will play around with this idea, thanks. Regards, Lucas ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Gimias-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gimias-developers
