GSoC 2011 Scripter2 Proposal: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
Line 22: Line 22:
== Implementation Plan ==
== Implementation Plan ==


Implementation of this project will be based on the well-known software engineering principle, [http://en.wikipedia.org/wiki/Test-driven_development Test-driven Development]. All those scripts that are packaged with Scribus is tested with the new ScripterNG, and development proceeds by solving all those issues which encounter while testing them. All scripts those bundled with Scribus were developed based on Scripter1. This development process will also help to make the Scribus API better, since there exist more chances for some code refactoring.  
Implementation of this project will be based on a well-known software engineering principle [http://en.wikipedia.org/wiki/Test-driven_development Test-driven Development]. All scripts packaged with Scribus will be tested with scripter2, and development will proceed by solving all issues encountered in the testing. All scripts bundled with Scribus were developed based on scripter1, so they can be used for testing scripter2. This development process will also help to make the Scribus API better, since opportunities for code refactoring may be discovered in the process.  


=== Deliverables ===
=== Deliverables ===


* Support for complete Scripter1 API in ScripterNG.
* Support for complete Scripter1 API in Scripter2.
** Reference : [http://wiki.scribus.net/canvas/ScripterNG/Development/PortingOldScripter Porting Old Scripter] by Henning
** Reference : [http://wiki.scribus.net/canvas/ScripterNG/Development/PortingOldScripter Porting Old Scripter] by Henning


Revision as of 17:05, 8 April 2011

Enhancing ScripterNG in Scribus

Abstract

Scribus shows that professional desktop publishing is possible with Free Software. Scribus has many powerful features which are often mentioned in articles. For instance, high quality PDF export and color management are considered to be the strong points of Scribus. However, the scripting features of Scribus are not getting attention even after the complete redesign of its architecture even though analysis of the user mailing list postings shows that the scripted use of Scribus's features is on a constant rise and is a critical functionality for many professional users.

Scribus has a well designed API for its new ScripterNG also known as scripter2, developed as part of GSoC 2008. This scripting engine can also be adapted to multiple scripting languages. However, the scripter2 still does not expose many of the Scribus API calls present in the old scripter1. One of the main goals of this project is to port the complete API of the old scripter to the scripter2 for retaining the backwards compatibility and providing complete API coverage needed for the deprecation of scripter1 and the switch to scripter2.

Problem Description

The new scripter2 has not been added to Scribus as a default scripting engine even though it was developed back in 2008 because its Scribus API coverage is still below that of scripter1. For instance, Styles API is missing in scripter2. Hence, users are unable to handle Scribus styles in their scripts. In addition, createParagraphStyle and createCharacterStyle were present in scripter1, but missing in scripter2.

Here is a long list of changes which are yet to be implemented in ScripterNG :

This project will complete the porting of scripter1 scripting engine to scripter2, so that much improved scripter2 may be used as the default scripting engine in Scribus.

Implementation Plan

Implementation of this project will be based on a well-known software engineering principle Test-driven Development. All scripts packaged with Scribus will be tested with scripter2, and development will proceed by solving all issues encountered in the testing. All scripts bundled with Scribus were developed based on scripter1, so they can be used for testing scripter2. This development process will also help to make the Scribus API better, since opportunities for code refactoring may be discovered in the process.

Deliverables

Timeline

First week

  • Setting up the infrastructure like blog/wiki, code repository etc.
  • Getting additional feedback from developers and from the community about the project.

Week 2-3

  • Testing out scripts available and analysis of needed changes to be implemented
  • Documentation of changes

Until 11th of July

  • Porting features from old Scripter, listed in the reference link.
  • Implement most needed API features before midterm evaluation.
    • Discussions with development team regarding those features to be implemented before midterm evaluations

Until 15th of July

Writing mid-term evaluation

Until 10th of August

  • Further improving the ScripterNG API by adding all the features left, after the midterm evaluations
  • Writing sample scripts, for unit tests.
    • Each and every function ported to new Scripter will be tested.

Until 15th of August

  • Fixing bugs
  • Reviewing and improving usability
  • Writing documentations
    • User documentation for each function, quoting the sample scripts
    • Developer Documentation.

Until 26th of august ('pencils down')

Preparations for Final Evaluation

Student Biography

I am Jain Basil Aliyas, a computer science & engineering student from India. I am one among the members of Scribus team, KDE and Pardus Projects.

Contact Information

Name : Jain Basil Aliyas

Country : India

Time Zone : GMT +530

IRC Nickname : jainbasil in #scribus, #scribus-dev

Useful Links.

 - http://wiki.scribus.net/canvas/ScripterNG/Development/PortingOldScripter
 - http://wiki.scribus.net/canvas/ScripterNG/Development
Retrieved from "https://wiki.scribus.net/wiki/index.php?title=GSoC_2011_Scripter2_Proposal&oldid=25337"