[lazarus] [win32] Client area under win32

[Vincent Snijders]

> -----Oorspronkelijk bericht-----
> Van: Gerry Ferdinandus [mailto:gerry_ferdinandus at hotmail.com]
> Verzonden: woensdag 18 september 2002 11:59
> Aan: lazarus at miraclec.com
> Onderwerp: [lazarus] [win32] Client area under win32
> b) Testing tools.
> For testing our interface we need some testing programs. The Lazarus
> examples are not suitable for our purpose. So we need some new one. For
> example one program to test ALL the property and event of
> Tbutton. An other
> program to test TComboBox etc. The new examples will also benefit for the
> future ‘new’ interface project (native OS X interface?).
> This is a ‘long term investment’ for the Lazarus project. But we
> need these
> testing tools.
> You need to test these new examples first on Linux/GTK system. (Dual boot
> system is recommended working method). Because LCL+GTK is ‘stable’ for
> programming and testing purpose.
What kind of tools are thinking of. Something like a unittesting tool as
DUnit. If you could be a bit more specific, I could maybe help and write
those tools.

> c) Win API knowledge.
> I thing most Delphi programmers does not know much about win 32
> API. Of show
> no interests in studying it. Because they are trained in programming with
> component. This can be a problem for our goal. But for point (b)
> you do not
> need to know the API. For point (a) Api knowledge is recommended.
> I have a
> book ‘Programming windows 95’ by Charles Petzold (1996) it’s about
> programming windows with visual C by using API and not MFC. This
> is where I
> get my info about API.
>
> As you can see ‘hacking’ the Windows32 interface code now is not
> professional for the long-term investment. So we must decide first if we
> want to ‘hacking’ now or follow the above procedure.
> First thing we must know our limitation in both time and knowledge of the
> subject. And do not get over excited about things.
>
> I think the testing tools are the most important things for now. So I
> suggest that we write ALL the testing tools and THEN make the
> decision if we
> want start ‘hacking’ or start documenting (a).

> >I think the best place to discuss is in the maillist.
So do I.