OpenEuphoria

2. Re: wxEuphoria vs Win32EuLib ?

• Posted by mattlewis (admin) Jun 11, 2009
• 995 views

There are some things that win32lib does that wxEuphoria does not, and vice versa. One advantage of using win32lib is that you do not have an additional dll/so that must be installed by end users.

Matt

4. Re: wxEuphoria vs Win32EuLib ?

• Posted by mattlewis (admin) Jun 11, 2009
• 1050 views

A dll/so (dynamically loaded library / shared object) is just some code that someone has written and compiled into a form that can be used by other programs. So it's really a matter of wanting to use something that exists in a dll.

For example, in order to access the Win32 API, in order to create windows, etc, Windows provides many different dlls that do different things. The most common are kernel32.dll and user32.dll. There are many others.

I'm not sure exactly what you mean here. Are you talking about a feature of wxWidgets that wxEuphoria does not yet provide?

Different features could be built into a single dll, just like you can put more than one euphoria source code file into a program. Each operating system will need a different dll, as they all have slightly different file formats, as well as underlying libraries that the dll will need to use.

"dll" and "so", respectively. Well, Ok, sometimes on windows, you'll get .ocx files, which are ActiveX components, and are really dlls, though they also have to follow some additional conventions.

Actually, sometimes, on unix-like systems, you'll get extra version information appended after the .so. wxEuphoria does this to make it easier to figure out which version of the library you're using:

   libwxeu.so.13 
   libwxeu.so.14 
   ...etc 

There's often also a symbolic link without the version information that points to (usually the latest, or current stable) the so. This allows users to not have to worry about the version number (assuming that different versions are compatible, of course).

Matt

6. Re: wxEuphoria vs Win32EuLib ?

• Posted by jeremy (admin) Jun 11, 2009
• 1026 views

[/quote]

You need to add in there dylib. For instance, wxEuphoria *should* run on OS X also, no? I can take an unaltered C wxWidgets app and compile/run on Windows, Linux and OS X.

In the past, open_dll would take a lib file to load and would return -1 if it couldn't be loaded. You would then try the next, and next, and next and finally err. However, the new open_dll in 4.0 saves you a lot of work, simply do:

constant hDll = open_dll({ "myfile.dll", "myfile.ocx", "myfile.so", "myfile.so.1", "myfile.so.1.0", "myfile.so.1.0.0", "myfile.dylib" }) 
if hDll = -1 then 
    crash("Could not open myfile shared library.") 
end if 

It will cycle through the list and return the handle to the first one that loads successfully.

Jeremy

8. Re: wxEuphoria vs Win32EuLib ?

• Posted by mattlewis (admin) Jun 11, 2009
• 1049 views
• Last edited Jun 12, 2009

Well, there's been no release so far that will work with eu 4.0, which has itself been in a state of flux. So since you're using eu 4.0, I suppose you're right. The next release will work with both 3.1 and 4.0.

wxEuphoria v0.12.2 should be stable for use with eu 3.1.

Yes, auto-sizing is a wonderful thing. Once I got used to it, I found it a lot easier than even using an IDE. No more dragging controls around. It all just works.

I think my favorite custom control is the wxGrid. It does some nice things, many of which, admittedly, Phil Russell's win32lib add-on EuGrid does, too.

Hey, Greg's been doing more with wxEuphoria lately than I have. I'm actually looking forward to getting eu 4.0 out the door so I can have more time to focus on my other stuff like wxEuphoria.

Matt

10. Re: wxEuphoria vs Win32EuLib ?

• Posted by euphoric (admin) Jun 11, 2009
• 1008 views
• Last edited Jun 12, 2009

That's true! How could I forget?!? Sorry Greg!

So, I'll hire ninjas to kidnap you guys and bring you to the dungeon, where you'll toil away forever on wxEuphoria. Okay, at least until v1.0.