![]() |
|
project links added to online manual |
Matthew Leverton
Supreme Loser
January 1999
![]() |
The online manual now contains links to various projects (sorted by user rating) with source code. Example: screen. The idea is that if you don't understand how the Allegro function works, you can download the source to one of the listed projects and see how it's used. Of course this requires the source code to be uploaded to Allegro.cc. Right now only zip files are supported, but other formats will be supported soon. At some point, I also plan on making the source code viewable (read-only) online. -- |
OICW
Member #4,069
November 2003
![]() |
Sounds interesting and usefull too. I like the idea. [My website [www.oicw.cz]][CppReference [www.cppreference.com]][Pixelate [pixwiki.bafsoft.com]][Allegators worldwide][Who's online] |
GullRaDriel
Member #3,861
September 2003
![]() |
Yeah, the manual is growing :-) "Code is like shit - it only smells if it is not yours" |
Trezker
Member #1,739
December 2001
![]() |
Awesome, you've earned yet another fluffy dragon. [My github [github.com]] |
Matthew Leverton
Supreme Loser
January 1999
![]() |
All valid source files have been parsed. I changed the ranking of listed projects to be the most popular projects with the fewest references to Allegro routines. The theory is that the fewer functions that are used (less code), the easier it will be to follow what's going on. Of course it's just an estimate, but it doesn't really matter because any single one of the projects should be sufficient. Also attached is a CSV of the most commonly used Allegro keywords. The count is only the number of different projects the keyword appears in, not the total times its used. -- |
|