Talk:Sugar on Windows

From OLPC
Revision as of 11:39, 2 June 2006 by Memracom (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

For me, and, who knows, maybe for some other people as well, this is like a mountain wall of learning above what I know already.

I have recently heard of Python and have just become aware that something called PyGTK exists. What is GTK? What is GECKO? GUI is graphical user interface, I know.

If it all gets into one of those open source website typical get this tar and that z and use this utility obtainable from somewhere else and this version of Windows and that version and so on, it just becomes a task which is a quantum leap above my knowledge and abilities.

If one buys software packages for Windows from places like http://www.serif.co.uk then one simply installs them and if there is a software patch it is downloadable from the internet as a .exe and one simply runs it. One then starts to use the software. It seems to me, possibly unfairly, that at least some open source projects are all tar this and z something that and needing to have been doing these advanced operating system things for some time.

What is it that means that OLPC could not supply the Sugar development system with all the underlying parts like Python in one easy to install .exe installation file?

Once people can get the Sugar environment up and running we could try to get applications up and running. Yet if having the Sugar environment means that one needs all of the background knowledge about operating systems and building up environments from modules and needing to have all of the unpacking tools and so on, then it will not be something in which everyone can participate, each at his or her own level of ability.