GSoC 2007 Publishing Solution Task Plan: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 16: | Line 16: | ||
# Connects to a file store | # Connects to a file store | ||
# | # 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.
- SSE engine - should be a decent text editor in itself.
- Editor GUI - should support as many Scribus text attributes as possible with a clean interface to apply them.
- Output - Scribus native new file format (see /dtd directory for the draft).
- 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
- Connects to a file store
- Retrieves named text containers and feeds them to the SSE
- Pushes edited containers back into the file store/server