[lazarus] Ports to other platforms (was: Client area under win32)

Marco van de Voort marcov at stack.nl
Thu Sep 19 09:36:39 EDT 2002

[ text/html is unsupported, treating like TEXT/PLAIN ]

[ Charset ISO-8859-1 unsupported, converting... ]
> <table border=0 width="100%" cellpadding="8"  cellpadding="8"><tr><td bgcolor="#ffffff"><P><SPAN style="FONT-SIZE: 11px; COLOR: #000000; FONT-FAMILY: monospace">Hello,</SPAN></P>
> <P><SPAN style="FONT-SIZE: 11px; COLOR: #000000; FONT-FAMILY: monospace">I think that for the whole Lazarus project, which was originally intended as a multiplatform tool (as stated in the web page...), the best way to develop it is in a way that could allow the easiest porting to other platforms.</SPAN></P>
> <P><SPAN style="FONT-SIZE: 11px; COLOR: #000000; FONT-FAMILY: monospace">Best regards.</P>
> <P><BR><BR>-- <BR>Ram?n Bosque Pueyo [rbosque at eresmas.com] &nbsp;<BR>http://usuarios.tripod.es/rbosque/index.html<BR><BR>----- Mensaje Original -----<BR>Remitente: "Gerry Ferdinandus" gerry_ferdinandus at hotmail.com<BR>Destinatario: lazarus at miraclec.com<BR>Fecha: Mi?rcoles, Septiembre 18, 2002 11:58am<BR>Asunto: [lazarus] [win32] Client area under win32<BR><BR>&gt;Windows 32 interface is a long time project. So we need some ?project <BR>&gt;management method? implemented here.<BR>&gt;<BR>&gt;a) To make this project success full we need some good documentation. <BR>&gt;Like <BR>&gt;what is implemented at message level and things still need to be done <BR>&gt;etc. <BR>&gt;So we need some agreement about the document structure and the <BR>&gt;contents.People come and go. But documentation stays. If will also <BR>&gt;help other <BR>&gt;potential windows interface programmer.<BR>&gt;<BR>&gt;b) Testing tools.<BR>&gt;For testing our interface we need some testing programs. The Lazarus <BR>&gt;examples are not suitable for our purpose. So we need some new one. <BR>&gt;For <BR>&gt;example one program to test ALL the property and event of Tbutton. An <BR>&gt;other <BR>&gt;program to test TComboBox etc. The new examples will also benefit for <BR>&gt;the <BR>&gt;future ?new? interface project (native OS X interface?).<BR>&gt;This is a ?long term investment? for the Lazarus project. But we need <BR>&gt;these <BR>&gt;testing tools.<BR>&gt;You need to test these new examples first on Linux/GTK system. (Dual <BR>&gt;boot <BR>&gt;system is recommended working method). Because LCL+GTK is ?stable? <BR>&gt;for <BR>&gt;programming and testing purpose.<BR>&gt;<BR>&gt;c) Win API knowledge.<BR>&gt;I thing most Delphi programmers does not know much about win 32 API. <BR>&gt;Of show <BR>&gt;no interests in studying it. Because they are trained in programming <BR>&gt;with <BR>&gt;component. This can be a problem for our goal. But for point (b) you <BR>&gt;do not <BR>&gt;need to know the API. For point (a) Api knowledge is recommended. I <B
es Petzold (1996) it?s about <BR>&gt;programming windows with visual C by using API and not MFC. This is <BR>&gt;where I <BR>&gt;get my info about API.<BR>&gt;<BR>&gt;As you can see ?hacking? the Windows32 interface code now is not <BR>&gt;professional for the long-term investment. So we must decide first if <BR>&gt;we <BR>&gt;want to ?hacking? now or follow the above procedure.<BR>&gt;First thing we must know our limitation in both time and knowledge of <BR>&gt;the <BR>&gt;subject. And do not get over excited about things.<BR>&gt;<BR>&gt;I think the testing tools are the most important things for now. So I <BR>&gt;suggest that we write ALL the testing tools and THEN make the <BR>&gt;decision if we <BR>&gt;want start ?hacking? or start documenting (a).<BR>&gt;<BR></SPAN></P></td></tr></table>

Please use a normal message format.

More information about the Lazarus mailing list