#CONS TO NEOOFFICE INSTALL#
#CONS TO NEOOFFICE MANUAL#
#CONS TO NEOOFFICE UPGRADE#

The user will be made aware of the different UIs. The standard toolbar is legacy, the Notebookbar UIs were actually developed by work of LibO contributors.Ĭ)Provide freedom of choice to the user. more devs work on Linux environment and prefer standard toolbar thus they pick that for Windows users that prefer Tabbed UI)Ī) Highlight the flexibility in UIs from LibO, one of the strong points of LibO together with file compatibility,ī) Highlight ALL the UIs done by the Design community of LibO. This opens a can of worms of discussion, where personal preferences of devs might not match the preference of end users (ex. There might be Windows users that prefer the standard toolbar and won't like to have their UI changed from one version to the other.Ĭ) The devs need to choose the default UI to ship to users.

Option 1 also presents some disadvantages:Ī) Novice users, or users with such an ingrained routine that they don't venture to look at different menus still won't know where to change the UI in case they don't like it,ī) A choice is imposed by the devs to the users. Thus, something must be done for users to be made aware of them.Ģ - Provide a dialog picker at first start after an installation and give the user freedom of choice to select one of the multiple available UIs.Ī) not necessary to make a new dialog to select the UI.ī) Tailor the selected UI to OS where LibO is installed. IMO, the main problem that became quite clear in several comments in that Reddit thread and other online discussions is that many people didn't even know about the alternative UIs.

Working with one of the MUFFIN alternatives is already trivial from the View menu for anyone interested-no reason to choose one of them as a default when existing default is the most functional. While changing the default for only the Windows builds would require a whole parallel documentation including large sections detailing the differences between our button UNO actions and the MS API for the Ribbon namespace.Īgain that is pragmatism recognizing the reality of the development and documentation resources available to the project.įrankly the most functional MUFFIN UI is the Contextual Single hybrid-but the default Toolbar, Menu & Dialog supplemented by the Sidebar remains the most appropriate to ship cross-platform.Īgain that is being pragmatic. No this is pragmatic-the MUFFIN Tabbed NB only looks like the MS Ribbon UI it does not implement that API.

#CONS TO NEOOFFICE UPGRADE#

It turned out that JAVA was switched off in FF 3.6 after upgrade from 3.5.> The force of conservatism vs pragmatism and user adoption/growing the NeoOffice: Zotero OpenOffice Integration 3.0 plug-in Please ensure that the appropriate Firefox extension is installed and try again.'įF: Zotero OpenOffice Integration 3.0a7 plug-in Zotero Integration ErrorFirefox could not load the component required to communicate with your word processor. Clicking on the buttons brings up Firefox with the following error message

The toolbar is there, but it does not communicate with Firefox.

#CONS TO NEOOFFICE INSTALL#

The plug-in did not install automatically in NeoOffice after installation in Firefox, but I have managed to install it manually using the above description. oxt within the 'extensions/zoteroOpenOfficeIntegration/install' directory in your Firefox profile after installing the XPI.' oxt into NeoOffice automatically, but you can find a copy of the.

#CONS TO NEOOFFICE MANUAL#

Dan Stillman, thanks for useful advice about the manual installation of the.

Cons to neooffice