Maarten,
:murb: [maarten brouwers] wrote:
Hi Kay, and others,
URE (Uno Runtime Environment) is just an abbreviation for a collection
of tools and libraries OOo depends on. Unfortunately names have not
been chosen well (UDK, URE etc.), so I am planning to fix this.
As I said, Uno (URE) is the foundation of OOo, if you do not know
about it, that is sad :-(
I think many on the website dev list are here because they lack
understanding of technical details of the complete suite, but would like
to help out by spreading the word better (just like people e.g. at the
marketing/art department)
I understand that not everybody wants to know all technical details
regarding the OOo application suite. On the other hand I think that
having a brief overview at hand regarding its architecture, is
advantageous and lets better understand why things behave as they do.
My impression is, that you basically think you are the only one
allowed to have an opinion how users and contributors etc. are to be
guided through the main page. From my point of view, OOo is build up
by its accepted projects, so these accepted projects very well have
the right to attend to interest.
I don't think he thinks that he is the only one. But as said, most will
John already corrected my impression ... :-)
not look to the project from the components/projects point of view. This
IMHO there is a gradual path OOo users (as typical for all application)
go, being a newbie first, becoming an adept later on, so some be stuck
somewhere on the way.
does not mean this is an unimportant view, or that we think it is the
website is thought of as "only for the end users"... at least for me it
comes down to not understanding the overall structure (I might try to
find out, but it would be too time consuming). This is a main problem of
If you ever have the feeling again, that you would like to know more of
its internals, I would be glad to help you :-)
concern for openoffice.org. I believe the project page could very well
be used for explaining the structure of how all projects/components
relate. And this can both be interesting to interested end-users,
developers who want to connect to OOo from outside, or want to help
improve the foundations of OOo.
Yep, I believe the same.
I would highly appreciate it if someone like you, Kay, could give a
seagull-eye's view of the project, preferably graphically (sketch it on
paper, scan it and send it...) This would greatly help us developing a
website that does not only communicate the things we do understand well.
It is pleasure for me to help. Some time ago I created a very simplistic
(and not too beautiful) graphic, giving a brief overview of OOos
architecture, you may want to take a look:
http://wiki.services.openoffice.org/wiki/Architecture
And just another word regarding the terms contributor or contributing.
IMHO these are chosen badly, I am pretty sure that only a very few
people arriving at the homepage already know that they want to
contribute, especially developers (which we are lacking, in contrary
to users) are mostly curious about how things work, despite wanting to
'contribute' in the first place.
I believe (and I think this is also what you're saying) when the
projects are better presented, it will also stimulate people to contribute.
I have the same opinion.
g.,
Maarten
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
