There seems to be a lot of effort in the code to reproducing the windows GDI calls, this seems to be related to getting the edit component working.

How far does lazarus intend to go in implementing the GDI calls? Enough to allow owner draw style components to be written or just enough to get the edit component working?
Or even all the way.

Peter

Peter Dyson wrote

There seems to be a lot of effort in the code to reproducing the windows GDI calls, this seems to be related to getting the edit component working.

Thats just because as soon as we have an editor, we can start to develop lazarus with our own tools. So there is a lot of effort to get the editor working. In stead of building our own editor we use a public edit component already the for Delphi. To get things ported you need to be much like Delphi.

How far does lazarus intend to go in implementing the GDI calls? Enough to allow owner draw style components to be written or just enough to get the edit component working? Or even all the way.

A lot of Functions/Components rely on the winapi module. Thats not only the editor. Classes like TFont, TBrush, TPen, TBitmap, TCanvas are build upon the winapi (this way they are compatible with routines which use api calls). A component like TScrollbar can use just the winapi for itself so there is no need for it to create additional (GTK and others) code to for instance Show/Hide/Set itself.

In the beginning I don't think we are going to build all of the functions. Just a workable set which can be extended the mment a function is needed.

Marc