![docear doesnt work docear doesnt work](https://quotefancy.com/media/wallpaper/1600x900/1519805-Claire-Cook-Quote-If-plan-A-doesn-t-work-the-alphabet-has-25-more.jpg)
The submenus appear only when needed, in a short left vertical bar (again: only icons with clear meaning) the important edit menu appears even as an unobstrusive pair of small gears. For instance, Mindjet for tablets (and I think this approach could also be applied to desktops), shows only one short horizontal bottom bar with clearly telling icons (no need for accompanying thext). Plenty of new solutions are appearing in the own terrein of mindmapping. These versions are thus very pragmatic in their approach: they are made according to the needs of its own program and not to follow and adapt to the structure of Microsoft programs such as MS Word. These programs mostly use clever ad-hoc (text and graphic) versions of the old menus, each menu and sub-menu layout (bars, matrices, wheels, etc.), depending on the nature of the function to be displayed. It is very telling that most programs characterized by its lean interface do not use ribbons (Chrome, Firefox, Google Drive, Dropbox, iOS and Android, etc.). And the feeling that you get when you open the ribbons and they invade your screen and your eyes is terrible. And I do not see a real advantage for the learning curve of newcommers: ribbons still need text accompanying the bulky icons. They are actually the same classic menus but in horizontal display, but then taking too much room, even excessively in the small modern screens. Ribbons are not a really efficient nor innovative option. I find that Freeplane should look for a better alternative or complement to its current classic menus. But I think that the issue is not only about keeping the classic menus option but about improving them: more attractive and meaningful icons and symbols, regrouping of commands, and so on. ldmpub-nospam Posts: 56 Joined: Tue 5:35 am I have, in the past, redefined menus dealing with the menu in XML format and it was also Okay for me. Do you think we need a way to define ribbons in mind maps like we did it for menus in 1.3.x ? => I have no opinion. Do you agree Freeplane should keep the both UI options? => It's always a balance between the additonnal work to maintain both and the interest of keeping the old classical menu (for old computers, for "historical" users, for reference documentation. I'm just surprised not to find any "contextual menu" when right clicking on a nodeģ. How do you like the new structure used as a menu? => New menu structure (XML proposed by Dimitry) looks quite Ok. How do you like ribbon ui? => In general I like this type of presentation but yet I haven't seen / used it in Freepalane (or I have missed something?)Ģ.
![docear doesnt work docear doesnt work](https://hugelolcdn.com/i/556810.jpg)
I'm waiting, for about a year, for "Docear's ribbons" because I think this could increase Freeplane usability + this new user interface can help Freeplane gain new users.ġ. Regards, Dimitry Attachments menus-and-ribbons.zip (8.04 KiB) Downloaded 192 timesĭpolivaev Site Admin Posts: 667 Joined: Sat 1:21 pm Do you think we need a way to define ribbons in mind maps like we did it for menus in 1.3.x ? Do you agree Freeplane should keep the both UI options?Ĥ. How do you like the new structure used as a menu?ģ. If you do so Freeplane complains about some missing text keys and actions on start, it is ok for this test.Ģ. For enabling this menu you can just save it as /resources/xml/mindmapmodemenu.xml. To justify how it could work I wrote an xslt transformation back to the menus ribbons2menus.xsl also attached to this mail and used it to create valid mindmapmodemenu.xml which contains the same structure as the mindmapmoderibbon.xml and can be used with Freeplane 1.2.x / 1.3.x to get an impression what this structure looks like being displayed as a menu. This definition could have some ribbon specific attributes or menu specific attributes (like radio_action) ignored by the other ui but be useable for the both kinds of interfaces. I think that we should have just one menu structure definition valid for both ribbons and classical menus. Therefore Marcel (Docear) has implemented a new xml description of the ui attached here as mindmapmoderibbon.xml.ģ.
![docear doesnt work docear doesnt work](https://i.ytimg.com/vi/U-m-X87nCQA/maxresdefault.jpg)
Ribbons have significantly different ui elements than classical menus. I would give the user this option because ribbons are reported to consume pretty much computer power and slower the program down and because I generally prefer to let the user the choice.Ģ. Ribbon framework prohibits simultaneous use of application menu, but it is possible to let the user the choice to run freeplane with ribbons or with a classical menu. Let me share with you some insights and questions about it.ġ. As some of us already know Docear ( ) has introduced new user interface based on ribbons ( ) and we are going to adapt it in the coming Freeplane versions (1.4.x and above).