Le 15.10.2007 02:09, Warp nous fit lire :

>   Perhaps it would be a good idea to distribute these things into
> higher-level sections, such as "Core features", "Scripting language",
> etc.

And a change of design would cost you a lot to change the pages
hierarchy ?
How would you deal with a feature available as Core in XX and
Scripting in YY ?

maybe tag/icons for 3.1g/3.5/3.6/3.7/4. must be duplicated by
categories.

Let's make a "Core 3.7" logo, and so on.
I would suggest the feature-extension "not
available","Core","Scripting","Patch".

Style with icons in wiki is really easy, once you found it.

A new user (better, an innocent user) does not have to know the
internal of the product to find the information. An intuitive
approach should all that would be required.
Hence my first proposal: understanding what is a shape is at least
something a 7 year-old child can do.

Of course, some grow-up might be needed for more advanced concept,
but they should not be ordered by implementation.

I recognised section 11/ was a late addition, trying to keep the
"official" clean.

-- 
The superior man understands what is right;
the inferior man understands what will sell.
-- Confucius

Post a reply to this message