Allegro.pas is a wrapper to allow Pascal language to use the Allegro game programming library to create your own games in good old Pascal or the modern Object Pascal programming languages. Read more details on the introductory page.
Thanks to a note at the Discussion forums, I did some fixes and updates to version 4.4.5. They're a few, and mostly on the alwin unit. Actually I'm not sure that it works perfectly, but it compiles.
I've also updated the documentation, adding a search engine (actually just added an option to pasdoc). You can read it online or download as you wish.
As always, you can download from the download page.
About 3 years after 5.0.alpha, a new release of branch 5 (now TRUNK) was released today. It has a lot of improvements, and should be slightly more stable than previous alpha. You can download it from here. Any feed back is welcome.
I'll use it in the comming TINS 2016 contest, and I plan to use my entry as demonstration game for the library.
Yesterday, Allegro 5.2.0 was released. I tested it and it's quite nice. It fixes suff from 5.0 and adds new things, like the new 3D API that avoids the need of OpenGL or DirectX. It is much like the 3D routines used in pre-5 versions but using hardware acceleration.
So, Allegro.pas TRUNK will drop 5.0 support and go to the 5.2. Actually I want to release a new beta before TINS 2006, announced by Amarillion few days ago. This is, before Friday May 13.
Few time ago, Free Pascal version 3 was released. Sometime later, Lazarus 1.6 was released. I didn't test them 'till today, and I found a few issues. They're not major issues, just some warnings here and there. So I did a few changes and uploaded to the SVN.
On the other hand, I was thinking about what demonstration game to ship with Allegro.pas 5 branch. I was thinking in an old idea: first person snowball battle. So may be I'll create a prototype using version 4.4 then port it to version 5.0 (or may be 5.1).
Note: This was published in other of my current projects: Gesbit.
Some days ago, Leo has posted a comment asking why does Gesbit stay in SourceForge. I ansered that I know that GitHub is the trend and SourceForge have a bad reputation, but I prefer SVN over GIT and SourceForge did work for many years.
Later I found that new owners of SourceForge posted an article in his blog on day before Leo posted his comment. You can read it, but they recognize SourceForge's bad reputation proble, and talks about planning how to fix it. And they started by terminating the DevShare program, which was one of the main sources of that bad reputation. They also promised that there will be more changes in the future.
That's mean that I'll keep my SourceForge projects here for a while.