Talk:OLPC Python Environment: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Request for a straightforward way to set up Sugar on a Windows PC please)
(Don't combine with Sugar at this point)
Line 8: Line 8:


----
----

== 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.

Revision as of 20:52, 4 July 2006

Will the SVG part of gecko be included?

That's part of the plan, yes. - Blizzard


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.


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.