Add section about the new document editor.
diff --git a/GSoC2010Ideas.wiki b/GSoC2010Ideas.wiki index cbdb619..1c5e699 100644 --- a/GSoC2010Ideas.wiki +++ b/GSoC2010Ideas.wiki
@@ -29,6 +29,8 @@ ---- ---- += New Document Editor = + = Improving Documenting system/Adding a Wiki = ===Description=== @@ -58,6 +60,47 @@ ---- += New Document Editor = + +=== Description === +We're looking for a better way to handle documents, document revisions and document editing in Melange. To do that we need to switch the text editor from TinyMCE to something better usable and safer when it comes to HTML. Documents are used throughout Melange to show and edit, for example, the very Home Page, organizations home pages and, most important, project proposals. + +==== Characteristics we're looking for ===== + * Safe handling of HTML tags, or switch completely to Markdown syntax + * Be able to add custom tags + * Code highlighting (should be able to recognize automatically the language to highlight) + * Support for anchors + * Show images linked from the Net and/or uploaded to the system using BLOB API. + * Be able to accept attachments (perhaps with checking over MIME part to accept only certain types of files) + * Be able to add links + * Control over appareance (left, right, center, bold, italic, color, etc) + * Autosaving during editing + * Be able to show diffs between editing (but it should be possible to turn it off for certain pages) + * Document access control + +We did an internal study about the switching and we're thinking the safer way to go is not to use HTML for editing at all (but we welcome new exciting proposals!), so probably a solution could be to use an already made Markdown editor. To do that we need a markdown parser and a markdown WYSIWYG (or at least a WYSIWYM) editor. On the backend side, we need to store different revisions of each document. The simplest way to do that is to store a new document each time it's edited and to show the differences on the frontend side using libraries like Google-Diff-Match-Patch. The hardest way is to have a proper revision control system completely written in Python. One challenge of this part of the project may be the showing of proper differences of the very Markdown tags. + +==== Useful Links ==== + + * [http://markitup.jaysalvat.com/home/ markItUp!] + * [http://attacklab.net/showdown/ Showdown] + * [http://code.google.com/p/google-diff-match-patch/ Google-diff-match-patch] + * [http://alexgorbatchev.com/wiki/SyntaxHighlighter SyntaxHighlighter] + * [http://softwaremaniacs.org/soft/highlight/en/ Highlight.js] + +=== Skills === + * JavaScript + * HTML + * CSS + * Python + +Difficulty: +Moderate + +Mentors: + * Mario Ferraro + +---- =Testing, Code Guru, Code Quality Assurance= ===Description===