Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On 10/15/2010 07:35 PM, Marc Paré wrote:

We may decide to have different targeted versions of LibO for education;
business; academic; SOHO; corporate etc. with added value plugins. 

Rather than creating umpteen different versions of LibO, how about
umpteen different collections of extensions?  Include the most popular,
or theoretically most useful half a dozen or so collections in the
installation package, allowing the user which package(s) they want to
install.

I would also suggest not to drown the new user with too many new extensions (especially with them 
showing up in the menu bars) 

+1

#####

On a semi-related note, my suggestion is for extensions to be off one
menu, and not create their own top menu item.  (IOW, all extensions are
found under "Extensions", rather than have a top line menu item, like
".riess", "toools", "Scale Assistent", etc.)

I'd also suggest that toolbars be mergable into existing toolbars,
rather than create their own new toolbar.

jonathon
-- 
No human will see non-list, non-bulk, non-junk email sent to this address.
It all gets forwarded to /dev/null


--
E-mail to discuss+help@documentfoundation.org for instructions on how to unsubscribe
List archives are available at http://www.documentfoundation.org/lists/discuss/
All messages you send to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.