1. EuGL alpha 1 release
After having worked like a maniac all day long I now feel that EuGL is ready
for another release.
I've abandoned the idea about having a routine_id for each WM. Instead, you
have to write your own WndProc in every program (more work for you, less for
me:).
Seriously though, it _does_ add a lot of flexibility without sacrifising any
speed. And you can always use some cut-n-pasting to get things done a bit
quicker.
Among the new things are:
* So-so support for texture-mapping
* ..same goes for display-lists
* Fog
* 3 brand new example programs
* ..and more..
One of the new example programs that I wrote today is a simple clone of
OGLView. It's pretty neat if I may say so myself.. (though it was a pain in
the ... to code). Anyway, check it out and report any errors to me.
The URL is http://home.swipnet.se/progzone/eugl.zip (~283 kB)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
2. Re: EuGL alpha 1 release
- Posted by Irv Mullins <irv at ELLIJAY.COM>
Mar 07, 2000
-
Last edited Mar 08, 2000
----- Original Message -----
From: stab master <stabmaster_ at HOTMAIL.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Tuesday, March 07, 2000 7:43 PM
Subject: EuGL alpha 1 release
> After having worked like a maniac all day long I now feel that EuGL is
ready
> for another release.
Wow! This looks really nice. It's plenty fast, as well.
<heresy>
Wouldn't it be nice if, when Rob implements namespaces, he could
somehow allow _direct_ calls to C routines, so we could do away with
all that c_func() and c_proc() stuff.
</heresy>
It's not that I like c, but it looks like using c calls is going to be
unavoidable
if we intend to use any graphics or windowing library.
Regards,
Irv
3. Re: EuGL alpha 1 release
- Posted by Adam Weeden <adam_weeden at HOTMAIL.COM>
Mar 07, 2000
-
Last edited Mar 08, 2000
> <heresy>
> Wouldn't it be nice if, when Rob implements namespaces, he could
> somehow allow _direct_ calls to C routines, so we could do away with
> all that c_func() and c_proc() stuff.
> </heresy>
> It's not that I like c, but it looks like using c calls is going to be
> unavoidable
> if we intend to use any graphics or windowing library.
>
> Regards,
> Irv
I've actually thought of a nice way for library builders to make libraries
more user friendly. (Not sure how original this is, but I have never seen
it doen, it seems quite obvious to me).
Say you have a mydll.dll with a c_func in it called mycfunc that takes two
parameters of C_INT and returns a C_INT.
mydll = open_dll("mydll.dll")
cfunc1 = define_c_func(mydll, "mycfunc", {C_INT, C_INT}, C_INT}
global function mycfunc(integer first, integer second)
return c_func(cfunc1 , {first, second})
end function
We can now call mycfunc as if it was just a regular function. No more user
playing around with c_func and c_proc. Just an idea.
Adam Weeden
4. Re: EuGL alpha 1 release
- Posted by Everett Williams <rett at GVTC.COM>
Mar 07, 2000
-
Last edited Mar 08, 2000
Irv Mullins wrote:
><heresy>
> Wouldn't it be nice if, when Rob implements namespaces, he could
> somehow allow _direct_ calls to C routines, so we could do away with
> all that c_func() and c_proc() stuff.
></heresy>
>It's not that I like c, but it looks like using c calls is going to be
>unavoidable
>if we intend to use any graphics or windowing library.
>
Heresy, my Aunt Agnes, Euphoria is written in C. You would think
that it would come with a more natural way of talking to it's mother.
Of course, with only native Euphoria data types, it is going to be darn
hard to build all those C arguments without going back to peek and
poke. Maybe some external data types here. Oops, more heresey.
Everett L.(Rett) Williams
rett at gvtc.com
