On Tuesday 08 February 2005 01:16, Ian Laurenson wrote:
> I'm currently procrastinating on work that I should be doing - so
> thought I would bounce an idea (only half serious) off the discuss list.
>
> On this list there have been discussions about a "lite" version of
> OpenOffice.org, here is an idea of how it could be implemented.
>
> Imagine a "cut down" version of OpenOffice.org written in Python, I'm
> going to call it OpynOffice (OpyO pronounced oh pie oh) in this message.
>
> Some suggestions for OpyO are as follows:
> * No tables in text documents - instead these are implemented as
> embedded sheet objects.
> * Only one way of cross referencing (extend variables a little and do
> away with set references and bookmarks). The variables would also handle
> paragraph numbering.
> * Only scripting would be Python (i.e no BASIC interpreter).
> * No endnotes just footnotes that can be positioned at the end of the
> document.
> * Implement the spreadsheet with all functions, but leave things like
> DataPilots to be optional add-ons.
> * Presentations be implemented by presenting a page of a text document
> at a time.
> * Rather than having a specification of interfaces, make sure that the
> same code is used in all instances.
> * Some libraries, I think, would need to be developed in C++ (I'm not a
> Python expert).
>
> First steps would be refining an API, then creating/modifying an IDE for
> development of OpyO.
>
> So what do you think - is this "Py in the sky" or something worth
> considering?
Until some programmers actually starts looking at this and understanding the
complexity of OpenOffice.org it will be "Py in the sky".
--
CPH : openoffice.org contributor
Maybe your question has been answered already?
http://user-faq.openoffice.org/#FAQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
