Talk:OLPC Python Environment: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
=== |
=== Fix links to MacOS X, Windows instructions === |
||
These instructions are '''very''' out of date, and do not work. They should be |
These instructions are '''very''' out of date, and do not work. They should be fixed and updated by someone with experience. |
||
Someone new trying to install [[Sugar]] will be turned away if they have to go through all those steps to end up with something that is not functional. |
|||
---- |
|||
Will the SVG part of gecko be included? |
|||
That's part of the plan, yes. - Blizzard |
|||
It might be better to point people to the QEMU instructuions. |
|||
---- |
---- |
||
Revision as of 12:25, 6 November 2006
Fix links to MacOS X, Windows instructions
These instructions are very out of date, and do not work. They should be fixed and updated by someone with experience.
Someone new trying to install Sugar will be turned away if they have to go through all those steps to end up with something that is not functional.
It might be better to point people to the QEMU instructuions.
When you are doing the planning for a Setting Up a Sugar Development Environment on Windows page could you possibly arrange for it to be arranged so that one can download one .exe executable from the web and then running that executable installs it all automatically please? Some of the open source projects that one sees seem to assume great proficiency with unix and/or building up software systems and choosing this module and that module and unpacking tar and z something files. I feel that it needs a straightforward way for people to get the Sugar Development Environment set up with every step explained, so that they can start to use it rather than need to start trying to figure out how to get it installed.
- Sugar is currently under heavy development. The focus is on development, not testing--once the focus shifts an easy-to-use executable will surely become available. --SamatJain 11:58, 5 July 2006 (EDT)
Don't combine with Sugar at this point
It may make sense to combine this with SUGAR after it has stabilized but for now, we need some guidance for application developers, not systems developers. These people will be using Python as their main, or only development tool. They need help in getting Sugar running purely as a test environment for their app, not the whole thing that is used for more general system testing (dbus) or usability testing.
Right now the Sugar developers are maintaining pages oriented to people who want to help build SUGAR itself and that is a good way to keep things separated at this time.
- What is the difference between the OLPC Python Environment and Sugar? From their current descriptions, they sound identical. I don't think OLPC Python Environment should be mistaken for "application development environment" (e.g. what libraries, Python modules, etc are available) since they may not be Python-centric and will not stabilized for probably quite some time. --SamatJain 11:55, 5 July 2006 (EDT)
- The majority of application developers will be domain specialists, not programmers. For instance they will be scientists or teachers and they need straightforward development tools like Python to work with. If an educator sits down on their Windows machine and develops an application with Python and GTK, then only a small amount of work would need to be done to adapt it to the OLPC. The intent of this page: OLPC Python Environment is to have a description of the basic Python-based environment that is available for these developers to work with.