On Thu, September 22, 2005 13:34, Alexandro Colorado wrote: > I dunno about MS I dont have their suite, however I know it would be > achievable to solve a lot of companies issues and promote the use of > Master documents.
Master documents, zip, etc are only a workaround. Stuffing everything in a single file does not make its lifecycle more manageable, it's just less files to attach to e-mail messages. And it creates problems because when you comingle everything the responsability boundaries blur. Office workers should learn from Developpers which _have_ been doing collaborative work for a long time. Any serious software project is composed of hundreds/thousands of files created and updated by different persons/organisations in parallel and somehow still put together to create something. (and when I say files it's source code but also ressources like images, sound files and so on). You want to improve oo.o collaborative capacities ? 1. add a view where you can manage the set of files that constitute your project. It can be a master/compound document or just a filesystem view. And the filesystem view is probably better because the components are clearly defined. 2. create plug-ins to communicate with the various backing stores you have on the market (Notes databases for enterprise users, subversion/cvs for centralised teams, svk/git/darcs for decentralised and/or serverless teams). So revisions can be pushed/pulled from the SCM 3. modify OO.o so revisions are stored as different files in the SCM not in a single OO.o file And that's about it. No need to reinvent the wheel (badly). Most of the infrastructure already exists today, you only have to plug OO.o into it. -- Nicolas Mailhot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
