Hmm, that's a MediaWiki thing. Here's what it looks like default (without my css):

{"name":"603662","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/6\/2\/62556824fbd53d969a874cfeff20cd59.png","w":911,"h":830,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/6\/2\/62556824fbd53d969a874cfeff20cd59"}

I think what happens is the thumbnail will start (vertically) at the section where you put the thumbnail, but if the sections overlap, then the thumbnails will stack. It's not as cool as the allegro.cc way

If I narrow the window, that seems to support my hypothesis:
{"name":"603663","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/1\/8\/188cae9d5133d70f5a26dbaafdce344c.png","w":602,"h":830,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/1\/8\/188cae9d5133d70f5a26dbaafdce344c"}

I'm not sure there's anything I can do on that one. I would recommend that you just embed the images, not as thumbnails.

Bleh, you are telling people to places DLLs in system32 by hand, to place files in the VC directories, etc. There's a reason I write my own tutorials.

^{I confess, I used to tell people to do that too.}

Feel free to edit it. It's like, a Wiki and stuff.

I wish you would. My grammar is shameful

Anyway, I know it's not best practices, but I just threw it together; making incremental steps here and there. At least I'm putting something on the Wiki, and hopefully motivating others to do the same. I'll come back later and clean it up; maybe even write an installer. It'd certainly be nice to have an MSVC project template, which is on my list of things to do.

Thank you for the feedback.

Damn auto-lock system, I have no time yet, but if I don't write something it's going to be locked.

Anyway, I was seeing the new pages (Allegro 5 MSVC 2010 Inst. and Grid Coordinates vs. Pixel Coordinates) which are pretty good, but for me they're not well placed. I don't know if they're there just temporally.

Instructions about how to install allegro 5 should be simply an "Allegro 5 Tutorial", we could create another section inside the "Allegro 5 Tutorial" besides "Abstract" which it could say "Installing Allegro 5" then "Select your IDE" and there is where I want to place the Code::Blocks instructions, and inside each IDE might be instructions for different Operating Systems.

About "Grid Coordinates vs. Pixel Coordinates" is very difficult to know in which section we could include this, because it's not properly a "Game Design" or a "Concept" about something, but, if Allegro 5 draws primitives different than Allegro 4, then could be placed inside "Allegro 5 Tutorial" since is something related only to how Allegro 5 works.

Allegro 5 Tutorials
  
  ★ Installing Allegro 5
     
     • Visual Studio 2010
     • Code::Blocks 10.05
          | Windows
          | Linux
     • DevC++
          | Windows
          | Linux

  ★ Abstract  

     • Displays: Learn to create a display
     • Events: Learn about events and how to use them
     • Timers: Learn how to use timers
     • Bitmaps: Learn how to create and draw bitmaps
     • Input: Learn how to get input
     • Addons: Learn about Allegro's various addons
          • Primitives: Learn how to draw primitive shapes
               | Grid Coordinates vs. Pixel Coordinates
          • Fonts: How to use fonts and draw text
          • Audio: Learn how to play audio

What do you think??

I'd also NOT have a section for Dev-C++. That only encourages people to use it.

We should not support an outdated, end-of-life IDE. Doing so just enables users to keep using it. We should not provide any tutorials for it, and point them to a more modern IDE that's still supported and developed.

If someone is that set on using it, they can figure out how to make it work themselves. If they can't figure that out, then they probably shouldn't be programming anyway.

You may want to discuss x-code on OS X. I personally find it atrocious, but it's the Apple provided IDE. Not sure if there are any other popular IDEs to discuss for Linux.

Definitely should discuss XCode.
Chicken and egg problem though: most of us who know Allegro don't know XCode and those who don't know XCode don't know Allegro because there is no discussion for how to use Allegro with XCode.

The main thing for Linux is probably the commandline setup (which is fairly straightforward, thanks in part to pkg-config) which will actually work exactly the same on OS X.

I agree, the only mention of Dev-C++ should be the advice not to use it.

Btw., is there a place in the Wiki which explains how to get the 4 versions of MinGW listed under http://allegro.cc/files? I just wanted to give a link to someone in another thread where to download them and searched on mingw.org but have a hard time figuring it out (And I'm not using Windows myself.)

I see, so can just click that .exe at the top. But which of the 4 versions will that give you, and how do you get the other 3 versions?

Looking at the changes so far, I'm no sure the SVN pages should have been renamed the way they were. They are explicitly for SVN. Though I suppose someone could add general information to it, but it should have happened before the rename.

No, most people will be using the source tar ball. Or eventually^[1], official debian packages.