[Lazarus] What is the future of NoGUI widget set?
Mattias Gaertner
nc-gaertnma at netcologne.de
Wed Jan 26 14:46:03 CET 2011
Michael Schnell <mschnell at lumino.de> hat am 26. Januar 2011 um 13:06
geschrieben:
> On 01/25/2011 10:33 AM, Graeme Geldenhuys wrote:
> >
> > I also can't understand the point of the
> > 'nogui' widgetset.
> In fact its "Widget Type". (Not that I like this name, but somebody did
> name it so.)
It depends on the context.
Nowadays on this list "widget set" means a lcl backend, which depending on
context includes or excludes the widgetset depending LCL interface code. For the
lazarus devels the "LCL interface" is the code between the widget set and the
LCL platform independent code. For some users the "LCL interface" is the set of
functions/declarations in the unit LCLIntf, LCLType, InterfaceBase.
10 years ago, the term "widget set" was not used and I simply used the pascal
word "type" for the macro. I think for compatibility it should be kept. Of
course a second macro can be added, for example 'LCLWidgetSet' or 'LCLPlatform'.
> > An application is or GUI or non-GUI (latter
> > requiring no widgetset at all).
> Yep, but as the Timers, the Event Queue handling (and AFAIK the
> Exception handling) is implemented in the "Widget Type" code a noGUI
> Widget Type that provides such things does make sense (the current
> version of the noGUI Widget Type does not provide Timers and Event Queue).
Exception handling is done by the RTL. The LCL "Application" sets a hook to show
a dialog.
TTimers and event queue are implemented by the widget set.
Feel free to implement it for the nogui widget set.
Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20110126/059a7405/attachment-0003.html>
More information about the Lazarus
mailing list