| Revision 18311,
976 bytes
checked in by ghudson, 22 years ago
(diff) |
|
This commit was generated by cvs2svn to compensate for changes in r18310,
which included commits to RCS files with non-trunk default branches.
|
| Line | |
|---|
| 1 | |
|---|
| 2 | OAF is the new Object Activation Framework for GNOME. OAF has a |
|---|
| 3 | similar purpose to gnorba, the GNOME 1.x CORBA activation library, and |
|---|
| 4 | will replace it for GNOME 2.0. |
|---|
| 5 | |
|---|
| 6 | It allows you to do much more powerful activation queries than gnorba. |
|---|
| 7 | Each server is described by an XML file that defines its |
|---|
| 8 | attributes. When querying or activating, one may specify complex |
|---|
| 9 | requirements using the OAF query language. |
|---|
| 10 | |
|---|
| 11 | |
|---|
| 12 | OAF requires a special version of ORBit to build. You can find it |
|---|
| 13 | in the `ORBit-martin-forked' module in GNOME CVS; this is a version |
|---|
| 14 | of ORBit 0.5.x which has been ported to use glib HEAD and its API |
|---|
| 15 | has been modified to be the same than ORBit2. |
|---|
| 16 | |
|---|
| 17 | You can compile OAF with either ORBit-martin-forked or ORBit2; the |
|---|
| 18 | only thing you need to do is to recompile all your code. |
|---|
| 19 | |
|---|
| 20 | OAF will start using ORBit2 now too far in the future, but currently |
|---|
| 21 | ORBit2 is still too unstable to be used. |
|---|
| 22 | |
|---|
| 23 | |
|---|
| 24 | |
|---|
| 25 | Also, if you want to build the API documentation for OAF, you need |
|---|
| 26 | gtk-doc and jade. |
|---|
Note: See
TracBrowser
for help on using the repository browser.
