<div dir="auto"><div>Hello Cheong Siu Hong,</div><div dir="auto"> Your Plan looks good to me. I agree with your plan as I have seen there are sugar-web activities not working as expected on Sugar. The issues there can be due to outdated sugar-web library. The porting guide also will be helpful for the new developers in future. As suggested by James Cameron , there must not be language barrier between developers we must be able to work on as much directions as possible. Thanks. <div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Wed 8 Apr, 2020, 9:30 PM , <<a href="mailto:sugar-devel-request@lists.sugarlabs.org">sugar-devel-request@lists.sugarlabs.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Sugar-devel mailing list submissions to <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank" rel="noreferrer">sugar-devel@lists.sugarlabs.org</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> or, via email, send a message with subject or body 'help' to <a href="mailto:sugar-devel-request@lists.sugarlabs.org" target="_blank" rel="noreferrer">sugar-devel-request@lists.sugarlabs.org</a> You can reach the person managing the list at <a href="mailto:sugar-devel-owner@lists.sugarlabs.org" target="_blank" rel="noreferrer">sugar-devel-owner@lists.sugarlabs.org</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of Sugar-devel digest..." Today's Topics: 1. Re: Updating sugar-web with changes from Sugarizer (James Cameron) ---------------------------------------------------------------------- Message: 1 Date: Wed, 8 Apr 2020 09:26:26 +1000 From: James Cameron <<a href="mailto:quozl@laptop.org" target="_blank" rel="noreferrer">quozl@laptop.org</a>> To: Cheong Siu Hong <<a href="mailto:cheongsiuhong@gmail.com" target="_blank" rel="noreferrer">cheongsiuhong@gmail.com</a>> Cc: <a href="mailto:sugar-devel@lists.sugarlabs.org" target="_blank" rel="noreferrer">sugar-devel@lists.sugarlabs.org</a> Subject: Re: [Sugar-devel] Updating sugar-web with changes from Sugarizer Message-ID: <<a href="mailto:20200407232626.GE3490@laptop.org" target="_blank" rel="noreferrer">20200407232626.GE3490@laptop.org</a>> Content-Type: text/plain; charset=iso-8859-1 I agree with the plan. My goal is to leverage work done on activities so that they are available on both Sugar and Sugarizer. Having a Sugar Web library that works on both is a better outcome than having two separate libraries, because it will reduce maintenance. What has tended to happen is that developers who want to work on JavaScript are attracted to Sugarizer, and developers who want to work on Python are attracted to Sugar. A division by language preference. Once an activity is accepted into Sugarizer, developers have been content with that dopamine hit and haven't worked to get the activity working in Sugar. Firstly because of the evolution of the Sugar Web library inside Sugarizer, secondly because of scope constraints for GCI tasks or GSoC projects, and thirdly because no other developers have been working on JavaScript activities in Sugar. This is an opportunity for developers skilled in JavaScript to write or port activities to Sugar. On Tue, Apr 07, 2020 at 12:42:08AM +0800, Cheong Siu Hong wrote: > Hello all, > > Currently, the sugar-web library is fairly outdated. I have been working on > backporting changes from Sugarizer's sugar-web, and more details can be seen in > the pull request at [1]<a href="https://github.com/sugarlabs/sugar-web/pull/133" rel="noreferrer noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/pull/133</a>. > > I would like to open this up to more discussion, but so far from the discussion > in the PR, the plan currently is as follows: > > 1. Update a set of files for sugar-web (i.e. for each component) > 2. Test if some Sugar Web activities work with the updated library, else make > porting fixes. > 3. Repeat steps 1 and 2 until sugar-web is up to date with Sugarizer. > 4. Select a version for next release (i.e. 0.118) > 5. Push changes to selected Sugar Web activities to make them work with the > updated library. > 6. Write a guide for porting old Sugar Web activities. > > This merely brings the sugar-web repository back up to speed with that of > Sugarizer's. Sugarizer activities may still not work natively on Sugar. > > I would also like to ask and discuss about the direction that this library is > going to take. Is the aim to have a sugar-web library that will work on both > native Sugar Desktop and Sugarizer? Currently, I have submitted a GSoC proposal > for working on this, and it would be great to hear the community's thoughts on > the matter. > > Best regards, > Cheong Siu Hong > > References: > > [1] <a href="https://github.com/sugarlabs/sugar-web/pull/133" rel="noreferrer noreferrer" target="_blank">https://github.com/sugarlabs/sugar-web/pull/133</a> > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank" rel="noreferrer">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer noreferrer" target="_blank">http://quozl.netrek.org/</a> ------------------------------ Subject: Digest Footer _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank" rel="noreferrer">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> ------------------------------ End of Sugar-devel Digest, Vol 138, Issue 9 ******************************************* </blockquote></div></div></div>