[Pipet Devel] Re: Overflow/Loci/GMS collaboration

Gary Van Domselaar gvd at redpoll.pharmacy.ualberta.ca
Tue Mar 14 10:51:35 EST 2000

> It's amusing that all 3 projects independently decided to separate the GUI
> from the core.  But if we are to keep the GUI separate, does it really matter
> what language the GUI is written in, or is this a personal preference?

considering that the GUI is used to visually construct data workpaths,
speed is not an issue, and that most user feedback requests are for
interface modifications, I suggest we stick with Python, considering it
is such an excellent rapid prototyping language, and very easy to pick

> I know it seems awkward to have 3 languages.  But I guess we'll have to see to
> what extent our projects will be merged.  If we're looking at a single
> distribution, and Overflow and GMS agree on either C or C++, then we can
> consider C or C++ for the GUI.  But if our projects become separate
> distributions (as with Gnome) that communicate through CORBA, language
> shouldn't matter.

I can see why we would want to use CORBA's IIOP to communicate between
'cores' in a network distributed environment, and also to control
wrapped applications, which likely are also distributed, but if the core
and GUI reside on the same box, is there a need to communicate to the
GUI through CORBA? Loci and Overflow have already developed an XML
protocol for core<-->GUI communication.  Is there a better argument for
switching to CORBA?


                                  Gary Van Domselaar
                               gary at bioinformatics.org
                           bioinformatics.org: The Open Lab

More information about the Pipet-Devel mailing list