1. RE: Lin32Lib?
Irv suggested...
> I think the only choices are to learn C++, or come up with a
> thousand bucks to buy Kylix. :(
A thousand bucks split amongst 200 Euphorians is only $5 each... 
2. RE: Lin32Lib?
jbrown105 at HotPOP.com wrote:
> > If Iused your Graphics Engine, then I could just port Dos32Lib, and use
> that,
> > but it would work in an xterm. WHile a good project, I'd rather use X
> > than
> > SVGAlib.
>
> I mean, it wouldn't work in an xterm. sorry for the typo. The reason it
> wouldn't work is because SVGAlib requires a console, which can't be
> access in
> X.
>
>
I think you should try running Jirri's widget demos
using my library. You and you will see you don't need X.
Bernie
3. RE: Lin32Lib?
hi
i've also had trouble contacting jiri about the widgets lately, so i
think he must be off somewhere enjoying himself.
i can say that until relatively recently he was working on the up-dated
version, and separately working on an improved version of the font
package.
i can also say that i have submitted to jiri an advanced full draft of a
70-page tutorial/documentation for the widgets, which you can take as
indicating that i for one will not be abandoning the project, even if
jiri adopts the odd course of having fun instead.
my work was aimed at encouraging others, both beginners and advanced
programmers, to concentrate on a single GUI library for both linux and
DOS (although DOS regrettably is becoming more and more obsolete with
each new hardware advance). i therefore noted bernie's contribution with
great enthusiasm.
i was hoping that the development project would be embraced by a wider
group. my own expertise is more in writing than coding, so although i
can code reasonable applications, and bug-test, make suggestions etc
from the user-perspective, optimising a definitive library is beyond me.
i also see a significant gap in the tutorial range for euphoria - i
thought the widgets could be used as a vehicle for the next step up from
david gay's beginners' tutorial.
at the moment, the bleeding edge version of the widgets is only partly
working, and that part is incompatible with the last uploaded version,
so i am unable to sensibly use the widgets at all or finalise the
documentation, which has been adapted towards the latest version.
while we're waiting to hear from jiri, are there others who would be
interested in this project?
cheers
tacitus
Travis Beaty wrote:
> Howdy!
>
> As I've stated in an earlier post, my biggest problem with going the GTK
> route at
> the moment is due to the fact that, after repeated tricks and/or
> tweaking, I've
> yet to get Euphoria to link up to the GTK .so file using open_dll().
> So,
> Bernie's idea is gaining popularity in my mind ... I've downloaded
> eu_engin and
> I'll be taking a look at it.
>
> Concerning Jiri's widgets, is he still supporting the project? I've
> written to
> him and asked, but I haven't gotten a reply (he's no doubt taking full
> advantage
> of retirement and autumn down there in the south 40. Back six months
> or so
> ago, he had a small disaster in which what was his most recent version
> of the
> widgets were accidentally deleted. Since then, I haven't heard anything
> about
> them.
>
> Jiri? Mr. Craig, any thoughts on the open_dll() dilemma?
>
> -- Travis --
>
>
4. RE: Lin32Lib?
David Cuny wrote:
> But this caused me a bit of grief. I had written a Euphoria program to
> read
> the GTK include files, and generate wrappers for the structures. But
> apparently because of alignment issues, the position of structure fields
> is
> different under Windows than it is in Linux. That meant that some of the
> code would fail - seemingly randomly - under Linux.
actually, some of your GTKLib demos crashed under Windows but worked
perfectly under Linux
5. RE: Lin32Lib?
> -----Original Message-----
> From: Irv Mullins [mailto:irvm at ellijay.com]
> Most of the good packages, like QT, are written in C++, which
> makes interfacing
> with them very difficult.
Actually, I don't think that it would be as difficult as you might think
(not that it'll be simple). Working with COM has given me a new insight on
interfacing with C++, since that's effectively what happens with COM. Also,
in working with COM, I think I might have solved some other problems that
might get in your way.
Here's what I think you'll need to do:
- Get a hold of the constructor for an object. It should return a pointer
to the object.
- Wrap the member functions just like you would with C.
- Pass the pointer to the object as the first argument in any function call
(C++ does this implicitly).
I suspect that the functions will have to be loaded by ordinal (C++ name
decoration isn't much to look at), so you'll probably need to get your hands
on a lib file or some other kind of documentation on the lib. This could be
the most difficult part, except that I guess since this is linux, you ought
to be able to get a look at the full source, right?
And then you'll probably need to load the .so's manually (since
open_dll/define_c_func don't seem to work by ordinal). So you'll probably
have to call them by pointer (no problem, since fptr.e in EuCOM should work
in linux :).
Matt Lewis
