Hi!
Yes, I think that a GSOC project related to Proofread Page is a very good idea. The things to do would be:
1. Refactoring of the extension code by splitting the very big file ProofreadPage.body.php that do too much things into specific classes what will be more easily testable. Write unit tests for them.
2. Refactoring of the JavaScript module that manages edition of Page: and make it compatible with the VisualEditor. This includes:
- for wikitext editing system a full rewrite in order to make the code readable and testable. The tasks would be:
- move to server part of the extension things that can be done by it as it have been done for Index: pages.
- use libraries packaged with MediaWiki like JQuery when possible.
- find and use a good free JS library for zooming into scans in order to improve the current zoom feature that might be enhanced.
- work with the Visual Editor team in order to make the Visual Editor work with Page: pages. The first step is to make the body of the page editable, then the proofreading level and, if it's possible, header and footer.
3. Add modules to the Visual Editor to support specific tags used by Wikisource like <pages>, <section> and <poem>.
4. Allows to edit using the Visual Editor textareas of the Index: pages form.
...
What do you think about it?
Thomas
PS. I CC QGil and Sumanah who manage GSOC.
From: zanni.andrea84@gmail.com
Date: Mon, 25 Mar 2013 15:05:46 +0100
Subject: Re: [Wikisource-l] Missing project ideas for GSOC
To: wikisource-l@lists.wikimedia.org; dacuetu@gmail.com; thomaspt@hotmail.fr
Do you think that working on the Proofread extension
for making it compliant with the brand new Visual Editor
could be feasible?
I know that Tpt (in cc) was working on it,
maybe it would be a good (and useful) project.
Aubrey