Well, who's up for it?

amarillion, can you fire up the TINS website again? Let's do some kind of hack for the Holly Days.

We can hack Allegro source / wiki / docs, or we can have a holiday hack. What say you?

No rules? Free for all? What about rolling for genre? IDK. Add certain special effects? Improve an old program? I need at least a week for a holiday hack. We should do something like Dec 17th-31st or so? What's a good date?

I'm working on molto (ala Molto Allegro). My D wrapper for Dallegro which is a wrapper for allegro in D which is a wrapper around OpenGL on Linux...

On the otherhand, my syntax is awesome:

draw(text("hello world"), tint(255,0,0), pos(25,25));
draw(bitmap(bmp_sprite1), pos(25,25), tint(255,255,0)); 
draw(bitmap(bmp_sprite1), pos(25,25), tint(255,255,0), flip(vertical), rotate(pi));

- order of arguments doesn't matter

- optional arguments (in any order, as opposed to on the end like in C/C++/traditional D)

- ALL COMPILE TIME that compiles down to the correct al_draw_bitmap or al_draw_textprintf, etc

- Very easily extensible.

- Doesn't explode the number of unique functions (al_draw_tinted_scaled_rotated_bitmap) with additional features,

- so you can add less used ones like "centered" vs top-left-aligned without quadratically adding more function signatures.

- CLEARLY labeled, and grouped arguments. "pos" is a position. No matter what argument you specify or what line it is. It's like the pleasure of a dynamic language like Javascript but it compiles to nothing.

- Whereever I can, I use the signature of the API itself to be a clue as to the correct way to use the functions.

- Ever use a draw function without initializing the pre-requisite allegro_init function? You can't. You simply cannot. Because you can't call a function (method!) without creating a gfx object, and the object cannot exist unless you call it with a constructor that implies the correct pre-requesites as its required arguments.

- For example, in Allegro 5, a timer cannot be used without being attached to queue. So in Molto, a timer cannot be constructed without providing a queue. The linkage is now obvious. The API is documentation.

If there was any doubt - I'm in.