Difference between revisions of "ProjectOrientedCchostIntegrationSpec"
Jump to navigation
Jump to search
Prokoudine (talk | contribs) (+ tiny update) |
Prokoudine (talk | contribs) m (yet another tiny update) |
||
| Line 8: | Line 8: | ||
==Workflow description== | ==Workflow description== | ||
==Implied changes== | |||
===Internal=== | |||
===GUI=== | |||
==Usability considerations== | |||
==Stages of implementation== | ==Stages of implementation== | ||
===First stage=== | ===First stage=== | ||
Latest revision as of 13:14, 27 February 2008
Project oriented integration with ccHost
Synopsis
When you work on a project like "new corporate style", usually you use a uniform base color palette, a uniform set of patterns and templates.
Since Inkscape already can talk to ccHost, it should be possible to set up a ccHost powered web storage for documents like swatches, patterns, templates, fonts etc. and use it from Inkscape along the usual Open Clip Art Library and/or Open Font Library.
ccHost installations as such are out of scope of this specification.
Workflow description
Implied changes
Internal
GUI
Usability considerations
Stages of implementation
First stage
Inkscape should be able to use several ccHost based servers simultaneously.
Second stage
Inkscape should be able to open/save swatches and patterns from/to ccHost servers.
Third stage
Inkscape should be able to open/save templates from/to ccHost servers via 'New from Template' dialog