Re: [Sugar-devel] Enquiry Regarding Contribution To Write Activity Project

[James Cameron]

My guess is what we call "Tables" in English.

I'm not the right person to answer.  "git blame" shows the wording
came from Lionel.

https://github.com/sugarlabs/GSoC/blame/master/Ideas-2019.md#L474

Lionel speaks French.  These two Google Translations suggest that
"Array" is a valid translation;

"table in document" -> "tableau dans de document"

"array in document" -> "tableau dans de document"

On Thu, Mar 28, 2019 at 10:20:32AM +0530, Ashish Aggarwal wrote:
> Hello James ,
> I have a query . The idea [1]page refers to having arrays in the text editor .
> Is the arrays here stand for arrays in programming language or something else 
> ?
> I have attached screenshot with this mail .
> 
> On Wed, 27 Mar 2019 at 10:01, James Cameron <[2]qu...@laptop.org> wrote:
> 
> Thanks Ashish.
> 
> A next step is for coding mentors Michaël Ohayon and Lionel Laské to
> review and comment.
> 
> You can also work on your proposal.
> 
> [3]https://github.com/sugarlabs/GSoC/blob/master/Template.md
> 
> On Tue, Mar 26, 2019 at 02:10:34PM +0530, Ashish Aggarwal wrote:
> > Hello James,
> > I went through the mentioned text editors Quill, TinyMCE, CKEditor,
> webODF as
> > well as SunEditor and Froala.
> > Here is result of the search done by me :
> >
> > 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 - [1]here.
> >
> > 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 [2]here.
> >
> > 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 [3]
> > here purely based on HTML/CSS and JS .
> >
> > Ref - [4][4]https://stackoverflow.com/a/6008195
> >
> > 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  [5]Api2Pdf REST API ( We can also
> use
> > the same in our custom editor )
> >
> > Also npm packages such as  [6]html-pdf can also solve the problem
> >
> > There is one more way do implement it using [7]this
> >
> > 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 [8]FileSaver.js and 
> [9]
> Blob
> >
> > A more advanced way would be [10]StreamSaver.js in case of extremely
> large
> > files ( greater than 2gb ) .
> >
> > For doc : We can use jquery word export plugin [11]example .
> >
> > Also we can use [12]MariGold.OpenXHTML
> >
> > For RTF : We can use [13]this type of approach and Blob to get RTF files
> >
> > Regards , 
> >
> > [14]Ashish aggarwal
> >
> > github - [15]ashish0910
> >
> >  
> >
> > On Tue, 26 Mar 2019 at 03:57, James Cameron <[16][5]qu...@laptop.org>
> wrote:
> >
> >     Welcome.
> >
> >     Third step was to make a study of existing web editors, identifying
> >     

Re: [Sugar-devel] Enquiry Regarding Contribution To Write Activity Project

[Ashish Aggarwal]

Hello James ,
I have a query . The idea page

refers
to having arrays in the text editor . Is the arrays here stand for arrays
in programming language or something else ?
I have attached screenshot with this mail .

On Wed, 27 Mar 2019 at 10:01, James Cameron  wrote:

> Thanks Ashish.
>
> A next step is for coding mentors Michaël Ohayon and Lionel Laské to
> review and comment.
>
> You can also work on your proposal.
>
> https://github.com/sugarlabs/GSoC/blob/master/Template.md
>
> On Tue, Mar 26, 2019 at 02:10:34PM +0530, Ashish Aggarwal wrote:
> > Hello James,
> > I went through the mentioned text editors Quill, TinyMCE, CKEditor,
> webODF as
> > well as SunEditor and Froala.
> > Here is result of the search done by me :
> >
> > 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 - [1]here.
> >
> > 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 [2]here.
> >
> > 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 [3]
> > here purely based on HTML/CSS and JS .
> >
> > Ref - [4]https://stackoverflow.com/a/6008195
> >
> > 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  [5]Api2Pdf REST API ( We can also
> use
> > the same in our custom editor )
> >
> > Also npm packages such as  [6]html-pdf can also solve the problem
> >
> > There is one more way do implement it using [7]this
> >
> > 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 [8]FileSaver.js and
> [9]Blob
> >
> > A more advanced way would be [10]StreamSaver.js in case of extremely
> large
> > files ( greater than 2gb ) .
> >
> > For doc : We can use jquery word export plugin [11]example .
> >
> > Also we can use [12]MariGold.OpenXHTML
> >
> > For RTF : We can use [13]this type of approach and Blob to get RTF files
> >
> > Regards ,
> >
> > [14]Ashish aggarwal
> >
> > github - [15]ashish0910
> >
> >
> >
> > On Tue, 26 Mar 2019 at 03:57, James Cameron <[16]qu...@laptop.org>
> wrote:
> >
> > 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 

Re: [Sugar-devel] Enquiry Regarding Contribution To Write Activity Project

[James Cameron]

Thanks Ashish.

A next step is for coding mentors Michaël Ohayon and Lionel Laské to
review and comment.

You can also work on your proposal.

https://github.com/sugarlabs/GSoC/blob/master/Template.md

On Tue, Mar 26, 2019 at 02:10:34PM +0530, Ashish Aggarwal wrote:
> Hello James,
> I went through the mentioned text editors Quill, TinyMCE, CKEditor, webODF as
> well as SunEditor and Froala.
> Here is result of the search done by me :
> 
> 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 - [1]here.
> 
> 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 [2]here.
> 
> 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 
> [3]
> here purely based on HTML/CSS and JS .
> 
> Ref - [4]https://stackoverflow.com/a/6008195
> 
> 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  [5]Api2Pdf REST API ( We can also use
> the same in our custom editor )
> 
> Also npm packages such as  [6]html-pdf can also solve the problem
> 
> There is one more way do implement it using [7]this
> 
> 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 [8]FileSaver.js and [9]Blob
> 
> A more advanced way would be [10]StreamSaver.js in case of extremely large
> files ( greater than 2gb ) .
> 
> For doc : We can use jquery word export plugin [11]example .
> 
> Also we can use [12]MariGold.OpenXHTML
> 
> For RTF : We can use [13]this type of approach and Blob to get RTF files
> 
> Regards , 
> 
> [14]Ashish aggarwal
> 
> github - [15]ashish0910
> 
>  
> 
> On Tue, 26 Mar 2019 at 03:57, James Cameron <[16]qu...@laptop.org> wrote:
> 
> 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] [17]https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#
> write-activity-for-sugarizer
> > [2] [18]http://ashishaggarwal.tech/
> > [3] [19]https://github.com/ashish0910
> 
> > ___
> > Sugar-devel mailing list
> > [20]Sugar-devel@lists.sugarlabs.org
> > [21]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> 

Re: [Sugar-devel] Enquiry Regarding Contribution To Write Activity Project

[Ashish Aggarwal]

Hello James,
I went through the mentioned text editors Quill, TinyMCE, CKEditor, webODF
as well as SunEditor and Froala.
Here is result of the search done by me :

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 - here .

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 here
.

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
here  purely based on
HTML/CSS and JS .

Ref - https://stackoverflow.com/a/6008195


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  Api2Pdf REST API
 ( We can also use the same in our
custom editor )

Also npm packages such as  html-pdf 
can also solve the problem

There is one more way do implement it using this


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 FileSaver.js
 and Blob


A more advanced way would be StreamSaver.js
 in case of extremely large
files ( greater than 2gb ) .

For doc : We can use jquery word export plugin example
 .

Also we can use MariGold.OpenXHTML



For RTF : We can use this

type of approach and Blob to get RTF files

Regards ,

Ashish aggarwal 

github - ashish0910 














On Tue, 26 Mar 2019 at 03:57, James Cameron  wrote:

> 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]
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#write-activity-for-sugarizer
> > [2] http://ashishaggarwal.tech/
> > [3] https://github.com/ashish0910
>
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
> 

Re: [Sugar-devel] Enquiry Regarding Contribution To Write Activity Project

[James Cameron]

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] 
> https://github.com/sugarlabs/GSoC/blob/master/Ideas-2019.md#write-activity-for-sugarizer
> [2] http://ashishaggarwal.tech/
> [3] https://github.com/ashish0910

> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel