![]() |
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.
Re-thinking the way toolbars work in ICM would be very welcome (and it has my vote) although I am of the opinion that this is just the tip of the iceberg when it comes to peculiarities of the GUI. Albeit the toolbars are a great place to start.
I feel that it may be constructive to skin the app based around particular workflows rather than having it as a big sandbox like (say) GIS platforms typically operate (which seems to me what ICM is currently emulating). Browsing through the forums briefly, I can see rather a lot of posts that ultimately tie back to UI/UX related matters. Perhaps instead of approaching them all individually, it might be beneficial to look at (say) the entire model-build process and determine how that workflow could be made more efficient. Try to hit several birds with one process-chart?
This relates back to what the original user is asking for as we could (for example) load a whole skin/workflow-template that omitted/included particular icons/toolbars depending on what one wants to do on that day (e.g. model build, model review, 2d analysis, verification, etc). If possible, the skins could then be optimised for some common screen sizes and resolutions. User can opt-in/out icons depending on preference and re-save it as custom if desired.
Perhaps that's getting too out of the box or should be its own topic? but I think its worth considering this matter from the bottom-up as well as the top-down. Would be interesting to hear from Innovyze what the constraints are around that as well as I don't develop GUI's myself, just use them. Cheers!