[docs] icons for common questions

Hi, Maybe it was an idea to have icons to show - on the list of libraries - in the opening page of each library that quickly reminds the user that - the library supports serialization - the library supports no exceptions Too pop-smart? -Thorsten

Thorsten Ottosen <tottosen@dezide.com> writes:
Hi,
Maybe it was an idea to have icons to show
- on the list of libraries - in the opening page of each library
that quickly reminds the user that
- the library supports serialization - the library supports no exceptions
Too pop-smart?
Sounds nifty to me. Small keyword text below each icon or maybe tooltips, plus click-through to find out what it means in detail, would make this really useful. -- Dave Abrahams Boost Consulting www.boost-consulting.com

David Abrahams wrote:
Thorsten Ottosen <tottosen@dezide.com> writes:
Hi,
Maybe it was an idea to have icons to show
- on the list of libraries - in the opening page of each library
that quickly reminds the user that
- the library supports serialization - the library supports no exceptions
Too pop-smart?
Sounds nifty to me. Small keyword text below each icon or maybe tooltips, plus click-through to find out what it means in detail, would make this really useful.
One other relevant categories: - header only - rtti required It is a common misconception that boost libraries needs building. I'm not of a icon making guy, but simply a link might be enough, e.g.: * any - [header only] Safe, generic container for single ... * array - [header only] [serialization] STL compliant * assign - [header only] [serialization] [no exceptions] Filling ... The link could be a different style than the link for the library -Thorsten

Thorsten Ottosen wrote:
David Abrahams wrote:
Thorsten Ottosen <tottosen@dezide.com> writes:
Hi,
Maybe it was an idea to have icons to show
- on the list of libraries - in the opening page of each library
that quickly reminds the user that
- the library supports serialization - the library supports no exceptions
Too pop-smart?
Sounds nifty to me. Small keyword text below each icon or maybe tooltips, plus click-through to find out what it means in detail, would make this really useful.
One other relevant categories:
- header only - rtti required
This is a really good idea. I'll suggest some others: - thread-safe (in the re-entrancy/mutex sense) and because it just came up as I'm learning Boost.Statechart: - protects shared data (i.e. no worries about cache coherence issues) I'm not familiar with Boost.Typeinfo yet but support for that seems a similar thing to serialization. -Dave
participants (4)
-
David Abrahams
-
David Greene
-
Thorsten Ottosen
-
Thorsten Ottosen