Re: almost scared to ask this...

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: almost scared to ask this...
by Thomas Zander on Saturday 12/Jan/2008, @06:09

One thing that I kept in mind while doing plugin-interface design for KOffice2 in general and for text specifically is to make sure companies can add their own workflow features without touching the KOffice codebase.
If a company wants to have something like a special variable in text that connects to their internal database (for example), they can write a text-plugin quite easily to do that, again without touching the KOffice codebase. (see the techbase tutorials about koffice plugins)

Since the libraries KOffice provides are LGPL the company may very well choose to make the plugin they want to use closed source. Which obviously means it will never hit the KOffice codebase.
There is a nice incentive for companies to go via KOfficeSource instead of doing it in-house not only because of the expertise, but also because of the Qt licenses required to do this.

Bottom line; this significantly lowers the trashhold for large rollouts to succeed. Any missing thing can now be added by paying the experts to do exactly that.

Exciting times :)

Related Links

·   Articles on KDE Office Suite
·   Also by Thomas Zander
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"Feature freeze means that everyone has a bad feeling when they change something, almost nothing more." -- Stephan Kulow
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.