Hi Peter,

On 7/17/07, Peter Foley <[EMAIL PROTECTED]> wrote:
> All,
>
> I have a question on what you feel the order of precedence is for the
> Admonitions; specifically for Important, Caution and Warning.
>
> Do you feel that the order is Important --> Warning  --> Caution (from
> least strong to strongest).
>

I'd rank them Important -> Caution -> Warning.  Personally it seems
like "warning" is the only one that can cut it for a real screamer -
something reserved for exceptional cases like "Potential catastrophy:
you may erase your hard drive by calling this function".

BTW, I really like docs that lay out their use of admonitions, like
all of the spirit libs.  It would be nice to settle on some simple
universal guidelines for when to use which admonition (sometimes when
I write docs I feel like I'm drawing from a hat when picking an
admonition).

> Also is it safe to say that if these icons were coloured Yellow -->
> Orange --> Red.  That this would help convey the strength of each state?
>

Sure - or if you don't find a yellow and an orange and a red that all
match the color scheme (whatever _the_ color scheme turns out to be),
you could also go with varying amounts of red in the sign - like in
the ones you posted on the wiki you could have the triangle
exclamation icon (red border around white sign) for caution (i agree
that that one is a good caution sign, like you say there), something
similar but with non-red border for important, and one of the full
blown red icons for warning.

BTW, I like your blue "i" for note - nice!

Cheers,

Stjepan

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests: 
https://lists.sourceforge.net/lists/listinfo/boost-docs

Reply via email to