Hi,
Jacob Floyd wrote:
I'm getting ready to create a new layer for OOo, and was told I should do it in UNO. However, I'm not sure how UNO helps me and I hope some one can explain this (read on):
From what I understand UNO uses the network for different OOo components to talk to each other. Is this true?
Of course it's true but only one facet of UNO. UNO is a component model which allows you to define interfaces language independent in UNOIDL.
You can now implement UNO objects/components in one of the support languages. The advantage of such an abstaction is that you can exchange for example a C++ implementation of component A with an implmentation in Java if necessary. Or you use component A running in a process on a different machine but for the client it is transparent if the component runs in procss or on a different machine. See the DevGuide for more information about UNO (the chapters "Professional UNO" and "Writing UNO Component" should be interesting for you -> an updated version is coming soon where the new UNO features are described))
In case of a toolit abstaction you can exchange the underlying implementation with a GTK based implementation, a Java Swing based implementation or something else. The code using the UNO interfaces (UNO abstraction) hasn't been rebuilt when you exchange the undelying implementation and that is of course a huge advantage.
The problem for a new toolkit layer is to find a common abstaction which is complete but also general enough that it can be mapped to the different platform/language dependent graphic layers.
Hope this make things clearer for you
Juergen
What happnes when a user doesn't have a network card or any network devices installed?
And how does UNO help in writing a UI component.
Note: I haven't read very far in the OO Developer Guide, but don't want to read all 1000+ pages only to find it's useless (and thus a major waste of my limited time). If it's explained in the document, and UNO really _is_ what I should use, then I'll read the docs.
FYI I'm going to be working on a new chrome layer (I call it "Silver Onion" right now If you search the dev@gsl.openoffice.org list for silveronion you should be able to find the thread where I started talking about my ideas.) to replace VCL (not all of VCL just the chrome/event portions). Also, this is big and will take a long time, so don't get your hopes up just yet, I'm still in the 'planning' phase.
Thanks, Jacob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
