Cynthia,
Cynthia Qu wrote:
> hi,Kay,
>
> Thank you very much for your introduction! I am sorry not reply to you
> immediatly, because I need to think it over. :)
No problem anyways :-)
> I am confussed about whether keeping on to do on this field or not, though I
> am interesting in this project. The big problem I am facing is I want to do
> something on the project, but I don't know how to start, or what I can do for
> it, or what is on process of it. As I have just known a little of the project
> during the past two monthes, I think it is cool to use UNO in different
> environments. And what I am more interested in is how to make it come true. I
> have a general idea on the UNO design, but I am lack of the code experience.
>
I think I understand this. I suggest to start with simpler Uno tasks,
may be fixing some issues etc.
>
> Kay Ramme - Sun Germany - Hamburg wrote;
> [...]
>> It all depends where we are heading with Uno ... and OpenOffice.org.
>> Unfortunately there is not (yet) any global vision or anything (despite
>> the all too broad mission statement).[...]
> Is that why we don't have many people disscuss on the mailist? And people in
> the project are adding UNOs for their special purpose, so they don't disscuss
> here? May I treat it as a SDK? What are we going to do besides adding UNOs?
The mailing lists IMHO have there very own problems, basically only a
few people are able to find them ... and there are just too many mailing
lists, not too forget the overlaps e.g. with api.openoffice.org or
odftoolkit.. or dev.. or porting..
As mentioned, one of the bigger problems in evolving Uno is the
constraint (or feature :-) to stay ABI (Application Binary Interface)
compatible.
>> A broader vision for Uno could be something as establishing it more
>> widely in the software world, FOSS as well as proprietary or commercial.
>> I certainly have some ideas etc. around this, and I also see a need for
>> this, especially in FOSS, where others are already trying to establish a
>> common object infrastructure to enable application inter-operation etc.
>> Unfortunately this is not what I get paid for ... :-(
> I think UNO technology will be widely used, thus I am interesting in it. May
> I know what the other contributors are doing on this project? How to know
> that?
> [...] :-)
There is at least one commercial company which uses Uno and which paid
Sun to make Uno available as a standalone product (URE). To understand
Unos potential we would need to look around and we probably would need
to actively advertise it ... and we would need a C' binding, thus the
"Clear separation ..." todo :-)
>> and if I find the time, would like to help improving the overall
>> architecture. From an overall project perspective, this seems to be most
>> important to strengthen our success and to stay competitive.
> It is a big deal and very important for the project! And may I take it as we
> don't need to do any tasks before thinking about the architecture? Do you
> have any tasks related need to do that I can do?
Like in any software project, the architecture has to evolve over time,
that means that I would not start a project by first implementing a
sophisticated architecture, but something which concretely solves the
problem. Later on, while the project evolves, I adapt the architecture
to more needs ... this is what we did not enough with OOo. From my point
of view, architecture becomes more and more concrete by doing constant
refactoring, IMHO you have a good architecture if you don't recognize it
as such :-)
>> My believe is, that if we work just a little bit more focused, OOo could
>> rule the
>> world :-)
> I believe in it, and that's why I am enjoying in doing something for it, too!
Good :-)
>
> And I appreciate you sharing time with me! :-)
You are always welcome!
>
> Best regards,
> Cynthia ^_^
> 2007-12-14
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
