KDevelop and the Qt Designer

Gordon Tyler gtyler at iafrica.com
Tue Aug 15 07:18:00 UTC 2000


----- Original Message -----
From: Mark Hatch <mhatch at ics.com>
Sent: Tuesday, 15 August 2000 08:12

> I think that this type of facility would be useful in general for other
tools.
> >From our experience in integrating our GUI Builder (BX PRO) with Source
> Navigator, other useful facilities would include:
>
> 1. Communication mechanism so that files generated by a GUI builder (or
other
> code generator) could be included in the project
> 2. Communication mechanism so that search paths for include files and
libraries
> could be added within the build mechanism.
>
> I suggest that Corba or some other "arms length" mechanism be used so that
> Kdevelop users could use their choice of tools that might be licensed
under
> licenses other than GPL.

CORBA seems rather heavy-handed for this type situation. Under KDE2, DCOP
would probably be a suitable mechanism. But I'm not quite sure what one
could use under KDE1. What inter-application communication mechanisms exist
for KDE1?

Ciao,
Gordon







More information about the KDevelop mailing list