Difference between revisions of "Inkscape invariants"

From Inkscape Wiki
Jump to navigation Jump to search
m (Reverted edits by HonHn1 (Talk); changed back to last version by GigaClon)
m (→‎Invariants of Inkscape: Added Gnome HIG link.)
Line 5: Line 5:
 
* Full SVG (plus XML, CSS2) compliance
 
* Full SVG (plus XML, CSS2) compliance
 
* Core written in C/C++
 
* Core written in C/C++
* Gtk-based user interface following the standards set out in the GNOME HIG
+
* Gtk-based user interface following the standards set out in the [http://library.gnome.org/devel/hig-book/stable/ GNOME Human Interface Guidelines (HIG)]
 
* Emphasis on a small core and extensibility.  Extensions should be first-class citizens, so we can say "no" to features in the core without guilt.
 
* Emphasis on a small core and extensibility.  Extensions should be first-class citizens, so we can say "no" to features in the core without guilt.
 
* Open, community-oriented development processes
 
* Open, community-oriented development processes

Revision as of 01:32, 18 December 2009

Invariants of Inkscape

These are the founding goals for Inkscape that we'll be adhering to in this project.

  • Full SVG (plus XML, CSS2) compliance
  • Core written in C/C++
  • Gtk-based user interface following the standards set out in the GNOME Human Interface Guidelines (HIG)
  • Emphasis on a small core and extensibility. Extensions should be first-class citizens, so we can say "no" to features in the core without guilt.
  • Open, community-oriented development processes
  • Baseline is the SodipodiHydra codebase
  • Where a better solution cannot be found, default to the way Illustrator does it.

OtherGoals - discussion of general project objectives and motivations