1. [WIN] Allegro for Euphoria Demo release
- Posted by Ray & Debbie Smith <smithr at IX.NET.AU>
Nov 05, 2000
-
Last edited Nov 06, 2000
Hi Everyone,
I have sent Rob a copy of my Euphoria wrapper for Allegro.
( It's also available at
http://members.nbci.com/ray_223/sw/euAllegro_demo.zip )
It is a "demo" since there is no doco and and hasn't been tested.
I will be changing quiet a few things in the next few weeks before I make an
alpha release which should contain some doco and be upwards compatiable
with future releases.
I have wrapped about 60 functions (out of the hundreds available) and
converted
about 10 demos (out of about 40).
I am releasing this demo version of euAllegro as some of the demo programs
are pretty cool and I'd like to know if anyone has problems running any of
the
demos ... and to drum up some interest!
Its a windows only version and I think you need DirectX 6 (well that's what
I have
and it works for me).
Allegro is an excellent library and am pretty surprised no one has done any
Euphoria
wrappers yet.
It has everything you need to make games ... except it isn't a 3d engine ...
and doesn't have any comms libraries .. .apart from that think of anything
else
you need to write games and Allegro can help you!
I haven't included the source code for my DLL but if anyone is interested I
can
send them a copy (it's pretty ugly, it isn't a coincidence I like
Euphoria!).
My plan is to:
* re-organise how I call the Allegro routines,
* standardise my naming conventions to be as close as possible to the native
Allegro calls
* determine how I can document it. Since it's so close to the native port
I'm hoping
to just append notes to the offical doco.
* then march through all the Allegro functions available and wrap them to
Euphoria.
* Write some little demos or games to show the power euAllegro can achieve.
* Investigate Linux usage. This might slip up the list somewhere.
This will probably take a few months .. maybe upto 6 months I guess.
I'd love to hear from anyone who downloads the euAllegro runs the
demos.
Ray Smith
2. Re: [WIN] Allegro for Euphoria Demo release
- Posted by Ray & Debbie Smith <smithr at IX.NET.AU>
Nov 05, 2000
-
Last edited Nov 06, 2000
Hi,
I have also loaded the C source code, executables and native allegro
manual at:
I have uploaded these so anyone interested can check the performance between
pure
C and Euphoria implementations of the same programs. I included the manual
so any interested can get all the info they need. The manual is in RTF
format
and can be opened with wordpad.
Visually I can't see any speed differences between the C executables and the
Euphoria demos. I haven't done any benchmarks.
Ray Smith
3. Re: [WIN] Allegro for Euphoria Demo release
It seems like you need a pixelformat detection routine.
When I ran EuBlend.exw I got a 15-bit gfx mode, while Allegro thought it was
16-bit.
Good job though..
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
4. Re: [WIN] Allegro for Euphoria Demo release
>> It seems like you need a pixelformat detection routine.
>> When I ran EuBlend.exw I got a 15-bit gfx mode, while Allegro thought it
>was
>> 16-bit.
What the program does is loop through the following display depth sequence {16,
15, 32, 24, 0}
The first mode that works is used.
If I send you the original C executable version of the blend demo (only about
7kb) can you run it
and tell me if it has the same results?
That way I can tell if it something I have done in the wrapper or demo, or
something in the base
Allegro library.
Thanks for the interest.
Ray Smith
5. Re: [WIN] Allegro for Euphoria Demo release
Actually, I already know what the problem is:
Whenever I try to set a 16-bit (565) graphics mode through DirectDraw I get
a 15-bit (555) mode instead. So it's a either a DirectX-related or a
driver-related problem. This does not happend when using VESA libraries
under DOS (though I've seen it happend on other computers). So what you'd
need is:
1) a function, internal or not, called getPixelFormat() or whatever.
2) use the information from this function to explicitly tell Allegro wich
pixelformat to use (only important when trying to set a HiColor mode). if
that can be done..
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
6. Re: [WIN] Allegro for Euphoria Demo release
DirectX itself will automatically let you know what pixelformat your
currently are using correctly. The thing is that the custom software graphic
routines Allegro uses needs to know this to draw correctly to the screen.
Basically what you said in your steps... Just wanted to clarify that.
Todd Riggins
------------
Actually, I already know what the problem is:
Whenever I try to set a 16-bit (565) graphics mode through DirectDraw I get
a 15-bit (555) mode instead. So it's a either a DirectX-related or a
driver-related problem. This does not happend when using VESA libraries
under DOS (though I've seen it happend on other computers). So what you'd
need is:
1) a function, internal or not, called getPixelFormat() or whatever.
2) use the information from this function to explicitly tell Allegro wich
pixelformat to use (only important when trying to set a HiColor mode). if
that can be done..
