GSoC 2010 Ideas: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
Line 27: Line 27:
* Create a "Document Wizard" plugin for standardised business cards, labels etc., like Avery or Pelikan by using OpenOffice.org's template "database" (actually an XML file)
* Create a "Document Wizard" plugin for standardised business cards, labels etc., like Avery or Pelikan by using OpenOffice.org's template "database" (actually an XML file)
* Rewrite the table code and create a table editor (see: [http://bugs.scribus.net/view.php?id=2564 RFE 2564])
* Rewrite the table code and create a table editor (see: [http://bugs.scribus.net/view.php?id=2564 RFE 2564])
* add an indicator for the modifiers (and eventually other specific shortcuts) currently available (like inkscape does in the status bar; i'd probably prefere a palette which could be disabled)
* Add an indicator for the modifiers (and eventually other specific shortcuts) currently available (like Inkscape does in the status bar; i'd probably prefere a palette which could be disabled)

Revision as of 13:52, 4 February 2010


Possible GSoC 2010 projects

Import/Export Filters

  • XPS export
  • XPS import
  • Rewrite/update the ODG/SXD importer
  • PageStream import filter (file format spec is available here)
  • Serif PagePlus PPP import filter (the new XML-based version). No spec available; requires analysis of existing PPP files.
  • Quark QXML import filter. No spec available; requires analysis of existing QXML files.
  • Colour-managed bitmap export

Text

  • CJK support (requires very close collaboration with Scribus developer Andreas Vox who's in charge of the text layout system)
  • Support for RTL scripts (Arabic, Hebrew; requires very close collaboration with Scribus developer Andreas Vox who's in charge of the text layout system)
  • Rewrite the Text Filter (add character styles, fix the dialog etc.)
  • Rich Text export from the Story Editor (ODT, RTF, Xtags, ICML, IDML, INX).
  • Enable import of all text formats available for text frames, including styles, into the Story Editor.

General

  • Rewrite the template system
  • Speed optimisation (requires experience with code optimisation in general, as well as advanced C++ and Qt knowledge)
  • Prepare Scribus for real resource management with Viaduct.
    • Objectives: a) Prepare the Scribus internals for Viaduct, b) add DTP requirements to Viaduct, c) prepare a pure C++ library of Viaduct.
    • Requirements: Close cooperation with the main author of Viaduct, Inkscape's Jon Cruz.
    • Advantages: A lot of freedom when it comes to implementation, because Viaduct is still in its infancy.
  • Create a "Document Wizard" plugin for standardised business cards, labels etc., like Avery or Pelikan by using OpenOffice.org's template "database" (actually an XML file)
  • Rewrite the table code and create a table editor (see: RFE 2564)
  • Add an indicator for the modifiers (and eventually other specific shortcuts) currently available (like Inkscape does in the status bar; i'd probably prefere a palette which could be disabled)