1. support to exw
- Posted by Jacques Deschenes <desja at GLOBETROTTER.QC.CA>
Nov 11, 1997
-
Last edited Nov 12, 1997
This message is for those of you who want to support exw.
There is a lot of work to do, I suggest that we advise each others of the
work we
are presently doing to avoid repetition.
There is no need to do 2 copies of the same work.
I'm presently working on commdlg.e and WinMenu.e and it's almost completed.
The first is a wrapper for comdlg32.dll and the second is an aid to the creation
of windows menu.
I hope to post this code next weekend with the apppropiate documementation.
to Daniel,
>To Jaques: it's great to have you around... you're kind of a living
>encyclopedia ;)
Thanks, but to be more realistic, I would say a very tiny encyclopedia,
maybe half
a dictionary. 
Regards,
Jacques Deschenes
Baie-Comeau, Quebec
Canada
desja at globetrotter.qc.ca
2. Re: support to exw
Jacques Deschenes wrote:
>
> This message is for those of you who want to support exw.
>
> There is a lot of work to do, I suggest that we advise each others of the
> work we are presently doing to avoid repetition.
I'm not doing wrappers for anything yet, I'm just playing around with
the raw dll functions at the moment. I've successfully made working
menus, pushbuttons, checkboxes, and radio buttons. It really is
possible! I've figured out how to process menu commands in WndProc, and
detect events for the other controls, but not how to read the state of
each control. I want to figure out dialog boxes next but I'm not sure
if I can do it with only one callback routine. (It might be possible to
share a WndProc by checking the whnd.) I'm probably going to end up
putting all the user32 functions into an include file but I don't plan
to document it.
How's everyone else getting along?
--
_____ _____ _____
________ /\ \ /\ \ /\ \
/ \ \ / \____\ / \____\ / \____\
/ _ \____\ / / ___/_ / /____/ / / ___/_
/ / \ |___| / / /\____\ / \ \ / / /\____\
\ \_/ / / \ \/ / ___/_\ \ \ \ \/ / ___/_
\ /____/ \ / /\ \\/\ \ \ \ / /\ \
\ \ \ \ \/ \____\ \ \ \ \ \/ \____\
\ \ \ \ / / \ \____\ \ / /
\ \____\ \ / / \ / / \ / /
\ / / \ / / \/____/ \ / /
\/____/ \/____/xseal at harborside.com\/____/
3. Re: support to exw
------ =_NextPart_000_01BCEF54.4940B500
Content-Transfer-Encoding: quoted-printable
re: advising of work others are doing
I'm working on an interface to Win32 that doesn't require the coder to =
actually use any of the Win32 calls. I suspect that it would not impact =
anyone else's work, although I would like to INCLUDE other's code, =
expecially common dialogs controls.
The interface is aimed at people who may want to do Win32 coding without =
dealing with the "messy" details of Windows. I'm using Visual Basic as =
my guide. Here's a sample of code using the library:
include win32lib.e
-- create a button
constant button1 =3D create( "pushbutton", "Press Me!", 100, 100, =
120, 40 )
-- give it an action
procedure click_button1()
object result
result =3D message_box( "Goodnight, Gracie", "Say Goodnight, =
Gracie", 0 )
close_window()
end procedure
-- vector the action
onClick[button1] =3D routine_id("click_button1")
-- write something on the window
w_position( 1, 1 )
w_puts( "Hello, World!" )
-- run the window
WinMain("Simple Demo")
As you can see, the user doesn't have to deal with Win32 data =
structures, event loops, or much of anything.=20
At this point, there's not a lot of functionality. Most controls are =
supported, but the only action you can do clicking. Because bind mangles =
routine names, you can't yet bind code created with the library.
One of my future goals is to place a Visual Basic type of front end on =
it - but first things first. :)
I hope to be posting a copy of the program to Robert some time today, so =
I can get some feedback from the group.
Also, I've got some code I converted from Win32Forth for building =
dialogs that I hope to get to some time in the near future. I've given a =
copy to Robert; if anyone feels compelled to take on the project, I =
could give you a copy of the untested code.
-- David Cuny
------ =_NextPart_000_01BCEF54.4940B500
