OpenEuphoria

Re: Euphoria 2.0

• Posted by David Cuny <dcuny at DSS.CA.GOV> Nov 06, 1997
• 602 views

------ =_NextPart_000_01BCEAA1.96594BC0

>When someone figures out how to do windoze apps with it, let me know.  I
>don't have time to trailblaze it, so I need giants whose shoulders I can
>stand on.

>Anyone done anything even remotely interesting with it yet?

I took a look at it, and decided to wait until I got my hands on a version
that supported more than 300 lines... It's too darned hard to write code
without a decent debugger, and the code to generate a basic window takes
about 250 lines.

I wish that Euphoria had a nicer way to maintain multiple versions on the
same machine, so I could keep coding using my registered 1.5a version,
and still play with the unregistered 2.0 alpha. Currently, I have to rename
the directories (FUPHORIA and EUPHROIA) manually to toggle between the two.

Maybe I'll write a routine that does it automatically... (mumbling out loud)

If people are looking for a good Win32 book, I'd highly recommend "Programming
Windows 95", by Charles Petzold. It shows how to code Win95 using C, not C++,
so you can see the calls to the Win32 library.

If you want a listing of all those magical constants in text form (instead of
the WinHelp file), you need a WIN.H file. There is a FREEWARE C compiler for
Win32 called "LCC" at:

   http://207.33.3.10/lcc-win32/

that contains a WIN.H file, so you can get the values of all those constants in
a plain text format. I think it's a compressed version of the one include in
the GNU Win32 library. Anyone wanna convert a 13,769 line file into a Euphoria
include file? ;)

I noticed in the documentation that only ONE Windows callback is supported
in this alpha release (although more are planned). I think this means that
(correct me if I'm wrong, Robert) your program can only talk to ONE window.

Since Win32 implements controls (such as buttons, check boxes, etc.) as child
windows, this means (I think) that this current release CANNOT support these
controls in a parent window. I suspect the same applies to dialog boxes,
although I could be mistaken.

Of course, there's nothing to prevent anyone from drawing stuff inside a
window frame that /looks like/ a Win32 control. Add some mouse event trapping
to it, and you've got something that looks and feels like the real thing.

The illusion would be broken if you tried to display a drop-down list in a
minimized window, and it did't extend beyond the border of the window. On the
other hand, you could avoid that problem by not using that particular control.

-- David Cuny

BTW: I'm still working on reconciling Pete's SVGA code into the the EE editor.
     I had promised some people that it would be released this week, but it
     looks like I'm going to slip another week. Sorry. I've got everything but
     the EE file reconciled.

     And thanks to all the people who have been sending in bug reports!
------ =_NextPart_000_01BCEAA1.96594BC0