[AD] allegro introduction on the website |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I just applied the patch below to the website, after a discussion in
#allegro. But maybe I was a bit quick. What do others think?
Modified Files:
readme.en
Log Message:
Replaced a very negative formulation by a positive one. We don't need to
mention other libraries here - nobody will read this and believe he
*must* use Allegro with no other choice :)
Index: readme.en
===================================================================
RCS file: /cvsroot/alleg/allegrowww/data/readme/readme.en,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- readme.en 18 May 2004 19:12:25 -0000 1.7
+++ readme.en 31 Jul 2004 16:29:25 -0000 1.8
@@ -200,18 +200,10 @@
#-beginner_text_4
If you are an experienced game programmer you can quickly get an
idea of how Allegro programs look like by skimming through the
-API or reading the bundled examples. You will find that
-Allegro <em>imposes</em> a DOS-like programming style where your
-game executes from the starting main() function and doesn't require
-threads, in contrast to other libraries which use events. Allegro
-also usually trades flexibility for easiness and abstraction,
-so for relatively complicated things like setting a graphic mode,
-you can end up with a single function call. If you don't like this
-style (which we think is better because you concentrate on writing
-the game instead of manipulating complicated functions) you might want
-to see the <a href="links<dotlangcode>.html">Libraries section of
-the links page</a>, where you can find other libraries providing
-similar functionalities.
+API or reading the bundled examples. Allegro tries to make the task of
+creating games as simple as possible to you, while maintaining the
+flexibility to utilize all the low level power you may want to use at
the
+same time.
--
Elias Pschernig