faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Multiplatform Support
by Sebastian Sauer on Wednesday 20/Feb/2008, @21:10
|
> That only works if those "90% of the people" all need the same
> "20% of the features." I suspect that assumption is faulty.
It depends what this 20% are. Let's look at KWord for example. Each users needs the functionality to 1) load a document, 2) edit that document and 3) save that document. And there you have already the basic functionality each user needs :)
Now let's look how additional functionality is integrated, for example Variables like displaying the current date/time or like the scripting plugin. They are both done as plugins.
What you gain from this? A defined small(er) set of basic functionality that just needs to work 100% correct for anybody on the one hand and a very modular architecure on the other. Those does provide then;
* easy way to add or remove plugins without any recompile
* a clear API and separation for functionality
* it's not needed to know about all details to add new functionality
* things are more reusable, look at the Flake-architecture here as example
* it's easy to tailor an app to special needs like the kids-office, mobile devices or full-powered desktop's
* a more cleaner codebase
* etc.
Someone already did mention firefox and imho we could also look at amarok or even plasma here. Provide base functionality that is just needed in any use-case and go with plugins for more specialized additional functionality.
Well, that's at least my pov here :) |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
