[Sugar-devel] Sugar-devel Digest, Vol 138, Issue 9

[Saumya Mishra]

Hello Cheong Siu Hong,
 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.

On Wed 8 Apr, 2020, 9:30 PM , <sugar-devel-request at lists.sugarlabs.org>
wrote:

> Send Sugar-devel mailing list submissions to
>         sugar-devel at lists.sugarlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.sugarlabs.org/listinfo/sugar-devel
> or, via email, send a message with subject or body 'help' to
>         sugar-devel-request at lists.sugarlabs.org
>
> You can reach the person managing the list at
>         sugar-devel-owner at lists.sugarlabs.org
>
> 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 <quozl at laptop.org>
> To: Cheong Siu Hong <cheongsiuhong at gmail.com>
> Cc: sugar-devel at lists.sugarlabs.org
> Subject: Re: [Sugar-devel] Updating sugar-web with changes from
>         Sugarizer
> Message-ID: <20200407232626.GE3490 at laptop.org>
> 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]https://github.com/sugarlabs/sugar-web/pull/133.
> >
> > 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] https://github.com/sugarlabs/sugar-web/pull/133
>
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> ------------------------------
>
> End of Sugar-devel Digest, Vol 138, Issue 9
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200409/a494e213/attachment.htm>