Re: [Sugar-devel] Port to python3

[James Cameron]

Ultimate test is to run the activity on a system that does not have
Python 2.  If it doesn't run, or doesn't run properly, then work is
needed, and some of that work may relate to porting to Python 3.

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

Re: [Sugar-devel] Port to python3

[Saumya Mishra]

Hi Shivam,

Please go through this guide
https://github.com/sugarlabs/sugar-docs/blob/master/src/python-porting-guide.md
for any doubts related to Port of activity to Python 3. You can check the
pull request in GitHub repositories to check whether some work is remained
or not related to the port. Also, you can check old commits to see if the
activity is ported earlier to Python 3.



Regards
Saumya Mishra

On Sat, Apr 10, 2021 at 5:58 PM Shivam Rai 
wrote:

> Pls guide,
> How can i check that whether the port of an activity is successfully
> complete or which activities still require some work.
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Port to python3

[Shivam Rai]

Pls guide,
How can i check that whether the port of an activity is successfully
complete or which activities still require some work.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port Sugar and core activities to Python3 - Project Update

[James Cameron]

Thanks!

On Sat, Jun 13, 2020 at 03:34:07PM +0530, Saumya Mishra wrote:
> 
> Hello,
> 
> My progress on the GSoc Project so far-
> 
> Test and review old commits of sugar and sugar-datastore (port to python3
> commits only) , find most of the issues in sugar which was related to encoding
> and decoding of byte data, I opened pull requests as well as worked on some
> issues - [1]#922  | [2]#21 | [3]#923
> 
> Test Collaboration of fructose activities , I tested write, chat and pippy
> in detail. Found some issues , I have opened pull requests and issues for 
> that.
> Some of the major issues I found seem related to earlier python3 ports commits
> which have done without proper testing. The links of my work so far regarding
> this -[4] #921[5] | #40 | [6]#924
> 
> Debug and test issue found by find-words-activity [7]#411 and pippy in
> collab wrapper [8]#24
> 
> Turtle-Art : Test and find that port to gtk3 was incomplete, work on 
> fixing
> along with some minor updates in sprites.py [9]#82 | [10]#81
> 
> locosugar : Fix screen resolution and make it compatible with all screen
> sizes , fix warning erroneous pipeline which was mainly caused by old audio
> player modules , [11]@Jui Pradhan is also working with me in some issues found
> there. She will also look into release once my changes get merged. [12]#14
> 
> activity-turtle-flags : Rebase and merge with TurtleArt , Port to Python3 
> ,
> GTK3 and from GConf to GioSettings. The changes here is done , required
> reviews. [13]#8
> 
> PolariActivity : Work on Port to Python3 , some minor fixes and deletion 
> of
> zope, constantly , twisted and incremental source files as 
> distro packages will be supported here i.e. python3-twisted . Found a major
> issue which is UnicodeDecodeError while testing , which only needs to be
> solved.[14] #7
> 
> stick-hero-activity : Work on port of python3 , update to latest
> sugargame and major testing . Jui is working on the last python2 release , I
> will work on port after that [15]#1.
> 
> infoslicer : work on port to python3 and from sgmllib to html.parser is
> done. infoslicer uses two copies of beautifulsoup , which needs to be merged 
> in
> one somehow. Suggestions are to use the distro package of BeautifulSoup as it
> is a good practice nowadays. It is still in progress. [16]#34
> 
> Link of other found issues while testing [17]#5  |[18] #35
> 
> I will be working on the issues I mentioned above and if Jui wants she can 
> work
> on release of activities mentioned above. Along with that as Jui mentioned we
> are going to release the last python2 version of PyCut. I will work on port to
> Python3 on PyCut.
> I would also continue testing of activities regularly as we probably need more
> testing. 
> 
> Any suggestions are welcome.
> 
> Thanks and Regards
> Saumya Mishra
> 
> *
> 
> References:
> 
> [1] https://github.com/sugarlabs/sugar/pull/922
> [2] https://github.com/sugarlabs/sugar-datastore/pull/21
> [3] https://github.com/sugarlabs/sugar/issues/923
> [4] https://github.com/sugarlabs/sugar/pull/921
> [5] https://github.com/sugarlabs/write-activity/issues/40
> [6] https://github.com/sugarlabs/sugar/issues/924
> [7] https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/441
> [8] https://github.com/sugarlabs/collabwrapper/pull/24
> [9] https://github.com/sugarlabs/turtleart-activity/pull/82
> [10] https://github.com/sugarlabs/turtleart-activity/pull/81
> [11] mailto:juipradha...@gmail.com
> [12] https://github.com/sugarlabs/locosugar/pull/14
> [13] https://github.com/sugarlabs/activity-turtle-flags/pull/8
> [14] https://github.com/sugarlabs/PolariActivity/pull/7
> [15] https://github.com/JuiP/stick-hero-activity/pull/1
> [16] https://github.com/sugarlabs/infoslicer/pull/34
> [17] https://github.com/sugarlabs/mastermind-activity/issues/5
> [18] https://github.com/sugarlabs/infoslicer/issues/35

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

[Sugar-devel] Port Sugar and core activities to Python3 - Project Update

[Saumya Mishra]

Hello,

My progress on the GSoc Project so far-

Test and review old commits of *sugar* and *sugar-datastore* (port to
python3 commits only) , find most of the issues in sugar which was related
to encoding and decoding of byte data, I opened pull requests as well as
worked on some issues - #922   |
#21  | #923


Test Collaboration of *fructose* activities , I tested *write*, *chat*
and *pippy* in detail. Found some issues , I have opened pull requests and
issues for that. Some of the major issues I found seem related to earlier
python3 ports commits which have done without proper testing. The links of
my work so far regarding this - #921
 | #40
 | #924


Debug and test issue found by *find-words-activity* #411
 and* pippy* in
collab wrapper #24 

*Turtle-Art* : Test and find that port to gtk3 was incomplete, work on
fixing along with some minor updates in sprites.py #82
 | #81


*locosugar *: Fix screen resolution and make it compatible with all
screen sizes , fix warning erroneous pipeline which was mainly caused by
old audio player modules , @Jui Pradhan  is also
working with me in some issues found there. She will also look into release
once my changes get merged. #14


*activity-turtle-flags : *Rebase and merge with TurtleArt , Port to
Python3 , GTK3 and from GConf to GioSettings. The changes here is done ,
required reviews. #8


*PolariActivity : *Work on Port to Python3 , some minor fixes and
deletion of zope, constantly , twisted and incremental source files as
distro packages will be supported here i.e. *python3-twisted* . Found a
major issue which is UnicodeDecodeError while testing , which only needs to
be solved. #7 

*stick-hero-activity : *Work on port of python3 , update to latest
sugargame and major testing . Jui is working on the last python2 release ,
I will work on port after that #1
.

*infoslicer :* work on port to python3 and from sgmllib to html.parser
is done. infoslicer uses two copies of beautifulsoup , which needs to be
merged in one somehow. Suggestions are to use the distro package of*
BeautifulSoup *as it is a good practice nowadays. It is still in progress.
#34 

Link of other found issues while testing #5
 | #35


I will be working on the issues I mentioned above and if Jui wants she can
work on release of activities mentioned above. Along with that as Jui
mentioned we are going to release the last python2 version of PyCut. I will
work on port to Python3 on PyCut.
I would also continue testing of activities regularly as we probably need
more testing.

Any suggestions are welcome.

Thanks and Regards
Saumya Mishra
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to Gtk3: Gdk.Image error

[James Cameron]

Thanks for working on this.

I'm looking forward especially to your porting of the C++ code in this
activity, as that will be critical to success of the porting.

For reference, the issue you are working is
https://github.com/sugarlabs/Bounce/issues/7

My further reply in context below.

On Sun, Feb 09, 2020 at 03:27:10AM +0530, Abhishek Tanwar wrote:
> I am porting BOUNCE ACTIVITY (https://github.com/sugarlabs/Bounce)
> to Gtk +3 and I have ported it to some extent but I am stuck at a
> point where I am not able to find a solution.

https://github.com/sugarlabs/Bounce/pull/13 is a pull request work in
progress that contains a similar change from gtk.gdk.Image to
Gtk.Image, but pygi-convert.sh from the GNOME project (which I've
reviewed just now) does not make such a change as you and @tonadev
have made.

So my first question is why this change was made.  It looks like a
guess.  It looks wrong.

An instance of gtk.gdk.Image is an area for bit-mapped graphics stored
on the X Windows client.  It is not a widget.

https://developer.gnome.org/pygtk/stable/class-gdkimage.html

An instance of Gtk.Image is a widget for showing an image.  It is not
an image storage class.

https://lazka.github.io/pgi-docs/Gtk-3.0/classes/Image.html

So it doesn't seem likely that this change from gtk.gdk.Image to
Gtk.Image is correct.  These are two very different levels of the
software stack.

> Here is the link to my repository for BOUNCE activity :
> https://github.com/abhishektanwar/Bounce

Thanks.  I was unable to understand the pattern of changes you've
made; the commit messages were vague and short.  I don't know which
changes happened because of pygi-convert.sh, sugar-convert.sh, or your
own edits.  I don't know why you made those edits.

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#making-commits
has our advice on writing commit messages.

You have also committed the conversion scripts.  Please don't do that,
we don't need the scripts in the activity.

> I know that Gdk.Image is no more supported in Gdk3 and I have to use
> Cairo or Pixbuf but can't figure out how to convert it to Cairo.
> 
> Traceback (most recent call last):
>   File "/usr/share/sugar/activities/Bounce.activity/bounce.py", line 1634, in 
> on_drawarea_expose
>     self.on_drawarea_resize()
>   File "/usr/share/sugar/activities/Bounce.activity/bounce.py", line 1623, in 
> on_drawarea_resize
>     self.drawimage = Gdk.Image(Gdk.IMAGE_FASTEST, Gdk.visual_get_system(), 
> rect.width, rect.height)
>   File "/usr/lib/python2.7/dist-packages/gi/overrides/_init.py", line 39, in 
> __getattr_
>     return getattr(self._introspection_module, name)
>   File "/usr/lib/python2.7/dist-packages/gi/module.py", line 139, in _getattr_
>     self._name_, name))
> AttributeError: 'gi.repository.Gdk' object has no attribute 'Image'

The traceback is not useful.

You must use Cairo for drawing, without using a separate image buffer.

Migrating from GTK+ 2.x to GTK+ 3 explains this;
https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html#id-1.6.3.3.8

Instead of an expose signal and callback, you must connect a draw
signal and write a new callback.

The callback is given a Cairo context.  All drawing operations are
then performed on that context.

If you're not sure how to do this, look for another activity that was
ported from GTK 2 to GTK 3, and examine the changes made.  There are
many to choose from.  You must know how visualise git commit history
and how to read diffs.

Hope that helps!

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

[Sugar-devel] Port to Gtk3: Gdk.Image error

[Abhishek Tanwar]

I am porting BOUNCE ACTIVITY (https://github.com/sugarlabs/Bounce) to
Gtk +3 and I have ported it to some extent but I am stuck at a point where
I am not able to find a solution.

Here is the link to my repository for BOUNCE activity :
https://github.com/abhishektanwar/Bounce

I know that Gdk.Image is no more supported in Gdk3 and I have to use Cairo
or Pixbuf but can't figure out how to convert it to Cairo.

Traceback (most recent call last):
  File "/usr/share/sugar/activities/Bounce.activity/bounce.py", line 1634,
in on_drawarea_expose
self.on_drawarea_resize()
  File "/usr/share/sugar/activities/Bounce.activity/bounce.py", line 1623,
in on_drawarea_resize
self.drawimage = Gdk.Image(Gdk.IMAGE_FASTEST, Gdk.visual_get_system(),
rect.width, rect.height)
  File "/usr/lib/python2.7/dist-packages/gi/overrides/_init.py", line 39,
in __getattr_
return getattr(self._introspection_module, name)
  File "/usr/lib/python2.7/dist-packages/gi/module.py", line 139, in
_getattr_
self._name_, name))
AttributeError: 'gi.repository.Gdk' object has no attribute 'Image'
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Port to python3

[Abhay Malik]

Hey,
I changed the files as you recommended can you please have a look at it.

Here’s the link  
:https://github.com/sugarlabs/reflect/pull/13/files#diff-03091df2633029b2c2893b03883f5296
 



Thanks,
Abhay___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to python3 (3 of 10)

[James Cameron]

Thanks.

I'm almost always off-grid on Sundays.  Specifically from sunset on my 
Saturday, to sunset on my Sunday.  I'm in the Sydney Australia timezone, but 
about 400km away.

Also, this week I'm at linux.conf.au.

I expect to catch up with mail, pull requests, and issues some time next week.

I had mentioned this to several people, but perhaps other people were not on 
IRC.

On Sun, Jan 12, 2020 at 02:58:07PM +0530, ayush nawal wrote:
> Don't worry about it abhay, James get busy sometimes on weekends, you can
> continue with any other task till then. Submit a pull request and he will
> surely get back to you in time.
> 
> Regards
> Ayush
> 
> On Sun, 12 Jan, 2020, 8:23 am Abhay Malik, <[1]eshanmalik150...@gmail.com>
> wrote:
> 
> Hey, sorry to disturb,
>         It has been more than 36 hours and no one has reviewed my task,
> just wondering why that happened.
> 
> Thanks,
> Abhay
> 
> ___
> Sugar-devel mailing list
> [2]Sugar-devel@lists.sugarlabs.org
> [3]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:eshanmalik150...@gmail.com
> [2] mailto:Sugar-devel@lists.sugarlabs.org
> [3] 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

Re: [Sugar-devel] Port to python3 (3 of 10)

[ayush nawal]

Don't worry about it abhay, James get busy sometimes on weekends, you can
continue with any other task till then. Submit a pull request and he will
surely get back to you in time.

Regards
Ayush

On Sun, 12 Jan, 2020, 8:23 am Abhay Malik, 
wrote:

> Hey, sorry to disturb,
> It has been more than 36 hours and no one has reviewed my task,
> just wondering why that happened.
>
>
> Thanks,
> Abhay
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Port to python3 (3 of 10)

[Abhay Malik]

Hey, sorry to disturb,
It has been more than 36 hours and no one has reviewed my task, just 
wondering why that happened.


Thanks,
Abhay

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

[Sugar-devel] Port

[Abhay Malik]

hey, 
 how are you?, hope this a good time to talk?
 so basically, I am doing the porting to python 3 task, i got 
everything running but i'm stuck at this step which is to  test 
the activity on the virtual machine, then edit the sources over SSH using your 
IDE ,test the modified activity on  the virtual machine, and 
commit the changes, etc, as per the usual GitHub workflow, so how do i do this.___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to Python 3 (1 of 5)

[James Cameron]

We have a Python 3 Porting Guide;

https://github.com/sugarlabs/sugar-docs/blob/master/src/python-porting-guide.md

Skills you need, or will acquire, are;

- knowing how to write and debug programs in Python 2,

- knowing how to write and debug programs in Python 3,

We also have a Measuring coverage of Python activities
https://github.com/sugarlabs/sugar-docs/blob/master/src/python-coverage-guide.md

On Fri, Dec 06, 2019 at 10:23:45AM +0530, Abhay Malik wrote:
> Hey,
>   I am planning to start this task (Port to Python 3 (1 of 5)), but 
> however I’m a bit lost and I don’t know where to start, so can you please 
> give me some pointers as of where to begin to start doing this task 
> ___
> 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

[Sugar-devel] Port to Python 3 (1 of 5)

[Abhay Malik]

Hey,
I am planning to start this task (Port to Python 3 (1 of 5)), but 
however I’m a bit lost and I don’t know where to start, so can you please give 
me some pointers as of where to begin to start doing this task 
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to Python 3 - Status

[Walter Bender]

On Wed, Aug 14, 2019 at 4:01 AM James Cameron  wrote:

> G'day,
>
> Sugar modules are ported to Python 3;
>
> sugar-artwork (themes and icons)
> sugar-toolkit-gtk3 (toolkit)
> sugar-datastore (journal backend)
> gwebsockets
> sugar (graphical shell)
> browse (activity)
> hello-world (activity)
>
> Sugar starts and is usable.  A few minor issues have been added in
> GitHub.
>
> https://github.com/sugarlabs/sugar/issues/853
> https://github.com/sugarlabs/sugar/issues/854
> https://github.com/sugarlabs/sugar/issues/855
>
> Next, I'll be testing and merging pull requests for core activities.
>
> Thanks to Rahul and Aniket for all the hard work.
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>

Fantastic!!!

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

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

[Sugar-devel] Port to Python 3 - Status

[James Cameron]

G'day,

Sugar modules are ported to Python 3;

sugar-artwork (themes and icons)
sugar-toolkit-gtk3 (toolkit)
sugar-datastore (journal backend)
gwebsockets
sugar (graphical shell)
browse (activity)
hello-world (activity)

Sugar starts and is usable.  A few minor issues have been added in
GitHub.

https://github.com/sugarlabs/sugar/issues/853
https://github.com/sugarlabs/sugar/issues/854
https://github.com/sugarlabs/sugar/issues/855

Next, I'll be testing and merging pull requests for core activities.

Thanks to Rahul and Aniket for all the hard work.

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

[Sugar-devel] Port to Python 3 - Aniket and James chat

[James Cameron]

Aniket and I had a brief conversation just now.  Here's a summary;

1.  Porting to TelepathyGLib is necessary.  Understanding of Telepathy
is challenged by how it operates as a DBus service.  My post on 8th
March
http://lists.sugarlabs.org/archive/sugar-devel/2019-March/056365.html
describes how to use dbus-monitor to watch the communication between
the Telepathy API and the Telepathy service processes.

2.  Sugar doesn't have a "make uninstall" target.  This makes it hard
to test changes.  Options are (a) use the install log, (b) touch a
marker file and use find to list the files installed, (c) use
checkinstall.  Other developers may benefit from a working uninstall
target.

3.  Alternative to using "make uninstall" and "make install" cycles is
to edit the source files in place on a test VM, or use rsync to copy
them from your git repository to the VM over SSH,

rsync -r --checksum src/jarabe $HOST:/usr/local/lib/pythonN.M/dist-packages/
rsync -r --checksum extensions $HOST:/usr/local/share/sugar/

4.  in general if you can't test code within three to ten seconds of
saving a source file, you can spend some time to make tools to speed
that up.

5.  Datastore is also hard to test because it is a DBus service.  The
old one must be stopped, then removed, before a new one is installed
and started.  There's probably useful information from the DBus
project about how to do it differently.

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

Re: [Sugar-devel] Port to python 3 project

[James Cameron]

Yes, the GSoC project idea is for porting Sugar and the core
activities.

The Toolkit is to be Python 2 and Python 3 according to how it is
installed.  A typical system may have two installs of the Toolkit.

Porting of other activities can be done if there is time available, or
as part of demonstrating your capability in a proposal.

Sugargame is ported, but is waiting for release of Toolkit.

https://github.com/sugarlabs/sugargame/issues/2
https://github.com/sugarlabs/sugargame/pull/5
https://github.com/sugarlabs/sugargame/tree/python3

But don't imagine the GSoC project idea is only porting of source
code; there must also be releasing, packaging, and testing.  It was
too much for GSoC 2018.

On Tue, Mar 12, 2019 at 02:26:34PM +0530, aniket mathur wrote:
> Porting of all fructose activities was included as a part of the GSOC project.
> Does porting other activities to python 3 is not required  or simply  it is of
> less priority?
> Sugargame is also not ported to python 3.

> ___
> 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

[Sugar-devel] Port to python 3 project

[aniket mathur]

Porting of all fructose activities was included as a part of the GSOC
project. Does porting other activities to python 3 is not required  or
simply  it is of less priority?
Sugargame is also not ported to python 3.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to Python3

[James Cameron]

Thanks for looking.  I've answered in 
https://github.com/sugarlabs/sugar/issues/787

On Sun, Mar 03, 2019 at 01:53:51PM +0530, Gautham santhosh wrote:
> I went through #805 [0] and found that a lot of the files in src/jarabe
> has already been changed. So only the rest of the files needs to be changed
> right?
> 
> [0][1]https://github.com/sugarlabs/sugar/pull/805/commits/
> 7ed885c99925b4bc942874e282f2d961ec6dfbd4

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

[Sugar-devel] Port to Python3

[Gautham santhosh]

I went through #805 [0] and found that a lot of the files in src/jarabe
has already been changed. So only the rest of the files needs to be changed
right?

[0]
https://github.com/sugarlabs/sugar/pull/805/commits/7ed885c99925b4bc942874e282f2d961ec6dfbd4
-- 
---
Regards,
Gautham Santhosh
GitHub .
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port Sugar and core activities to Python 3 GSoC 2019

[James Cameron]

Someone wrote:
> [...] I am interested in "Port Sugar and core activities to Python
> 3" project and would like to work as a GSoC student developer with
> Sugar Labs.
>
> I am well experienced in python, though I am novice to porting but I
> am interested in learning, I thought it would be better to
> contribute before applying which would give some credibility. Please
> let me know how to get started and work on this projects where can
> I learn about this.

Yes.

Please use the mailing list sugar-devel@ and do not contact me
privately for questions that are of general interest.  Make sure you
are subscribed.

You might do these things;

- read the community documentation, especially code of conduct,
  https://github.com/sugarlabs/sugar-docs

- read the Sugar source code and documentation,
  https://github.com/sugarlabs/sugar
  https://github.com/sugarlabs/sugar/tree/master/docs

- read the Sugar Toolkit source code and documentation,
  https://github.com/sugarlabs/sugar-toolkit-gtk3

- read the Port to Python 3 project plan,
  https://github.com/orgs/sugarlabs/projects/1

- read the critical issues in the plan and the individual issue plans,

- prepare a native development environment suitable for testing Sugar
  and all dependencies,

- review pull requests and existing branches for the Port to Python 3,

- test Sugar, and report problems with Sugar,

- prepare Fedora and Ubuntu packages for Sugar components,
  
https://github.com/sugarlabs/sugar/blob/master/docs/debian-packaging-example.md

- fix problems, making pull requests and working through code review
  to get the pull requests merged,
  
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#making-commits
  
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#sending-a-pull-request

- review new pull requests by other developers.
  
https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#guide-for-reviewers

List is incomplete.  Good luck!

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

Re: [Sugar-devel] Port to TelepathyGLib

[Rahul Bothra]

Hi,

On Thu, May 17, 2018 at 3:11 AM, James Cameron  wrote:
> As you may have seen in my post in the last hour, forks of software
> dilute maintainership, and everyone is worse off.

> As part of porting to Python 3, we need to port to TelepathyGLib as
> well.  This is because there is no maintained static binding of
> Telepathy for Python 3.

> If we were to bundle Telepathy inside Sugar, we would most likely lose
> automatic maintenance of Telepathy.  Downstream distribution packagers
> know about this risk, and often give upstream projects a nudge about
> it.  An example is the Rsvg static binding that, while it was quite
> trivial, became a hot topic and eventually caused our GTK+ 2 toolkit
> to be dropped from Debian and Ubuntu, despite other GTK+ 2
> applications remaining.


Thanks for the detailed explanation. I agree, we should port.


> We may face other ports as well.  We're yet to uncover them, and may
> only uncover them by trying to run the code.  I'm hoping we don't have
> to port from static binding for D-Bus, but I won't know until we test
> the code.

Yes, I am not yet sure about D-Bus

> Don't worry about the 72 results of search;
> 1.  many of those activities don't work now, so there would be no
> significant gain from porting them,
> 2.  some activities are not in https://github.com/sugarlabs/
> 3.  best to concentrate on the "Fructose" set of demonstration
> activities,

Sure, I will keep this in mind, Thank you

> Perhaps the patterns of change can be expressed as a sed(1) script and
> added to your sugar-docs Port to Python 3 checklist?  This will help
> people like me who have activities to maintain.

Sure, I will make one soon.


Thanks

Rahul Bothra (Pro-Panda)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to TelepathyGLib

[James Cameron]

Thanks for working on this.

As you may have seen in my post in the last hour, forks of software
dilute maintainership, and everyone is worse off.

As part of porting to Python 3, we need to port to TelepathyGLib as
well.  This is because there is no maintained static binding of
Telepathy for Python 3.

If we were to bundle Telepathy inside Sugar, we would most likely lose
automatic maintenance of Telepathy.  Downstream distribution packagers
know about this risk, and often give upstream projects a nudge about
it.  An example is the Rsvg static binding that, while it was quite
trivial, became a hot topic and eventually caused our GTK+ 2 toolkit
to be dropped from Debian and Ubuntu, despite other GTK+ 2
applications remaining.

We may face other ports as well.  We're yet to uncover them, and may
only uncover them by trying to run the code.  I'm hoping we don't have
to port from static binding for D-Bus, but I won't know until we test
the code.

Don't worry about the 72 results of search;

1.  many of those activities don't work now, so there would be no
significant gain from porting them,

2.  some activities are not in https://github.com/sugarlabs/

3.  best to concentrate on the "Fructose" set of demonstration
activities,

Thanks for demonstrating the port complexity in the toolkit
https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/389/commits/a6f2cdaca58bc737d825365afd7bd3d7f12c530c

Perhaps the patterns of change can be expressed as a sed(1) script and
added to your sugar-docs Port to Python 3 checklist?  This will help
people like me who have activities to maintain.

On Thu, May 17, 2018 at 12:17:19AM +0530, Rahul Bothra wrote:
> Hi,
> 
> I started understanding how Telepathy and DBus work, and porting our code to
> use their PyGI bindings instead of static bindings, and it looks like a big
> task.
> Also, GitHub search gives 72 results [1]https://github.com/search?p=5=
> org%3Asugarlabs+%22from+telepathy%22=Code=%E2%9C%93 for instances of
> telepathy
> 
> Instead, Should we pack the static binding port of Telepathy inside
> Sugar-Toolkit. The only change that will then have to be made will be:
> "from telepathy.foo import bar" will have to be changed to "from
> sugar3.telepathy.foo import bar"
> 
> Please suggest if there can be any disadvantages in following this approach ?
> (Sorry, if it is obvious)
> 
> Regards
> Rahul Bothra (Pro-Panda)
> 
> On Wed, May 16, 2018 at 3:56 AM, James Cameron <[2]qu...@laptop.org> wrote:
> 
> On Tue, May 15, 2018 at 11:02:49PM +0530, Rahul Bothra wrote:
> > - Rahul will also contact upstream(s) of Telepathy to ask their
> >   plans of a Python 3.x Telepathy version
> 
> Telepathy upstream suggested using PyGObject API, available for both
> Python 2 and Python 3.
> 
> [3]https://lazka.github.io/pgi-docs/#TelepathyGLib-0.12
> 
> On Ubuntu 18.04 install package gir1.2-telepathyglib-0.12 and then
> this test passes;
> 
> $ python2
> >>> from gi.repository import TelepathyGLib
> 
> $ python3
> >>> from gi.repository import TelepathyGLib
> 
> For the moment, development can happen with your static binding port
> of Telepathy, but we should not plan to rely on it, because
> downstreams already have a Python 3 Telepathy in the form of
> TelepathyGLib.
> 
> So we must port.
> 
> [4]https://github.com/orgs/sugarlabs/projects updated with new "Port to
> TelepathyGLib"
> [5]https://github.com/orgs/sugarlabs/projects/4
> 
> 
> Change from
> 
>         from telepathy.foo import bar
> 
> to
> 
>         import gi
>         gi.require_version('TelepathyGLib', '0.12')
>         from gi.repository import TelepathyGLib
> 
> Prerequisite for Port to Python 3.
> 
>
> --
> James Cameron
> [6]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [7]Sugar-devel@lists.sugarlabs.org
> [8]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] 
> https://github.com/search?p=5=org%3Asugarlabs+%22from+telepathy%22=Code=%E2%9C%93
> [2] mailto:qu...@laptop.org
> [3] https://lazka.github.io/pgi-docs/#TelepathyGLib-0.12
> [4] https://github.com/orgs/sugarlabs/projects
> [5] https://github.com/orgs/sugarlabs/projects/4
> [6] http://quozl.netrek.org/
> [7] mailto:Sugar-devel@lists.sugarlabs.org
> [8] 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

Re: [Sugar-devel] Port to TelepathyGLib

[Rahul Bothra]

Hi,

I started understanding how Telepathy and DBus work, and porting our code
to use their PyGI bindings instead of static bindings, and it looks like a
big task.
Also, GitHub search gives 72 results
https://github.com/search?p=5=org%3Asugarlabs+%22from+telepathy%22=Code=%E2%9C%93
for instances of telepathy

Instead, Should we pack the static binding port of Telepathy inside
Sugar-Toolkit. The only change that will then have to be made will be:
"from telepathy.foo import bar" will have to be changed to "from
sugar3.telepathy.foo import bar"

Please suggest if there can be any disadvantages in following this approach
? (Sorry, if it is obvious)

Regards
Rahul Bothra (Pro-Panda)




On Wed, May 16, 2018 at 3:56 AM, James Cameron  wrote:

> On Tue, May 15, 2018 at 11:02:49PM +0530, Rahul Bothra wrote:
> > - Rahul will also contact upstream(s) of Telepathy to ask their
> >   plans of a Python 3.x Telepathy version
>
> Telepathy upstream suggested using PyGObject API, available for both
> Python 2 and Python 3.
>
> https://lazka.github.io/pgi-docs/#TelepathyGLib-0.12
>
> On Ubuntu 18.04 install package gir1.2-telepathyglib-0.12 and then
> this test passes;
>
> $ python2
> >>> from gi.repository import TelepathyGLib
>
> $ python3
> >>> from gi.repository import TelepathyGLib
>
> For the moment, development can happen with your static binding port
> of Telepathy, but we should not plan to rely on it, because
> downstreams already have a Python 3 Telepathy in the form of
> TelepathyGLib.
>
> So we must port.
>
> https://github.com/orgs/sugarlabs/projects updated with new "Port to
> TelepathyGLib"
> https://github.com/orgs/sugarlabs/projects/4
>
> 
> Change from
>
> from telepathy.foo import bar
>
> to
>
> import gi
> gi.require_version('TelepathyGLib', '0.12')
> from gi.repository import TelepathyGLib
>
> Prerequisite for Port to Python 3.
> 
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port to TelepathyGLib

[James Cameron]

Digigng into mailing list archives, we discussed this four years ago
for previous Port to Python 3 GSoC project [1].  There was also a
discussion in March 2014 [2].  Rahul, please read the threads for
background information.  Very interesting.

It was pointed out that collaboration will need care in testing.

I agree.

It was also said that the Fedora 18 development entrapment for the
OLPC XO-1, XO-1.5, XO-1.75, and XO-4 made a port to Python 3 less
attractive.  With these OLPC XO units now failing from old age, and
newer Ubuntu-based laptops available, this development entrapment is
less of a problem than in 2014.  I don't plan to package Sugar for
Fedora 18 with Python 3, but will instead maintain Python 2 branches
for as long as they are needed.

References:

1.  http://lists.sugarlabs.org/archive/sugar-devel/2014-May/048098.html
2.  http://lists.sugarlabs.org/archive/sugar-devel/2014-March/047416.html

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

[Sugar-devel] Port to TelepathyGLib

[James Cameron]

On Tue, May 15, 2018 at 11:02:49PM +0530, Rahul Bothra wrote:
> - Rahul will also contact upstream(s) of Telepathy to ask their
>   plans of a Python 3.x Telepathy version

Telepathy upstream suggested using PyGObject API, available for both
Python 2 and Python 3.

https://lazka.github.io/pgi-docs/#TelepathyGLib-0.12

On Ubuntu 18.04 install package gir1.2-telepathyglib-0.12 and then
this test passes;

$ python2
>>> from gi.repository import TelepathyGLib

$ python3
>>> from gi.repository import TelepathyGLib

For the moment, development can happen with your static binding port
of Telepathy, but we should not plan to rely on it, because
downstreams already have a Python 3 Telepathy in the form of
TelepathyGLib.

So we must port.

https://github.com/orgs/sugarlabs/projects updated with new "Port to
TelepathyGLib"
https://github.com/orgs/sugarlabs/projects/4


Change from

from telepathy.foo import bar

to

import gi
gi.require_version('TelepathyGLib', '0.12')
from gi.repository import TelepathyGLib

Prerequisite for Port to Python 3.


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

[Sugar-devel] Port from GStreamer Gst.Message.structure to get_structure()

[James Cameron]

GStreamer project removed or deprecated the structure field of Gst.Message, 
replacing it with a method get_structure().

Many activities are affected.

Code pattern to look for is a reference to message.structure, e.g.

bus = pipe.get_bus()
bus.connect('message', _cb)

def _cb(bus, message):
message.structure. ...

References:

https://github.com/orgs/sugarlabs/projects/3
https://lazka.github.io/pgi-docs/Gst-1.0/classes/Bus.html#Gst.Bus.signals.message
https://lazka.github.io/pgi-docs/Gst-1.0/classes/Message.html#Gst.Message.get_structure

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

[Sugar-devel] Port from GConf to Gio.Settings

[James Cameron]

The GNOME GConf library, which was part of GTK+ 2, has or is ending support 
soon, and downstream distributions will cease packaging.

* https://lists.debian.org/debian-devel/2018/02/msg00169.html
* https://developer.gnome.org/gio/stable/ch34.html

Sugar only kept GConf compatibility for upgrades from older versions of Sugar 
that did not use Gio.Settings.  That transition was long ago.  We must now 
remove this compatibility support.

* [ ] port Browse, Read and Write activities from GConf to Gio.Settings,
* [ ] remove GConf from Sugar, Sugar Toolkit, and Browse, Read and Write 
activities,
* [ ] remove GConf from any other activities.

https://github.com/orgs/sugarlabs/projects/2

-- 
James Cameron
http://quozl.netrek.org/
--- Begin Message ---
Control: severity -1 serious

As announced [1], we are working to remove gconf from Debian. As part of this 
process, I am now raising the severity of these bugs.

Please try to port your package away from gconf. Otherwise, please consider 
requesting that your package be removed from Debian to help us complete this 
goal.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

-- 
pkg-sugar-devel mailing list
pkg-sugar-de...@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/pkg-sugar-devel
--- End Message ---
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [PORT TO GTK3] Write

[Ignacio Rodríguez]

I'm trying to do the port to GTK3 Writing and at completion and run the
activity returns me this

-- 
Juan Ignacio Rodríguez
CeibalJAM!
Activity Central


org.laptop.AbiWordActivity-1.log
Description: Binary data
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [PORT TO GTK3] Write

[Gonzalo Odiard]

Hi Ignacio,
Write is already ported, but we have a dependency on a new abiword,
and is not packaged yet, then is a particular difficult area right now.
I hope we will have this solved the next week.

If you want see what other activity need port, you can see here
http://wiki.laptop.org/go/Activities/PortingToGtk3

Gonzalo

On Thu, Oct 11, 2012 at 9:04 AM, Ignacio Rodríguez nachoe...@gmail.comwrote:

 I'm trying to do the port to GTK3 Writing and at completion and run the
 activity returns me this

 --
 Juan Ignacio Rodríguez
 CeibalJAM!
 Activity Central


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


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

Re: [Sugar-devel] [PORT TO GTK3] Write

[Chris Leonard]

On Thu, Oct 11, 2012 at 11:10 AM, Gonzalo Odiard gonz...@laptop.org wrote:
 Hi Ignacio,
 Write is already ported, but we have a dependency on a new abiword,
 and is not packaged yet, then is a particular difficult area right now.
 I hope we will have this solved the next week.

 If you want see what other activity need port, you can see here
 http://wiki.laptop.org/go/Activities/PortingToGtk3


Ignacio,

I would suggest starting on a simpler one like Ruler (ask Walter
Bender) or ask the Activity Central Team if Anish needs some help with
TamTam.

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

[Sugar-devel] Port GTK3

[Ignacio Rodríguez]

Hello, you pass missing GTK3 programs .. Because I think a unique
experience. And I would like to learn. Testing!

-- 
Juan Ignacio Rodríguez
CeibalJAM!
Activity Central
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port GTK3

[Rafael Ortiz]

Hi Ignacio.

On Wed, Oct 10, 2012 at 3:19 PM, Ignacio Rodríguez nachoe...@gmail.comwrote:

 Hello, you pass missing GTK3 programs .. Because I think a unique
 experience. And I would like to learn. Testing!

 --
 Juan Ignacio Rodríguez
 CeibalJAM!
 Activity Central


 ___



Welcome!. testing is great way to learn.



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


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

Re: [Sugar-devel] Port GTK3

[Ignacio Rodríguez]

Rafael, I think comprendistes not, what programs are available to do the
port.
I'm speak spanish:

Rafael, creo que no comprendistes. Que programas estan disponibles para
hacer el port a GTK3!?
2012/10/10 Rafael Ortiz raf...@activitycentral.com

 Hi Ignacio.

 On Wed, Oct 10, 2012 at 3:19 PM, Ignacio Rodríguez nachoe...@gmail.comwrote:

 Hello, you pass missing GTK3 programs .. Because I think a unique
 experience. And I would like to learn. Testing!

 --
 Juan Ignacio Rodríguez
 CeibalJAM!
 Activity Central


 ___



 Welcome!. testing is great way to learn.



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





-- 
Juan Ignacio Rodríguez
CeibalJAM!
Activity Central
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port GTK3

[Rafael Ortiz]

On Wed, Oct 10, 2012 at 3:31 PM, Ignacio Rodríguez nachoe...@gmail.comwrote:

 Rafael, I think comprendistes not, what programs are available to do the
 port.
 I'm speak spanish:

 Rafael, creo que no comprendistes. Que programas estan disponibles para
 hacer el port a GTK3!?


There are plenty of activities yet un-ported.. the best way to test that is
to install the activities you like on a newest OLPC build (sugar  0,96)
and see if they don't start.

For porting please contact the original devs or maintainers.





for example you can take a look at

 2012/10/10 Rafael Ortiz raf...@activitycentral.com

 Hi Ignacio.

 On Wed, Oct 10, 2012 at 3:19 PM, Ignacio Rodríguez 
 nachoe...@gmail.comwrote:

 Hello, you pass missing GTK3 programs .. Because I think a unique
 experience. And I would like to learn. Testing!

 --
 Juan Ignacio Rodríguez
 CeibalJAM!
 Activity Central


 ___



 Welcome!. testing is great way to learn.



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





 --
 Juan Ignacio Rodríguez
 CeibalJAM!
 Activity Central


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


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

Re: [Sugar-devel] Port all activities from cjson to json

[Peter Robinson]

On Mon, Sep 24, 2012 at 7:16 PM, Manuel Kaufmann humi...@gmail.com wrote:
 On Mon, Sep 24, 2012 at 12:53 PM, Daniel Drake d...@laptop.org wrote:
 Info Slicer
 http://bugs.sugarlabs.org/ticket/3950

 I've just closed this ticket because the port was already done.

The port might be done but there's not been a release yet. Both on
a.sl.org and source.sl.org the latest release is 15 and that crashes
at the moment due to the lack of a cjson module.

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

Re: [Sugar-devel] Port all activities from cjson to json

[Peter Robinson]

On Thu, Sep 27, 2012 at 9:46 PM, Rafael Ortiz
raf...@activitycentral.com wrote:


 On Tue, Sep 25, 2012 at 8:07 AM, Simon Schampijer si...@schampijer.de
 wrote:

 On 09/24/2012 09:46 PM, Rafael Ortiz wrote:

 On Mon, Sep 24, 2012 at 1:16 PM, Manuel Kaufmann humi...@gmail.com
 wrote:

 On Mon, Sep 24, 2012 at 12:53 PM, Daniel Drake d...@laptop.org wrote:

 Info Slicer
 http://bugs.sugarlabs.org/ticket/3950


 I've just closed this ticket because the port was already done.


 It's already fixed on speak and chat.
 *

 http://git.sugarlabs.org/speak/mainline/commit/917627f0ffab3b01b764f7169ec87c79a811cc54
 *

 http://git.sugarlabs.org/chat/mainline/commit/302e7334412d98727666146ba4568fc57ce7dd49

 Cheers.


 Can we get a release of those?

 Regards,
Simon


 Working on  speak releases,   Aleksey is chat's maintainer.

What's the status of these releases?

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

Re: [Sugar-devel] Port all activities from cjson to json

[Gonzalo Odiard]

CC: walter

On Sat, Oct 6, 2012 at 10:15 AM, Peter Robinson pbrobin...@gmail.comwrote:

 On Mon, Sep 24, 2012 at 7:16 PM, Manuel Kaufmann humi...@gmail.com
 wrote:
  On Mon, Sep 24, 2012 at 12:53 PM, Daniel Drake d...@laptop.org wrote:
  Info Slicer
  http://bugs.sugarlabs.org/ticket/3950
 
  I've just closed this ticket because the port was already done.

 The port might be done but there's not been a release yet. Both on
 a.sl.org and source.sl.org the latest release is 15 and that crashes
 at the moment due to the lack of a cjson module.

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

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

[Sugar-devel] Port all activities from cjson to json

[Daniel Drake]

Hi,

With the latest sugar-toolkit release, sugar now no longer uses cjson,
which has long been unmaintained and buggy, and no longer has the
speed advantages that it used to (as other libraries have caught up).

Any activity that uses cjson should be ported to use the 'json' module
included in python. http://docs.python.org/library/json.html

This list includes:

Anno
author CCd

Chat
http://bugs.sugarlabs.org/ticket/3949

Info Slicer
http://bugs.sugarlabs.org/ticket/3950

Memorize
http://bugs.sugarlabs.org/ticket/3951

Speak
http://bugs.sugarlabs.org/ticket/3952

Anyone know of others?


This is more of a FYI than anything - its low priority, and OLPC
builds will include python-cjson at least until the last 4 activities
listed above have been ported, which I don't expect to happen
immediately.

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

Re: [Sugar-devel] Port all activities from cjson to json

[Gonzalo Odiard]

Memorize fixed in git, will be in the next version.

Gonzalo

On Mon, Sep 24, 2012 at 12:53 PM, Daniel Drake d...@laptop.org wrote:

 Hi,

 With the latest sugar-toolkit release, sugar now no longer uses cjson,
 which has long been unmaintained and buggy, and no longer has the
 speed advantages that it used to (as other libraries have caught up).

 Any activity that uses cjson should be ported to use the 'json' module
 included in python. http://docs.python.org/library/json.html

 This list includes:

 Anno
 author CCd

 Chat
 http://bugs.sugarlabs.org/ticket/3949

 Info Slicer
 http://bugs.sugarlabs.org/ticket/3950

 Memorize
 http://bugs.sugarlabs.org/ticket/3951

 Speak
 http://bugs.sugarlabs.org/ticket/3952

 Anyone know of others?


 This is more of a FYI than anything - its low priority, and OLPC
 builds will include python-cjson at least until the last 4 activities
 listed above have been ported, which I don't expect to happen
 immediately.

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

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Aleksey Lim]

On Tue, May 22, 2012 at 01:46:48PM -0300, Flavio Danesse wrote:
 Today I will be working on a new patch to fix the
 function Chat.activity Iwas left pending yesterday and fixing some details
 in the typing.
 If you want to give me access to the repo and upload everything in a new
 branch.
 My user is git flavio

Sure, I've added you to chat repository and pushed gtk3 branch.
Feel free to process gtk3 porting work there. I think it will be useful
to keep master bracnh as regular development trunk as long as
majorority of users are on gtk2 based sugar.

 Hoy estaré trabajando en un nuevo parche para Chat.activity para arreglar
 la función que me quedó pendiente ayer y arreglando algunos detalles en el
 tipado.
 Si quieren me dan acceso al repo y subo todo en una rama nueva.
 Mi usuario en git es flavio

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Gonzalo Odiard]

Flavio patches need review.

Also would be good follow in all the activities the suggestions in
http://wiki.sugarlabs.org/go/Features/GTK3/Activity_Porting
regarding to branches. Will do our lives easier in the future :)

Gonzalo

On Wed, May 23, 2012 at 2:41 PM, Aleksey Lim alsr...@sugarlabs.org wrote:

 On Tue, May 22, 2012 at 01:46:48PM -0300, Flavio Danesse wrote:
  Today I will be working on a new patch to fix the
  function Chat.activity Iwas left pending yesterday and fixing some
 details
  in the typing.
  If you want to give me access to the repo and upload everything in a new
  branch.
  My user is git flavio

 Sure, I've added you to chat repository and pushed gtk3 branch.
 Feel free to process gtk3 porting work there. I think it will be useful
 to keep master bracnh as regular development trunk as long as
 majorority of users are on gtk2 based sugar.

  Hoy estaré trabajando en un nuevo parche para Chat.activity para arreglar
  la función que me quedó pendiente ayer y arreglando algunos detalles en
 el
  tipado.
  Si quieren me dan acceso al repo y subo todo en una rama nueva.
  Mi usuario en git es flavio

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

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Aleksey Lim]

On Wed, May 23, 2012 at 03:26:16PM -0300, Gonzalo Odiard wrote:
 Flavio patches need review.

gtk3 branch was created exactly for experiments with gtk3 porting when
master is for regular development until it will be clear that most of
Chat users are on gtk3 based sugar and it is the time to switch to gtk3
Chat for regular coding.

 Also would be good follow in all the activities the suggestions in
 http://wiki.sugarlabs.org/go/Features/GTK3/Activity_Porting
 regarding to branches. Will do our lives easier in the future :)
 
 Gonzalo
 
 On Wed, May 23, 2012 at 2:41 PM, Aleksey Lim alsr...@sugarlabs.org wrote:
 
  On Tue, May 22, 2012 at 01:46:48PM -0300, Flavio Danesse wrote:
   Today I will be working on a new patch to fix the
   function Chat.activity Iwas left pending yesterday and fixing some
  details
   in the typing.
   If you want to give me access to the repo and upload everything in a new
   branch.
   My user is git flavio
 
  Sure, I've added you to chat repository and pushed gtk3 branch.
  Feel free to process gtk3 porting work there. I think it will be useful
  to keep master bracnh as regular development trunk as long as
  majorority of users are on gtk2 based sugar.
 
   Hoy estaré trabajando en un nuevo parche para Chat.activity para arreglar
   la función que me quedó pendiente ayer y arreglando algunos detalles en
  el
   tipado.
   Si quieren me dan acceso al repo y subo todo en una rama nueva.
   Mi usuario en git es flavio
 
  --
  Aleksey
  ___
  Sugar-devel mailing list
  Sugar-devel@lists.sugarlabs.org
  http://lists.sugarlabs.org/listinfo/sugar-devel
 

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


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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Flavio Danesse]

Parece que no se usar las ramas en git, porque no me las actualiza.
No se supone que es así?: git push origin rama



2012/5/23 Aleksey Lim alsr...@sugarlabs.org

 On Wed, May 23, 2012 at 03:26:16PM -0300, Gonzalo Odiard wrote:
  Flavio patches need review.

 gtk3 branch was created exactly for experiments with gtk3 porting when
 master is for regular development until it will be clear that most of
 Chat users are on gtk3 based sugar and it is the time to switch to gtk3
 Chat for regular coding.

  Also would be good follow in all the activities the suggestions in
  http://wiki.sugarlabs.org/go/Features/GTK3/Activity_Porting
  regarding to branches. Will do our lives easier in the future :)
 
  Gonzalo
 
  On Wed, May 23, 2012 at 2:41 PM, Aleksey Lim alsr...@sugarlabs.org
 wrote:
 
   On Tue, May 22, 2012 at 01:46:48PM -0300, Flavio Danesse wrote:
Today I will be working on a new patch to fix the
function Chat.activity Iwas left pending yesterday and fixing some
   details
in the typing.
If you want to give me access to the repo and upload everything in a
 new
branch.
My user is git flavio
  
   Sure, I've added you to chat repository and pushed gtk3 branch.
   Feel free to process gtk3 porting work there. I think it will be useful
   to keep master bracnh as regular development trunk as long as
   majorority of users are on gtk2 based sugar.
  
Hoy estaré trabajando en un nuevo parche para Chat.activity para
 arreglar
la función que me quedó pendiente ayer y arreglando algunos detalles
 en
   el
tipado.
Si quieren me dan acceso al repo y subo todo en una rama nueva.
Mi usuario en git es flavio
  
   --
   Aleksey
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
  

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


 --
 Aleksey

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Aleksey Lim]

On Wed, May 23, 2012 at 04:07:00PM -0300, Flavio Danesse wrote:
 Parece que no se usar las ramas en git, porque no me las actualiza.
 No se supone que es así?: git push origin rama

To checkout new branch, do

git fetch
git checkout origin/gtk3 -b gtk3

to push to new branch

git push origin gtk3

 2012/5/23 Aleksey Lim alsr...@sugarlabs.org
 
  On Wed, May 23, 2012 at 03:26:16PM -0300, Gonzalo Odiard wrote:
   Flavio patches need review.
 
  gtk3 branch was created exactly for experiments with gtk3 porting when
  master is for regular development until it will be clear that most of
  Chat users are on gtk3 based sugar and it is the time to switch to gtk3
  Chat for regular coding.
 
   Also would be good follow in all the activities the suggestions in
   http://wiki.sugarlabs.org/go/Features/GTK3/Activity_Porting
   regarding to branches. Will do our lives easier in the future :)
  
   Gonzalo
  
   On Wed, May 23, 2012 at 2:41 PM, Aleksey Lim alsr...@sugarlabs.org
  wrote:
  
On Tue, May 22, 2012 at 01:46:48PM -0300, Flavio Danesse wrote:
 Today I will be working on a new patch to fix the
 function Chat.activity Iwas left pending yesterday and fixing some
details
 in the typing.
 If you want to give me access to the repo and upload everything in a
  new
 branch.
 My user is git flavio
   
Sure, I've added you to chat repository and pushed gtk3 branch.
Feel free to process gtk3 porting work there. I think it will be useful
to keep master bracnh as regular development trunk as long as
majorority of users are on gtk2 based sugar.
   
 Hoy estaré trabajando en un nuevo parche para Chat.activity para
  arreglar
 la función que me quedó pendiente ayer y arreglando algunos detalles
  en
el
 tipado.
 Si quieren me dan acceso al repo y subo todo en una rama nueva.
 Mi usuario en git es flavio
   
--
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
   
 
   ___
   Sugar-devel mailing list
   Sugar-devel@lists.sugarlabs.org
   http://lists.sugarlabs.org/listinfo/sugar-devel
 
 
  --
  Aleksey
 

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Flavio Danesse]

Si, pero me da error:

error: src refspec gtk3 matches more than one.
error: failed to push some refs to 'gitori...@git.sugarlabs.org:
chat/mainline.git'


2012/5/23 Aleksey Lim alsr...@sugarlabs.org

 On Wed, May 23, 2012 at 04:07:00PM -0300, Flavio Danesse wrote:
  Parece que no se usar las ramas en git, porque no me las actualiza.
  No se supone que es así?: git push origin rama

 To checkout new branch, do

git fetch
git checkout origin/gtk3 -b gtk3

 to push to new branch

git push origin gtk3

  2012/5/23 Aleksey Lim alsr...@sugarlabs.org
 
   On Wed, May 23, 2012 at 03:26:16PM -0300, Gonzalo Odiard wrote:
Flavio patches need review.
  
   gtk3 branch was created exactly for experiments with gtk3 porting when
   master is for regular development until it will be clear that most of
   Chat users are on gtk3 based sugar and it is the time to switch to gtk3
   Chat for regular coding.
  
Also would be good follow in all the activities the suggestions in
http://wiki.sugarlabs.org/go/Features/GTK3/Activity_Porting
regarding to branches. Will do our lives easier in the future :)
   
Gonzalo
   
On Wed, May 23, 2012 at 2:41 PM, Aleksey Lim alsr...@sugarlabs.org
   wrote:
   
 On Tue, May 22, 2012 at 01:46:48PM -0300, Flavio Danesse wrote:
  Today I will be working on a new patch to fix the
  function Chat.activity Iwas left pending yesterday and fixing
 some
 details
  in the typing.
  If you want to give me access to the repo and upload everything
 in a
   new
  branch.
  My user is git flavio

 Sure, I've added you to chat repository and pushed gtk3 branch.
 Feel free to process gtk3 porting work there. I think it will be
 useful
 to keep master bracnh as regular development trunk as long as
 majorority of users are on gtk2 based sugar.

  Hoy estaré trabajando en un nuevo parche para Chat.activity para
   arreglar
  la función que me quedó pendiente ayer y arreglando algunos
 detalles
   en
 el
  tipado.
  Si quieren me dan acceso al repo y subo todo en una rama nueva.
  Mi usuario en git es flavio

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

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

 --
 Aleksey

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Aleksey Lim]

On Wed, May 23, 2012 at 04:29:54PM -0300, Flavio Danesse wrote:
 Si, pero me da error:
 
 error: src refspec gtk3 matches more than one.
 error: failed to push some refs to 'gitori...@git.sugarlabs.org:
 chat/mainline.git'

Sorry, I create tag with the same name. fixed.

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Manuel Kaufmann]

On Mon, May 21, 2012 at 9:58 PM, Flavio Danesse
fdane...@activitycentral.com wrote:
 Paso port a sugar3 de Chat.activity

Hello Flavio,

Please, take in mind that we have a proccess[1] to submit a patch and
try to follow it. It better for all of us if we all follow those
steps.

Regarding porting Chat to GTK3, there is another wiki page[2] that
explains the process (related with branches).

Another thing that I'd like to mention is the language. This list is
in English, and it would be good if we can respect that. I wouldn't
like to start reading emails in German or Chineese (I don't have any
problem with those languages, but I don't understand a word :P )

With this things said, thanks a lot for the patch and your work!

[1] http://wiki.sugarlabs.org/go/Development_Team/Code_Review
[2] http://wiki.sugarlabs.org/go/Features/GTK3/Porting

-- 
Kaufmann Manuel
Blog: http://humitos.wordpress.com/
Porfolio: http://fotos.mkaufmann.com.ar/
PyAr: http://www.python.com.ar/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Manuel Kaufmann]

On Tue, May 22, 2012 at 7:12 AM, Aleksey Lim alsr...@sugarlabs.org wrote:
 If yes, I can create gtk3 branch and you can commit there.

Just in case. This[1] is the way to create a branch to port activities

[1] http://wiki.sugarlabs.org/go/Features/GTK3/Porting#Preparation

-- 
Kaufmann Manuel
Blog: http://humitos.wordpress.com/
Porfolio: http://fotos.mkaufmann.com.ar/
PyAr: http://www.python.com.ar/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Manuel Quiñones]

2012/5/22 Aleksey Lim alsr...@sugarlabs.org:
 On Mon, May 21, 2012 at 09:58:24PM -0300, Flavio Danesse wrote:
 Paso port a sugar3 de Chat.activity

 Thanks, are you willing to suport gtk3 port?
 If yes, I can create gtk3 branch and you can commit there.
 Not sure if it makes sense to release gtk3 based Chat on ASLO (ASLO
 doesn't handle a difference between gtk2/3 on client side), but if some
 distros will be interesting in gtk3, they can download a tarball.

You can upload to ASLO and specify that the activity is for Sugar 0.96
(put that same value in from/to versions).  That version is GTK+3
enabled.  We are doing the same in other activities already ported.

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

Re: [Sugar-devel] Port Gtk 3 (Chat.activity)

[Flavio Danesse]

Today I will be working on a new patch to fix the
function Chat.activity Iwas left pending yesterday and fixing some details
in the typing.
If you want to give me access to the repo and upload everything in a new
branch.
My user is git flavio

Hoy estaré trabajando en un nuevo parche para Chat.activity para arreglar
la función que me quedó pendiente ayer y arreglando algunos detalles en el
tipado.
Si quieren me dan acceso al repo y subo todo en una rama nueva.
Mi usuario en git es flavio
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel