Difference between revisions of "User Manual Work in Progress"

From Inkscape Wiki
Jump to: navigation, search
m (Manualwip.Html moved to User Manual Work in Progress: Confusing name corrected.)
(revamp)
Line 1: Line 1:
This page is intended to inform on Inkscape Manual evolutions.
+
= Illustrations =
If you want to help, just add your name in the () of the concerned line of the [[manualwiptoc.html||table of content]]. If you have ideas, just add a line.
+
  
ROADMAP TO THE MANUAL UPDATE / Work in Progress
+
Here is TODO for illustrations:
* UPDATE icons
+
* UPDATE screenshots
+
* UPDATE Menus
+
* UPDATE Infos for modified commands such as
+
      fill and stroke dialog ( )
+
      UI principles ( )
+
      for full overview, see [[manualwiptoc.html||table of content]]
+
* Create pages for new commands such as
+
      boolean ops ( )
+
      clone tool ( )
+
      for full overview, see [[manualwiptoc.html||table of content]]
+
* Add themes part to help on basic manipulation with info that don't fit in the menus explanation pages
+
      My first Inkscape Document ( )
+
* Translations needed (for updated files only)
+
  
* Create a autogen.sh file, such as for [[The_Gimp]], that generates help files for sources and integrate them in the help menu
+
1. Work out visual style.
 +
 
 +
1.1. Color fill. We probably need a more or less fixed (let's say — recommended) color palette that would take into consideration:
 +
 
 +
* that shape primitives should look uniformly across manual;
 +
* that printed black and white (or, rather, greyscale) version should look good and colors should differ;
 +
* add your point here ;-)
 +
 
 +
We probably should even try to avoid using many color filled objects unless the purpose is to illustrate some kind of color transition. But I'm not married to this argument, so feel free to attack :-)
 +
 
 +
My suggestion is to stick to Tango palette (which is exactly recommendation, not  law).
 +
 
 +
1.2 Stroke width. Should be 2-5px, maybe? Ideas?
 +
 
 +
1.3 Size of objects. We probably do not want shape primitives to have a very much different size unless for specific reason.
 +
 
 +
1.4 Margins. Currently every screenshot has a different set of top/bottom/left/right margins. That means that the space between text and an illustration is different.
 +
 
 +
1.5 Something that I definitely forgot
 +
 
 +
2. Improve existing illustrations to match visual style
 +
 
 +
3. Add missing illustrations.
 +
 
 +
= Uniformness of content =
 +
 
 +
Another thing that really should be fixed is non-uniformness of content in Tools section: every chapter on tools is written in its own way.
 +
 
 +
What generic structure do you envision as best?
  
 
[[Category:Wiki Attic]]
 
[[Category:Wiki Attic]]

Revision as of 15:48, 20 October 2008

Illustrations

Here is TODO for illustrations:

1. Work out visual style.

1.1. Color fill. We probably need a more or less fixed (let's say — recommended) color palette that would take into consideration:

  • that shape primitives should look uniformly across manual;
  • that printed black and white (or, rather, greyscale) version should look good and colors should differ;
  • add your point here ;-)

We probably should even try to avoid using many color filled objects unless the purpose is to illustrate some kind of color transition. But I'm not married to this argument, so feel free to attack :-)

My suggestion is to stick to Tango palette (which is exactly recommendation, not law).

1.2 Stroke width. Should be 2-5px, maybe? Ideas?

1.3 Size of objects. We probably do not want shape primitives to have a very much different size unless for specific reason.

1.4 Margins. Currently every screenshot has a different set of top/bottom/left/right margins. That means that the space between text and an illustration is different.

1.5 Something that I definitely forgot

2. Improve existing illustrations to match visual style

3. Add missing illustrations.

Uniformness of content

Another thing that really should be fixed is non-uniformness of content in Tools section: every chapter on tools is written in its own way.

What generic structure do you envision as best?