Kay Ramme wrote:
Hi there!
Hi Charles,
[... snip ...]
did you see Leonard Madas "Grand
Vision" document yet?
http://wiki.services.openoffice.org/wiki/User_Experience/Grand_Concept
Just went through that thing just to still find the same old prejudice
about our internal architecture.
Am still thinking that anyone who still comes up these days presenting
with that 'new(?) idea' to split up the than in such new(?) concept
strategy so called 'monolithic-OOo' didn´t understand the concepts of
shared libraries of modern operating system and didn´t understand the
basic concepts of UNO and OpenOffice.org's component model.
Just to repeat that here for the few-hundred-and-and-a-dozeneds-times
for those who still do not know: just because there is one soffice
executable and a shared framework to open documents for all
OpenOffice.org modules doesn´t mean every functionality available has to
be loaded on startup at once.
It´s all already 'modularized' and there do exists already ongoing
efforts to split up the installation files into packages which depend of
each other - been there done that! - so what? This is not something that
is such a great new idea that we would not already working on since a
long time.
Also I do not currently see why to bring concepts like the Lively Kernel
into play when talking about dynamic content in Impress or other
modules. Impress and other modules already have an API that you can
program it with which is defined in UNO and available to all supported
programming languages which have a language binding available for UNO. I
more and more get the feeling that there´s a strange kind of battle
going on these days named something like "on which virtual machine and
API´s do you want to run your virtual machines and API´s today?" or
"Here´s the right stack to use for your stack!" After all if I want to
extend something like impress with dynamic content features I just need
SOME sort of API to do so and preferable support for some programming
language which I can know how. Why care whether that is something based
on UNO and OpenOffice.org existing UNO API´s and the existing
OpenOffice.org extension features plus a few possible future
enhancements thereof or something tight to a new API on top of some
other new API based on javascript and SVG/HTML support in firefox or on
an new API based on top of installed java support or an API based on top
of installed Flash support or an new API based on support for IE and
Active-X controls being there or <whatever/>.
[... snip ...]
Regards,
Bernd Eilers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
