I recommend something more neutral such as Starter, Intermediate, and Full or some equivalent, so it is about the interface, not the user of it. The default on an install could be Starter in the absence of an existing user configuration.
Should we consider having the skins simply be options on a single binary, especially since they should all be able to consume the same ODF files? This should mean that the same localizations would work and be done once for a release. The help system might be specialized based on the skin selection, but that is an isolatable provision. There would also be no explosion in the builds and problems of users having to choose among them. I am assuming there would be no dramatic difference in the "chrome" so the move among levels is not startling in terms of appearance, but more in availability of menus, sidebars, some dialogs, etc. And, of course, this is yet one more interesting area where we would have to find developers that are equipped and available to work on something like this. - Dennis THINKING OUT LOUD [To help with interchange, the configuration file could be used to signal which level was used to produce a document, so that the consumer has some idea what might be needed to edit all of its features. Having this be smooth in all directions takes some more thought.] My limited sense of OOo4Kids is that it is not just the build of OpenOffice but the packaging of extensions and other aids that matters. The downside of a single distribution is that it does not become smaller than the current one. I don't know if that matters for an OOo4Kids clone or not. OT: This is a problem that Microsoft Office has attempted to address in a variety of ways over the years. The idea is not to confront new users and the very occasional users with a plethora of choices and complex menus. One attempt involved progressive disclosure of additional options and choices based on what an *individual* user tended to use, so it was personalized and dynamic. Like it or not, the ribbon was the replacement for all that. One useful feature about the ribbon is that it can be collapsed and almost all of the application window used for the document being worked on. The context (right-click) menu provides a variety of immediate actions depending on where the cursor is and the ribbon can be recalled when needed. And there are substantial provisions for customization, including simple tuning by users who put features they use often on a quick-start bar next to the window title. I put a sample screen capture about this at <https://bz.apache.org/ooo/show_bug.cgi?id=126098#c9>. -----Original Message----- From: jan i [mailto:j...@apache.org] Sent: Monday, February 16, 2015 01:26 To: dev@openoffice.apache.org Subject: Re: OOo4Kids & OOoLight Status On Monday, February 16, 2015, RA Stehmann <anw...@rechtsanwalt-stehmann.de> wrote: > On 15.02.2015 23:14, Guy Waterval wrote: > > > > > > You could reduce the number of options here. For instance OOoLight is not > > necessary. The differences with OOo4Kids are too small. > > Novice, Intermediate and Advanced (AOO without modifications) should be > > enough (personal opinion). > > > IMO the brand (OOoLight) should be kept and a special skin, so adults > need not to use a "kiddy" skin, if they want to use a lighter office suit. In order to keep it (as AOO) we. need to know - is the brand registred and eho has the current right to the brand - can we as AOO provide resources to keep this alive I think it is a good downstream project, but I do not currently see a possibility to add this to the AOO project. rgds jan i > > But this may not be important. > > Regards > Michael > > -- Sent from My iPad, sorry for any misspellings. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
