OpenEuphoria

Re: Fw: Re: Win32Lib - What to do?

• Posted by Ralf Nieuwenhuijsen <nieuwen at XS4ALL.NL> Feb 24, 1998
• 730 views

|
| >or should I not waste my time with this?
|
|  Not sure if this is a waste or not...I know that a port of Mac0S would
|have made a lot of Mac users happier with PC's...I like the idea of being
|able to...
|
|    Start one program with Dos that would act like a shell...
|Like a front end.  Then you could write Euphoria programs that would access
|the shell, and interact with the user through the shell.  Kind of a
standard
|for Eu windowing programs, but to actually install one you would only have
|to download the interface code and data objects.  A mac interface would be
a
|useful alternative, as it would already exist to write for.  If you could
|provide a basic interface, maybe we could add on to it.

    This could be done, ONE simple standard interface used by all programs.
    Put the whole MacGUI in a DLL. (have multiple DLL's for different looks,
an OS2 look, an win95 look, an win98/ie4 look, a macOS look.
    Have ONE header file, that handles the input from and too the dll's.
    The user just tells the look they want.
    Example:
    "MacOS"
    And it will use: EUMACOS.DLL
    THe routines are all the same in every DLL, so we could just add a new
DLL to use with the GUI.

Ralf

|    Hmm... well anyway.  I really wanted to ad that your program made it
|easy for me to create windowing programs.  I like that, and can use that,
|except for the lack of a refresh.  Adding refresh capability and especially
|graphics would be icing on the cake...
|    Thanks for you for taking so much time to help us...

Maybe when we have a full windows GUI library, we could make an WYSIWYG
editor ?
Then Visual Basic will be dead, like QBasic.
(Well, Control Creation Support, Active-X support, etc.)

Yes, about that, VBX's, OCX's and vbrun???.DLL's are all dll's
VBX's & OCX have some standard routines. (it are DLL's with some
restrictions like, this has to be there, and this)

If we can het a spec somehere (what routines will be available in every
OCX/VBX to integrate with them like VB does, we could write a .E to load and
use an VBX or OCX.
I mean, together with a VBRUN dll we could even allow a program to launch an
VB-form. (just ask one of those guys that write vb-decompilers how VB makes
an .exe)

BTW (Upfrom version 5) VB compiles the programs, so decompiling isn't
possible THAT easy.

Ralf