We are starting to evaluate our efforts to migrate to Connect Edition and with no "Menus" and ultimately Tasks being phased out, the question arises, "What does Bentley consider to be the Connect replacement for Tasks?"
There is only so much room in the ribbon. We used to use the Bill Steinbock MDL Barmenu for selecting items to draft. Sometimes, these were similar to a a settings manager item, but other times they were more like a task that was linked to a settings manager. And we had a unique barmenu mdf file for nearly every file/model type we had in our standards. I experimented making tasks from these and found that I ended up with many many task toolboxes. Far more than I think would be feasible to put into the ribbon.
And we tested enabling Tasks in Connect, but we actually will be using Open Road Designer and when you enable tasks in ORD, it breaks the Workflow menu, where a number of the workflows disappear and the only way to restore them is to disable tasks. If this bug can be fixed, I'd be content using tasks, as they look a lot like Tool Palettes in AutoCAD so I don't have to train a new "convert" how they work. As far as the bug is concerned, its been reported and supposed to have a defect report, but a number of new releases have been issued (more than 4) and it is still broken.
Basically you're stuck with the ribbons unless you start working on other interface options like screen menus, vb apps etc. I have a similar issue with an extensive build I just can't deliver as effectively using the ribbon interface. an interface I have issues with in the first place. One option I have looked at which we will use to some extent is to use named expressions to control turning on and off different ribbons. It's an easy way to deliver discipline ribbons like we used to do with tasks, but it's far from being as neat.
I agree a move to new interface can easily be the most complex and painfuil part of the migration, especially when a former customization is complex.
I do not know ORD well enough to evaluate how and why tasks break its GUI, but to use tasks during the migration is not bad idea. But at the same time you should be aware tasks were added during beta testing as "temporary solution" and as far as I know there is no public plan how they will be supported and when they will be removed from MicroStation. So to think about and to be prepared for ribbon should be planned even when tasks are enough for the first migration step.
I agree with Bear that there are more options in MicroStation CONNECT Edition GUI and it's not about ribbon only. As Bear wrote, you can customize and combine:
I see several "GUI migration problems":
Personally I know users who are happy with ribbon, but they often invested substantial time to understand how new GUI works and to customize it. But I am also aware of some workflows and requirements, where best practice or commonly accepted solution has not investigated yet.
Labyrinth Technology | dev.notes() | cad.point
Took me a bit to give them a go, but these days I use Named Expressions extensively. Well worth putting the effort in to have a play and see how they work. These might help as well:
What do you show and hide based upon Named Expressions?
I have looked at these, but ran into an issue. In our barmenu based workspace, we allow users to manually swap to another barmenu after the default one opens for a particular file type. I could not determine if you could provide users with a way to show or hide ribbon tabs on demand.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
caddcop said:What do you show and hide based upon Named Expressions?
well ... anything :-)
You can use from top to down, from workflows to individual icons / tools.
I remember customizations where e.g. tabs and its content were hidden based on loaded application(s) and/or defined configuration variables.
caddcop said:In our barmenu based workspace, we allow users to manually swap to another barmenu after the default one opens for a particular file type. I could not determine if you could provide users with a way to show or hide ribbon tabs on demand.
I am not quite sure whether I understand fully your workflow (and what barmenu is), but a few comments: