A supplement suite of office programs?
revolutionary.dan at gmail.com
Thu Dec 22 19:27:43 CST 2005
Chandler's being done in Python. It will be open source all the way down,
which will be a big difference from this project. Not necessarily better or
worse, just different.
I think that if this is going to look and act like a suite, then we need a
convention for information-sharing. Doing it ad hoc per module is going to
get unwieldy and ugly very fast.
But this need not be hard or arduous. We can just agree that each app will
save its data in XML and publish the DTD to the other apps in the folder
On 12/22/05, Lynch, Jonathan <bnz2 at cdc.gov> wrote:
> I don't know what they are developing Chandler in
The way to divvy up work seems pretty straight forward. Anyone wanting
> to participate can contribute an application(s) to the suite. If two
> apps need to communicate with each other, then the developers working on
> those apps need to work that out together. Any freelance work that is
> generated by the suite could be bid on by any (or all) of the developers
> who have contributed. Any customization work would go directly to the
> developer of the specific app that is to be customized. Any a-la-cart
> sales would go to the developer of that particular a-la-cart component.
> However, in order to contribute an a-la-cart component, you should also
> have contributed a freeware component.
> I am open to all ideas, of course. These are just ideas off the top of
> my head.
> Take care,
Dan Shafer, Information Product Consultant and Author
Get my book, "Revolution: Software at the Speed of Thought"
More information about the use-livecode