On Wed, 2006-06-12 at 11:40 +0100, Finn Gruwier Larsen wrote: > A simpler and better documented API would be a very good thing because > it would attract more programmers and developers to the OOo community. > But there's more to it: it would enhance the possibilities of making > money out of OOo by customizing it for end-users. That would make more > small IT companies and freelance consultants interested in participating > in the community and spreading the product, etc. I think we need that to > happen.
Another example: I know a developer who works for a company that sells training materials. They are organized into modules, but different clients require a different collection of modules. What they would like to do is: * Store each module in an ODF file. * Write an OOo-based program that grabs a set of modules, organizes them and saves them all as one PDF file that can be given to their clients as a handbook for the course. He was asking me for help with the OOo API, but in the end I couldn't help him. AFAIK they haven't yet implemented this solution. I know another developer, who is the CTO of a medium-sized company. The company needs to do a lot of document transformation. He's getting the company to store data in ODF format under the expectation that they'll be able to mix&match and transform it into whatever format they need. He is a bit nervous about whether this will work out the way he hopes. If there was an easy&efficient OOo file conversion API he would be more comfortable. Best, Daniel. -- "I AM in shape. Round IS a shape."
signature.asc
Description: This is a digitally signed message part
