Hi Greg,
very good question :-)
Am Freitag, den 25.11.2011, 00:31 +0000 schrieb Greg:
Hi I'm curious,
How modular is the LibO code base? In other words, do we have separate
* document model (Model)
* page renderer | slide renderer | drawing renderer &c. (View)
* bunch of action modules (one for each user action), that can be rendered
as menu/context items, toolbar items, or API calls (Controller)
Just wondered, because I think it presses on the need to build a solid and
flexible foundation that will enable efficacy and ease of restructuring LibO
to implement great plans like Mirek's Citrus.
Oh, its also required for much smaller plans, I'd say. Although I don't
know alle the scary details, I had lots of discussions with devs in the
past. For example, when we've discussed the need for an "Outline View",
I have been told that the "Model/View" isn't clearly separated in
Writer. Thus being only one example ... so it will need major code
restructuring to provide a clean MVC.
This is one of the reasons why large-scale improvement proposals don't
help our development at the moment ... instead, it helps them to improve
the code iteratively and to refactor bit-by-bit. (Mirek addressed some
of these concerns with his roadmap, although the chunks are still too
large).
If the code is a jungle, we'd be better advised to make it fit for purpose. A
goal and a roadmap would be a great idea. Architectural simplification would
also leave some breathing space for the design team to test and refine Mirek's
ideas (and competing proposals) with users.
Although some people within the community might disagree: I think a
rough plan - a vision - would greatly help to communicate what we have
in mind in general. And whilst we have our development working with us
on smaller improvements, we could really make use of the given time to
resolve open questions like target users, high-priority workflows, ...
You've asked "Hope that makes sense?" ... Absolutely! Glad to have
people with your expertise around!
Cheers,
Christoph
PS: I'm terribly tired, so I'll skip any mediocre proposal how to
continue. But I'd be happy for any input :-) Good night!
--
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent 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.