On 02/01/11 17:13, Zaphod Feeblejocks wrote: > Could first-time users be taken to the addons page, so they know > functionality can be > extended? > > Could addons be clearly posted in the menus?
I think LibO could learn a lot from Mozilla's add-ons interface. Their revamped add-ons interface (for Firefox 4.0) places add-ons at the heart of the interface and has the feeling of an app-store. Lib0 needs to implement something like this to improve add-on discovery and simplify installation. As for implementing docx writing as an add-on and the wider question of whether or not LibO should support docx at all. It was my understanding that one of the primary aims of *The Document Foundation* and *LibreOffice* projects, was to put the user first. The average end-user doesn't care about the politics behind document formats. They simply want an office suite that works and doesn't require endless tweaks to allow interoperability with their colleagues, many of whom (perhaps lamentably) will be using Microsoft Office. Dismissing Microsoft's proprietary OOXML format and/or farming it out to an add-on amounts to nothing more than petty politics; it will turn users off and hurt this project immeasurably. Also, if OOXML writing is to be farmed out to an add-on, would you have it installed as a default add-on or would you have the user seek it out. If the prior, why not implement it internally? If the latter, you'll need to improve your add-ons interface for discovery and ease of installation (see above). Kind Regards, Lee Hyde. -- "The only demand that property recognizes, is its own gluttonous appetite for greater wealth, because wealth means power; the power to subdue, to crush, to exploit, the power to enslave, to outrage, to degrade." -- Emma Goldman, Anarchism & Other Essays (1910) -- Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***