1. Re: Graphics for Win32
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BDECC0.214051C2
charset="iso-8859-1"
Ralf mentioned:
> And, Robert once dropped he will look into graphics support
> for Win32. Something we're still waiting for.
Just thought I'd drop a Win32Lib status report. I should have a minor update
available in a day or so that add some minor functions:
cut/copy/paste/clear/undo, as well as fixing limits on structures (so you
can have an unlimited number of controls).
I've got getPixel coded; I'll try to add setPixel and a number of
shape-drawing routines (drawRectangle, drawRoundedRectangle, etc.) into the
release as well.
After that, I'll try to get into something I've been avoiding with Win32Lib:
bitmap support. You'll know when I'm working on it, because I'll be posting
a lot of questions to this forum.
[Win32Lib: Naming Convention]
I've noticed that the Win32 C calls look like:
Rectangle( hdc, xLeft, xTop, xRight, yBottom )
For Win32Lib, the equivalent would be:
drawRectangle( id, xLeft, xTop, xRight, yBottom )
I'm considering changing the naming conventions to match their C
equivalents. My personal (preferred) coding style is:
TheConstant
theFunction
theVariable
For Win32Lib, the naming standard would become:
THE_CONSTANT
ProcedureCall
variableName
Of course, code written under the prior convention would break, but it
shouldn't be that hard to fix. Using upper case for function calls would
distinguish routines from variables, and hopefully avoid name conflicts.
Comments?
-- David Cuny
------_=_NextPart_001_01BDECC0.214051C2
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2232.0">
<TITLE>RE: Graphics for Win32</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Ralf mentioned:</FONT>
</P>
<P><FONT SIZE=3D2>> And, Robert once dropped he will look into =
graphics support </FONT>
<BR><FONT SIZE=3D2>> for Win32. Something we're still waiting =
for.</FONT>
</P>
<P><FONT SIZE=3D2>Just thought I'd drop a Win32Lib status report. I =
should have a minor update available in a day or so that add some minor =
functions: cut/copy/paste/clear/undo, as well as fixing limits on =
structures (so you can have an unlimited number of =
controls).</FONT></P>
<P><FONT SIZE=3D2>I've got getPixel coded; I'll try to add setPixel and =
a number of shape-drawing routines (drawRectangle, =
drawRoundedRectangle, etc.) into the release as well.</FONT></P>
<P><FONT SIZE=3D2>After that, I'll try to get into something I've been =
avoiding with Win32Lib: bitmap support. You'll know when I'm working on =
it, because I'll be posting a lot of questions to this =
forum.</FONT></P>
<BR>
<P><FONT SIZE=3D2>[Win32Lib: Naming Convention]</FONT>
</P>
<P><FONT SIZE=3D2>I've noticed that the Win32 C calls look like:</FONT>
</P>
<P> <FONT SIZE=3D2>Rectangle( =
hdc, xLeft, xTop, xRight, yBottom )</FONT>
</P>
<P><FONT SIZE=3D2>For Win32Lib, the equivalent would be:</FONT>
</P>
<P> <FONT =
SIZE=3D2>drawRectangle( id, xLeft, xTop, xRight, yBottom )</FONT>
</P>
<P><FONT SIZE=3D2>I'm considering changing the naming conventions to =
match their C equivalents. My personal (preferred) coding style =
is:</FONT>
</P>
<P> <FONT =
SIZE=3D2>TheConstant</FONT>
<BR> <FONT =
SIZE=3D2>theFunction</FONT>
<BR> <FONT =
SIZE=3D2>theVariable</FONT>
</P>
<P><FONT SIZE=3D2>For Win32Lib, the naming standard would =
become:</FONT>
</P>
<P> <FONT =
SIZE=3D2>THE_CONSTANT</FONT>
<BR> <FONT =
SIZE=3D2>ProcedureCall</FONT>
<BR> <FONT =
SIZE=3D2>variableName</FONT>
</P>
<P><FONT SIZE=3D2>Of course, code written under the prior convention =
would break, but it shouldn't be that hard to fix. Using upper case for =
function calls would distinguish routines from variables, and hopefully =
avoid name conflicts.</FONT></P>
<P><FONT SIZE=3D2>Comments?</FONT>
</P>
<P><FONT SIZE=3D2>-- David Cuny</FONT>
</P>
</HTML>
------_=_NextPart_001_01BDECC0.214051C2--
