User talk:Jcfrench: Difference between revisions
(Great stuff, to learn to understand Sugar!) |
m (formating comments) |
||
(9 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
Thanks for your fascinating detective story! |
Thanks for your fascinating detective story! |
||
It is definitively stuff for including with laptop translated to their own language in addition to people curious to learn Python and development for Sugar, like me. |
It is definitively stuff for including with laptop translated to their own language in addition to people curious to learn Python and development for Sugar, like me. |
||
⚫ | |||
== Sugar Architecture == |
|||
⚫ | |||
--[[User:Tonyv|Tonyv]] 06:12, 27 February 2007 (EST) |
--[[User:Tonyv|Tonyv]] 06:12, 27 February 2007 (EST) |
||
== OLPC-HIG == |
|||
follow-up to [[User talk:Xavi#API Links]] |
|||
:Be my guest! :) I added the ''obvious'' links to the HIG... but didn't know which others would really fit and where. BTW, adding the HIG-links was mainly a suggestion, as I think it could add more context... but if you think one of 'my' links shouldn't go or point elsewhere, please change them :) If you need any help, just ask! :) --[[User:Xavi|Xavi]] 17:04, 5 March 2007 (EST) |
|||
== OLPC-HIG API == |
|||
follow-up to [[User talk:Xavi#User Interface for the illiterate]] |
|||
:Hi! I think there's been a glitch... I'm not the author, nor curator, nor reviewer or anything about the [[OLPC Human Interface Guidelines]]... just somebody that translated it into [[OLPC Human Interface Guidelines/lang-es|spanish]]... |
|||
:I would recommend you contact OLPC people, or those that collaborated editing it ([[User:Walter|Walter Bender]], difinitely OLPC; not sure about [[User:Eben|Eben]]) if you plan to change anything else. |
|||
:BTW, I thought that by [[API]] links you were planning to point ''towards'' the OLPC-HIG, not point ''from''... no problem, I like the additions :) but would check with OLPC people just to be on the safe side :) |
|||
:As for the ''illiterate interface'', I do agree that it's a point to be considered (quite seriously) if not just for the kids, but also for their parents and other community members that could be illiterate adults... a solution could involve the [[End-user application software#Text to speech|text to speech]] of the [[OLPC Human Interface Guidelines/The Sugar Interface/Rollovers|Rollovers]] but quite honestly, I'd be just guessing about what makes sense for illiterate people... Cheers! --[[User:Xavi|Xavi]] 19:30, 7 March 2007 (EST) |
|||
== API Templates == |
|||
follow-up to adjoint text in [[User talk:Xavi#API Links]] |
|||
:Templates? Don't know if I'm the best around for it, but will definitely try to help! :) |
|||
:I have no clue about [[Python]] code structure... so I would need some input on what the standard, optional, and other data you have in mind to include in the template... I'll check some docs (currently looking at [[Python Style Guide]], and see what I can come back with... nevertheless any starting input will be appreciated! :) --[[User:Xavi|Xavi]] 19:53, 7 March 2007 (EST) |
|||
== Sugar documentation == |
|||
I hope you can cover things in a generic non-Python way as well. I'm porting [[Tux Paint]], which is in plain old C. I can only read Python in the most superficial way, just as many people would read FORTRAN or Ada. I have no idea how to query or change the screen mode, deal with Sugar's file selection, interact with the mesh, etc. [[User:AlbertCahalan|AlbertCahalan]] 12:06, 12 March 2007 (EDT) |
|||
I need to make this go away: |
|||
ERROR - /usr/share/activities/tuxpaint.activity must specify a service name |
|||
I don't want this bloat. Adding a dummy service name eliminates the message, but then Sugar gets all stupid about not seeing my app. Neither GNOME nor KDE has this problem, nor any old-style setup. Assuming that I really do need to link against the dbus library, what do I shove down the pipe to pacify Sugar? |
|||
[[User:AlbertCahalan|AlbertCahalan]] 22:10, 22 March 2007 (EDT) |
|||
== Welcome, and development == |
|||
<div style="border:2px solid #fda; padding:8px; margin:1px; background-color:#fffdf9"> |
|||
[[Image:Green and white machine.jpg|right|150px]] |
|||
Welcome to the One Laptop per Child wiki. Please make yourself at home; read through the [[Table of Contents]] and [[OLPC FAQ|FAQ]], and take a look around. |
|||
Some possible pages of interest: |
|||
* [[Pictures]] |
|||
* [[Ask OLPC a Question]] |
|||
* [[OS images for emulation]] |
|||
* [[Content]], [[Software]], [[Hardware]] |
|||
* [[Rollout and community building ideas]] |
|||
Feel free to leave me a note on my [[User talk:Sj|talk page]] if you have further questions or need help finding your way around. |
|||
</div> |
|||
What do you mean by your interest in OLPC Development? It's a red link that I would like to flesh out... [[User:Sj|Sj]] [[User talk:Sj|<font color="fc9"><small>talk</small></font>]] 19:05, 18 March 2007 (EDT) |
|||
:SJ, I'm interested in figuring out what it will take to develop OLPC software on an OLPC laptop or emulated environment. Each release, we get a little closer. However, without GIT on the OLPC dev image, it's still very hard. -[[User:Jcfrench|Jeff]] 12:50, 20 March 2007 (EDT) |
|||
== speech synth == |
|||
This is certainly important. I've been talking to some folks at IBM about this -- they have some good packages for same. If you still want to help out in that direction, I can put you in touch with them... [[User:Sj|Sj]] [[User talk:Sj|<font color="fc9"><small>talk</small></font>]] 13:51, 25 May 2007 (EDT) |
Latest revision as of 03:52, 4 July 2007
Thanks for your fascinating detective story! It is definitively stuff for including with laptop translated to their own language in addition to people curious to learn Python and development for Sugar, like me.
Sugar Architecture
I would suggest adding your stuff to Sugar contents directory for the Wiki after checking by the Sugar architects themselves! --Tonyv 06:12, 27 February 2007 (EST)
OLPC-HIG
follow-up to User talk:Xavi#API Links
- Be my guest! :) I added the obvious links to the HIG... but didn't know which others would really fit and where. BTW, adding the HIG-links was mainly a suggestion, as I think it could add more context... but if you think one of 'my' links shouldn't go or point elsewhere, please change them :) If you need any help, just ask! :) --Xavi 17:04, 5 March 2007 (EST)
OLPC-HIG API
follow-up to User talk:Xavi#User Interface for the illiterate
- Hi! I think there's been a glitch... I'm not the author, nor curator, nor reviewer or anything about the OLPC Human Interface Guidelines... just somebody that translated it into spanish...
- I would recommend you contact OLPC people, or those that collaborated editing it (Walter Bender, difinitely OLPC; not sure about Eben) if you plan to change anything else.
- BTW, I thought that by API links you were planning to point towards the OLPC-HIG, not point from... no problem, I like the additions :) but would check with OLPC people just to be on the safe side :)
- As for the illiterate interface, I do agree that it's a point to be considered (quite seriously) if not just for the kids, but also for their parents and other community members that could be illiterate adults... a solution could involve the text to speech of the Rollovers but quite honestly, I'd be just guessing about what makes sense for illiterate people... Cheers! --Xavi 19:30, 7 March 2007 (EST)
API Templates
follow-up to adjoint text in User talk:Xavi#API Links
- Templates? Don't know if I'm the best around for it, but will definitely try to help! :)
- I have no clue about Python code structure... so I would need some input on what the standard, optional, and other data you have in mind to include in the template... I'll check some docs (currently looking at Python Style Guide, and see what I can come back with... nevertheless any starting input will be appreciated! :) --Xavi 19:53, 7 March 2007 (EST)
Sugar documentation
I hope you can cover things in a generic non-Python way as well. I'm porting Tux Paint, which is in plain old C. I can only read Python in the most superficial way, just as many people would read FORTRAN or Ada. I have no idea how to query or change the screen mode, deal with Sugar's file selection, interact with the mesh, etc. AlbertCahalan 12:06, 12 March 2007 (EDT)
I need to make this go away:
ERROR - /usr/share/activities/tuxpaint.activity must specify a service name
I don't want this bloat. Adding a dummy service name eliminates the message, but then Sugar gets all stupid about not seeing my app. Neither GNOME nor KDE has this problem, nor any old-style setup. Assuming that I really do need to link against the dbus library, what do I shove down the pipe to pacify Sugar?
AlbertCahalan 22:10, 22 March 2007 (EDT)
Welcome, and development
Welcome to the One Laptop per Child wiki. Please make yourself at home; read through the Table of Contents and FAQ, and take a look around.
Some possible pages of interest:
- Pictures
- Ask OLPC a Question
- OS images for emulation
- Content, Software, Hardware
- Rollout and community building ideas
Feel free to leave me a note on my talk page if you have further questions or need help finding your way around.
What do you mean by your interest in OLPC Development? It's a red link that I would like to flesh out... Sj talk 19:05, 18 March 2007 (EDT)
- SJ, I'm interested in figuring out what it will take to develop OLPC software on an OLPC laptop or emulated environment. Each release, we get a little closer. However, without GIT on the OLPC dev image, it's still very hard. -Jeff 12:50, 20 March 2007 (EDT)
speech synth
This is certainly important. I've been talking to some folks at IBM about this -- they have some good packages for same. If you still want to help out in that direction, I can put you in touch with them... Sj talk 13:51, 25 May 2007 (EDT)