GSoC 2007 Publishing Solution Task Plan: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
No edit summary
 
Line 16: Line 16:


# Connects to a file store
# Connects to a file store
# Retrie
# Retrieves named text containers and feeds them to the SSE
# Pushes edited containers back into the file store/server

Latest revision as of 22:56, 16 March 2007

Task #1 - Standalone Story Editor (SSE)

This is the main qt4 gui.

  1. SSE engine - should be a decent text editor in itself.
  2. Editor GUI - should support as many Scribus text attributes as possible with a clean interface to apply them.
  3. Output - Scribus native new file format (see /dtd directory for the draft).
  4. Connector - interaction with the file server/store/engine.

Task #2 - Web-based Story Editor (WSE)

Web-based php|python/ajax. Same output functionality as SSE.


Task #3 - Scribus Object Exchange Engine

  1. Connects to a file store
  2. Retrieves named text containers and feeds them to the SSE
  3. Pushes edited containers back into the file store/server