Difference between revisions of "LCL Interface Redesign Idea"

From Lazarus wiki
(code highlight and category)
m (Interface identifiers are normally prefixed with an 'I', not a 'T')
Line 18: Line 18:
 
'''The change to .Handle will not break existing code.'''
 
'''The change to .Handle will not break existing code.'''
  
<delphi>TWSxxWinControl.CreateHandle Returns a TLCLHandle
+
<delphi>TWSxxWinControl.CreateHandle Returns a ILCLHandle
  
TLCLHandle = IInterface; // interfaces as com objects
+
ILCLHandle = IInterface; // interfaces as com objects
  
TxxPrivate = class(TPrivate, TLCLHandle);
+
TxxPrivate = class(TPrivate, ILCLHandle);
  
TGtkPrivateButton = class(TGtkBin, TLCLHandle);</delphi>
+
TGtkPrivateButton = class(TGtkBin, ILCLHandle);</delphi>
  
 
All TWSxx. methods  should be moved to the private class. for instance:
 
All TWSxx. methods  should be moved to the private class. for instance:
Line 37: Line 37:
  
 
NOTE:
 
NOTE:
I'm not to sure if we should expose the TLCLHandle as Interface. This will cause an overhead of adding exception frames, addref and releaseref calls. We can do it internally and use TLCLHandle = PtrUInt (MWE).
+
I'm not to sure if we should expose the ILCLHandle as Interface. This will cause an overhead of adding exception frames, addref and releaseref calls. We can do it internally and use TLCLHandle = PtrUInt (MWE).
  
 
==Other possibilities==
 
==Other possibilities==

Revision as of 09:45, 2 February 2011

Why would we want this ?

In the present situation, the handle returned by TWSWinControl.CreateHandle is in case of win32 the winapi handle of the widget and in case of gtk a PGtkWidget. For the QT and Carbon widgetset a private internal object is returned. Using an internal object has some advantages. One of them is that we can use a true object hierarchy, with clear inheritence inside the widgetset. However, many code using the LCL expects the handle being castable. Returning an object would break this.

NOTE: In case of gtk, we don't have to return the internal object, we still can use the existing way of retrieving the widgetinfo NOTE2: We also can start to use LCLHandle only, so that a later transition will be easier

This is current Idea for the structure of the interface and how it relates to handles

Overview:

  • Fork a branch of lazarus/
  • Replace TWinControl.Handle with TWinControl.LCLHandle (there should exist no Handle yet)
  • Try to get the LCL compiled and maybe the IDE so it doesn't use the (inefficient) .Handle anymore
  • Introduce .Handle again, now as WSclass call
  • Merge the branches

The change to .Handle will not break existing code.

<delphi>TWSxxWinControl.CreateHandle Returns a ILCLHandle

ILCLHandle = IInterface; // interfaces as com objects

TxxPrivate = class(TPrivate, ILCLHandle);

TGtkPrivateButton = class(TGtkBin, ILCLHandle);</delphi>

All TWSxx. methods should be moved to the private class. for instance: <delphi> class procedure TWSGtkWinControl.SetText(const AWinControl; const AText: String); var

 PrivWinControl: TGtkPrivateWinControl;

begin

 PrivWinControl := TGtkPrivateWinControl(AWinControl.LCLHandle);
 PrivWinControl.SetText(AText);

end;</delphi>

NOTE: I'm not to sure if we should expose the ILCLHandle as Interface. This will cause an overhead of adding exception frames, addref and releaseref calls. We can do it internally and use TLCLHandle = PtrUInt (MWE).

Other possibilities

For accessing widgetset native handles or IDs from the LCL, in the current situation, ppl have to cast the handle. In the case of gtk, to retrieve the XID, one needs the following cast:

<delphi>PGdkPrivateWindow(PGtkWidget(Handle)^.window)^.XID</delphi>

When interfaces are used, one can imagine the following code

<delphi>{$IFDEF GtkHasX} TGtkPrivateWidget = class(TGtkPrivate, ILCLHandle, IX11Handle);

(AWinControl.LCLHandle as IX11Handle).XID</delphi>

or maybe better: <delphi>if Supports(AWinControl.LCLHandle, IX11Handle, X11Handle) then

 ... DoSomething with X11Handle</delphi>

Which leads to cleaner constructs, without the need of internal knowledge of the handle and can be the same in all widgetsets that use X11.

Note that for this we need COM interfaces and not CORBA, however we don't need reference counting, so AddRef and ReleseRef can be implemented by just returning -1

A problem with interfaces is that Qt for example runs in several operating systems. How do you know what is supported where? We will need to fill the class definition with ifdefs.