This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
On Mon, 8 Feb 1999, Lalo Martins wrote: > > Hmm, they serve two very different purposes. An application that > wants to be extensible and customizeable should go Guile; an > application that wants to export some of its functionality > should go CORBA. Agreed. For an example of an app that will/does use both, look at Guppi - http://www.gnome.org/guppi/ - right now it exports a "Guile interpreter" CORBA interface, which provides the IPC to support a hacked copy of scwmrepl. gnome-guile-repl can talk to any program that exports the guile interpreter interface. Guppi has bindings to some of its internals and to the Goose statistical library, and will eventually be "embeddable" in other Gnome apps using CORBA. > Trouble is where the developer wants both - > like GNOME Panel and Control-center; they want to be extensible > by independent "applets". IMHO these applications should go > _both_ GNOME and Guile, so that other developers have the option > of writing a (probably compiled) CORBA-client applet or a > Guile-script one. > In this particular instance, you could just export the client-side stubs to Guile then write the client in Guile. (The "real solution" is Guile bindings for ORBit, but that would be harder. :-) Havoc