Re: [Sugar-devel] Appropriate to call myself senior developer?
On 15 August 2010 05:19, Bernie Innocenti ber...@codewiz.org wrote: El Sat, 14-08-2010 a las 12:28 +0200, Sascha Silbe escribió: Hi! Would anyone dislike me calling myself senior developer and system administrator at Sugar Labs in my CV or consider it inappropriate? If so, what other description would you recommend? +1 from me... ...as long as I can be Senior Wizard Extraordinaire and Überhaxc0r at Sugar Labs and everywhere else :-) Calling ourselves wizards would be interesting. And Silbe, +1. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Patch for documentation of graphics/animator.py
On Sat, Aug 14, 2010 at 18:02, su...@dev.seeta.in wrote: Hello all, I've made some changes to the docstrings in graphics/animator.py for its documentation and have uploaded the HTML generated using sphinx at: http://seeta.in/sugar/api/documentation/desttemp/html2/animator.html You can compare it with the initial one at: http://api.sugarlabs.org/sphinx/animator.html Attaching the original and new animator.py files along with the patch generated using 'git format-patch master' I've also made a spreadsheet for the documentation and am maintaining it at https://spreadsheets.google.com/a/seeta.in/ccc?key=0AjslliQkdNyvdFZjWnNwcEZzSC1fMkt6ZDlOOUFFMUEhl=en#gid=0 Attaching it. Please see if you would like to help or let me know in case of any suggestions/feedback. Hi Kandarp, some suggestions follow: Subject: [PATCH] description of animator.py The docstring for the module animator.py isn't really included in this patch. animator1.py | 69 ++--- This is very weird as there's no animator1.py file in sugar-toolkit. Please go through a git tutorial first, we'll all save time. +:Inherits: gobject.GObject Sphinx cannot get this information from the code? Is it common practice in sphinx-generated docs? +Returns +- None Can we leave this implicit? +Description: Adds animation type Why type? Seems to be adding an Animation instance. +Parameters +- None Can we leave this implicit? +Description: Stops animation, removes animation type See above. +Description: Records starting time, sets timeout_sid Docstrings should describe functionality, not explain the implementation. +class Animation(object): Watch out adding trailing spaces +Description: Updates frame, ends after t=duration PEP 257 says to use the first line for the one-line summary. Are you using any documented guidelines for the format of the docstrings? I would _strongly_ advise to start by adding docstrings to packages and modules. And only once that's done then get to classes and other top-level elements, then finally to methods. If you try to document the details before understanding the big picture, you are likely to fail. Regards, Tomeu Regards, Kandarp. ___ 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] Patch for documentation of graphics/animator.py
Tomeu, Thank you for the pointers. Appreciate it. We'll have a meeting this evening to discuss on your timely feedback. Regards, Manu On Sun, Aug 15, 2010 at 7:51 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Sat, Aug 14, 2010 at 18:02, su...@dev.seeta.in wrote: Hello all, I've made some changes to the docstrings in graphics/animator.py for its documentation and have uploaded the HTML generated using sphinx at: http://seeta.in/sugar/api/documentation/desttemp/html2/animator.html You can compare it with the initial one at: http://api.sugarlabs.org/sphinx/animator.html Attaching the original and new animator.py files along with the patch generated using 'git format-patch master' I've also made a spreadsheet for the documentation and am maintaining it at https://spreadsheets.google.com/a/seeta.in/ccc?key=0AjslliQkdNyvdFZjWnNwcEZzSC1fMkt6ZDlOOUFFMUEhl=en#gid=0 Attaching it. Please see if you would like to help or let me know in case of any suggestions/feedback. Hi Kandarp, some suggestions follow: Subject: [PATCH] description of animator.py The docstring for the module animator.py isn't really included in this patch. animator1.py | 69 ++--- This is very weird as there's no animator1.py file in sugar-toolkit. Please go through a git tutorial first, we'll all save time. +:Inherits: gobject.GObject Sphinx cannot get this information from the code? Is it common practice in sphinx-generated docs? +Returns +- None Can we leave this implicit? +Description: Adds animation type Why type? Seems to be adding an Animation instance. +Parameters +- None Can we leave this implicit? +Description: Stops animation, removes animation type See above. +Description: Records starting time, sets timeout_sid Docstrings should describe functionality, not explain the implementation. +class Animation(object): Watch out adding trailing spaces +Description: Updates frame, ends after t=duration PEP 257 says to use the first line for the one-line summary. Are you using any documented guidelines for the format of the docstrings? I would _strongly_ advise to start by adding docstrings to packages and modules. And only once that's done then get to classes and other top-level elements, then finally to methods. If you try to document the details before understanding the big picture, you are likely to fail. Regards, Tomeu Regards, Kandarp. ___ 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] (no subject)
HI all, When we start sugar-emulator in ubuntu , The title text in emulator window shows [Xephyr on 30.0].Now , after going through code and other resources what i deducted is that Xephyr is window/session manager which we uses to run sugar on Ubuntu.Now when i tried to find the source for text in code ,but I was directed towards xpehyr which means that the text in window is given by Xephyr . Now , i was wondering if there is any way so that we could indiacate that sugar emulator session was in progress.Like replacing/adding text in title bar with Sugar-something ? Regards, Ankur ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Appropriate to call myself senior developer?
El Sun, 15-08-2010 a las 11:41 +0100, Lucian Branescu escribió: ...as long as I can be Senior Wizard Extraordinaire and Überhaxc0r at Sugar Labs and everywhere else :-) Calling ourselves wizards would be interesting. Oompa-Loompas might be more appropriate :-) http://en.wikipedia.org/wiki/Oompa-Loompa -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Control Panel
On Sat, Aug 14, 2010 at 4:48 PM, u...@dev.seeta.in wrote: Hi, I was working on making some changes in sugar control panel in Ubuntu ,such that it should not require any restart even when very small change is made. So, can you tell me and help me out to figure that what changes are small enough so that they should not require changes.I will Try to make changes accordingly. On my findings, 1. my xo 2. date and time 3.frames 4.languages 5.modem configuration in the above options i am not able to make changes without restart.the rest options are working fine without restart. when we click on restart it doesnt restart sugar either. Few pointers would be helpful and I would really appreciate your support in this direction. Regards, Ankur Khurana. Research Engineer,SEETA http://seeta.in/ I would suggest starting with the date time configurating. 1. Look at the code how date/time are handles in the Sugar control panel. 2. Look at the code for gnome clock handles updating the date and time without a restart. 3. Apply what you learned in step two to step one. david ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Control Panel
On Sun, Aug 15, 2010 at 18:36, David Farning dfarn...@gmail.com wrote: On Sat, Aug 14, 2010 at 4:48 PM, u...@dev.seeta.in wrote: Hi, I was working on making some changes in sugar control panel in Ubuntu ,such that it should not require any restart even when very small change is made. So, can you tell me and help me out to figure that what changes are small enough so that they should not require changes.I will Try to make changes accordingly. On my findings, 1. my xo 2. date and time 3.frames 4.languages 5.modem configuration in the above options i am not able to make changes without restart.the rest options are working fine without restart. when we click on restart it doesnt restart sugar either. Few pointers would be helpful and I would really appreciate your support in this direction. Regards, Ankur Khurana. Research Engineer,SEETA http://seeta.in/ I would suggest starting with the date time configurating. 1. Look at the code how date/time are handles in the Sugar control panel. 2. Look at the code for gnome clock handles updating the date and time without a restart. 3. Apply what you learned in step two to step one. Also, it may be interesting to search the mailing lists archives and the bug trackers, I seem to remember this was discussed back then when it was first implemented. Regards, Tomeu david ___ 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] List of widgets used in Sugar?
Is there a list of current widgets that are used in Sugar activities? The Activity Team's wiki[1] now links to a page that is labelled as obsolete. *Status* My focus is currently on the widget identification system for Experior [2] (nee Sugarbot). The system enables scripting to take place. The system needs to support Sugar 0.84 widgets (icons, rather than text). As every type of gtk.Widget has its own quirks, I would like to prioritise them. More generally, Experior is coming along relatively nicely. I am progressively rewriting quite a lot of unpythonic code. This should result speedups readability improvements. I still expect the code to be replaced with Dogtail, but I'm not sure how difficult that will be. The canonical branch is being hosted on GitHub [3]. Partially because I wanted to see what all the fuss was about. Mainly because of its lightweight issue tracker. Once I feel that the code is at a fairly stable state, I'll move the tracker to bugs.sugarlabs.org. *Emerging Issues:* - Experior is designed to test actvities, I can't seem to test sugar-core UI feature atm [1] http://wiki.sugarlabs.org/go/Activity_Team#sugar-widgets_library [2] http://git.sugarlabs.org/projects/experior [3] http://github.com/timClicks/experior ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel