Chris Monahan wrote:

> So, what about the ability to add more or custom modules to that list?

If the component can be done as a macro, it can be included as an addon
for OOo.

> Alright here's an example, quite a simple one, OpenOffice Music - a

If you are talking about displaying a score using OOo, then install the
OOo-LilyPond macro to your setup.

If you want OOo to produce music from that score, then something more is
needed. If you want OOo to do sound editing, then you need a different
component.  [I have seen a half serious suggestion that Audocity,
LilyPond, abc2midi, and something else be merged/patched into OOo. In a
similar vain, the suggestion also made to patch The Gimp, Blender, and
another graphics program into OOo.]

> b: that with a published mechanism there could be a slew of extended
> modules offering things MS Office couldn't dream of.

What you are describing is a way for people that aren't familiar with
OOo to create vertical market applications with it.   A strategy that
was very successful for Microsoft, WordPerfect, and earlier times Ashton
Tate.[Now wondering if Ashton Tate pioneered that concept for software.]


> eg MS OneNote os impressive, but atm someone who wants to add
> such functionality to OpenOffice might face issues

sed /might/will/

OTOH, it might get ignored like issue 36672. (Though the dictionary that
is somewhere in Issuezilla with zero votes and zero comments might be a
better example.)

OTOH, # 24798 might be a better example of something closer to your
proposal, that has thus far apparently been ignored.

I thought that # 73868 & 73869 had been closed, but looks like it they
are still open.  :)
[Not that I like either palette, but they are an improvement on the
existing color palette.]

> And of course then, why stop with imitating MS Office functionality,
> anyone want a raster editor, music player or scanner/OCR frontend
> integrated into their office app? I'd bet my bottom dollar some would.

Assuming that either input, or output can be something in ODF format,
the ODF ToolSet will make it much easier for people to produce such addons.

One such component would be "Genealogy": This can import/export GEDCOM
files. It also includes a macro that opens up ancestor.com (or whatever
that site is called) similar to the (?current) wikipedia and
wikictionary macros.

A second one would be ForEx, which tracks the current Foreign Exchange
market. It includes a "simple' AI to suggest when it would be "best" to
buy/sell a specific currency. With minor changes, it could track the
stock markets of the world. [A potential issue with a component like
this would be SEC clearance/approval.]

> So in some ways I'm asking about a vast extension to the plugin architecture. 
> Ideally so that isn't so much a
> plugin architecture, more as a Generic Framework in which the components are 
> equal.

+1

> I'm possibly making suggestions that run completely against the grain
> of the way OpenOffice actually works under the hood, but I feel the

I see your request as a way of making it easy for niche functionality to
be easily added by end users with those specific needs.  Not everybody
needs a Genealogy component, or a ForEx component.  For some people,
that functionality can be a make/break issue.

xan

jonathon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to