> Ok I will :) But I can't promise I could get some time before b3, it
> seems we are going to have b4 so I don't see this as a problem (nor a
> blocker), of course for this to work what you say below has to be
> implemented, which I'm +1

>> One more thing: I'd finally like to change the DOM structure and CSS of
>> the quickstart template to match the structure generated by the JS
>> version. Mainly so both versions can be used interchangeably and because
>> the current one sucks ;)  Why? Because:

>> 1) The class of  the message should be conveyed in a... class attribute.
>> The current implementation makes impossible to refer to the *unique* div
>> that holds the flash in a reliable way from JS code. The id should
>> remain static, the class should vary with the kind of message (not the
>> other way around)

>> 2) If the flash message is wrapped in a div inside the "flash" div then
>> one can implement floating centered messages easily.

>> To make it easy to visualize, the dom structure that the js code
>> generates is like this:

>> <div id="some_id_of_your_liking">
>>    <div class="status_code">Message</div>
>> </div>

>> So the CSS style this could be something like:

>> #some_id_of_your_liking {
>>    display: none;  /* Recommended so a conditional can be avoided, the
>> JS code will make it visible */
>>    ...
>> }

>> #some_id_of_your_liking .ok { ....}
>> #some_id_of_your_liking .warn { ....}
>> #some_id_of_your_liking .error { ....}

>> Please strip the status_X prefix from the status code names, it is
>> redundant to say:

>> flash("lalalala", status="status_ok")
>> much nicer (IMHO) and less typing (mathematically provable):
>> flash("lalala", status="ok")

>> If no one object I'll implement these *slightly* breaking changes (for
>> existing users) tomorrow. Note that the default will still be non-js
>> flash messages, I'm just proposing to change the dom structure and CSS
>> to keep both in sync so it is easy to change between them.