On 25 January 2011 06:45, Frank Church <[email protected]> wrote: > > I am finding the NoGUI option useful in converting projects using > TDataModules to Linux, but there is some talk about phasing it out. > > Can anyone clarify the original purpose behind its existence and whether it > is problem free so long as no forms or controls are activated within the > App? > > As the original poster I have to say it serves my immediate need, of being able to gradually separate out the non GUI parts of an app and run them standalone. The data modules need to send the output to the GUI and I am now making the linking of the data modules with GUI conditional with preprocessor directives.
I can't say I am familiar with the LCL structure, lazbuild etc, so I say let NoGUI remain to ease the reorganization of existing GUI apps. My main concern now is how the GUI part of an app can expose an interface to data modules that do not require the data module to link with GUI libraries. The first thing that comes to mind is to use internet sockets for the interprocess communication, but it feels rather awkward as the presence of the necessary ports cannot be guaranteed on any system. Is that where stuff like interfaces, COM, and CORBA etc come into play, or are there simpler alternatives? > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com > -- Frank Church ======================= http://devblog.brahmancreations.com
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
