<div class="gmail_quote">---------- Forwarded message ---------- From: "Ashish Aggarwal" <<a href="mailto:ashish09101998@gmail.com">ashish09101998@gmail.com</a>> Date: Mar 26, 2019 2:10 PM Subject: Re: [Sugar-devel] Enquiry Regarding Contribution To Write Activity Project To: "James Cameron" <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> Cc: <<a href="mailto:sugar-devel@lists.sugarlabs.org">sugar-devel@lists.sugarlabs.org</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hello James, I went through the mentioned text editors Quill, TinyMCE, CKEditor, webODF as well as SunEditor and Froala.</div><div>Here is result of the search done by me :</div><div> </div><div>Quill : Quill is a free, open source WYSIWYG editor built for the modern web. It supports all major modern browsers . It has support on stack and github. The major issue I found in it was lack of support for tables. TinyMCE : It is also open source Licensed under LGPL . It has all major features required for editing the content . It has great documentation and an active community. It is not completely free and is API key based. CKEditor : It is also open source and an easy to use rich text editor . It also has large active community. It has some minor cross browser platform issues. WebODF : It is also open source . It has a major drawback the community is not active anymore. Reference - <a href="https://github.com/webodf/WebODF/issues/947" style="text-decoration-line:none" target="_blank">here</a>. SunEditor : It is also an open source editor. It has all major features required for the project. The major issue is it has a very thin community.I have also contributed to this Editor <a href="https://github.com/JiHong88/SunEditor/pull/84" style="text-decoration-line:none" target="_blank">here</a>. Froala : It is also an open source editor with active and large community . It also has all major features required for the project .It has good documentation and has a very good performance .It is available for all major frameworks. Although it is open source, but the professional support is paid. Conclusion : I feel the best way moving forward is to create our own purely javascript based rich text editor without pure reliability on any other text editor. Our editor would take inspiration from these editors in terms of frameworks used and coding style. The major advantage of doing it will be having a high scale of customisation as per the needs of the project. It would be easier to maintain and do changes to it as per our requirements. I have tried to implement a basic rich text editor with some major features <a href="https://ashish0910.github.io/Texteditor/index.html" style="text-decoration-line:none" target="_blank">here</a> purely based on HTML/CSS and JS .Ref - <a href="https://stackoverflow.com/a/6008195" style="text-decoration-line:none" target="_blank">https://stackoverflow.com/a/6008195</a> Export content to printable format : Most major rich text editors uses some API or js libraries to convert the data present in PDF format . For example CKEditor and TinyMCE uses <a href="https://www.api2pdf.com/documentation" style="text-decoration-line:none" target="_blank"><span style="font-size:10.5pt;font-family:Arial;color:rgb(10,144,235);font-weight:700;font-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underline;vertical-align:baseline;white-space:pre-wrap">Api2Pdf REST API</a> ( We can also use the same in our custom editor ) Also npm packages such as <a href="https://www.npmjs.com/package/html-pdf" style="text-decoration-line:none" target="_blank">html-pdf</a> can also solve the problem There is one more way do implement it using <a href="https://github.com/MrRio/jsPDF" style="text-decoration-line:none" target="_blank">this</a> Export content to editable format : Majority of previously existing text editors supports only convert to html format . However we can have export to txt , Open XML word documents , HTML. For txt and HTML : Best way to do this is through <a href="https://github.com/eligrey/FileSaver.js/" style="text-decoration-line:none" target="_blank">FileSaver.js</a> and <a href="https://www.javascripture.com/Blob" style="text-decoration-line:none" target="_blank">Blob</a>A more advanced way would be <a href="https://github.com/jimmywarting/StreamSaver.js" style="text-decoration-line:none" target="_blank">StreamSaver.js</a> in case of extremely large files ( greater than 2gb ) . For doc : We can use jquery word export plugin <a href="https://codepen.io/airpwn/pen/LRZdJo" style="text-decoration-line:none" target="_blank">example</a> . Also we can use <a href="https://github.com/kannan-ar/MariGold.OpenXHTML" style="text-decoration-line:none" target="_blank">MariGold.OpenXHTML</a> For RTF : We can use <a href="http://jsfiddle.net/JamesMGreene/2b6Lc/?utm_source=website&utm_medium=embed&utm_campaign=2b6Lc" style="text-decoration-line:none" target="_blank">this</a> type of approach and Blob to get RTF files Regards , <a href="http://ashishaggarwal.tech/" target="_blank">Ashish aggarwal</a>github - <a href="https://github.com/ashish0910" target="_blank">ashish0910</a> </div><div> </div><div> </div><div> </div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 26 Mar 2019 at 03:57, James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Welcome. Third step was to make a study of existing web editors, identifying features of each and ways to export content to editable or printable format. What were your results? On Mon, Mar 25, 2019 at 09:25:18PM +0530, Ashish Aggarwal wrote: > Hello everyone , > I came across the project Write Activity for Sugarizer [1]here . I really liked > the project and would like to contribute to it for gsoc but as the existing > project is based on python and the proposed project is required to be made on > javascript, as mentioned in the ideas page, I was not sure regarding the right > way towards contributing to this project. > I have already gone through the provided tutorials as well as the steps > mentioned and have been contributing towards Sugar Labs for a while now. > Please provide me the right approach going forward. > Thanks & Regards > [2]Ashish Aggarwal > Github Link - [3]ashish0910 > > References: > > [1] <a href="https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#write-activity-for-sugarizer" rel="noreferrer" target="_blank">https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#write-activity-for-sugarizer</a> > [2] <a href="http://ashishaggarwal.tech/" rel="noreferrer" target="_blank">http://ashishaggarwal.tech/</a> > [3] <a href="https://github.com/ashish0910" rel="noreferrer" target="_blank">https://github.com/ashish0910</a> > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div></div> </blockquote></div>