Talk:Activity tutorial: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
==Critique== |
==Critique== |
||
* The word activity seems highly overloaded/overused; e.g. three different uses in "hello.activity/activity/activity.info". Is it too late to shorten this? Do we really need this much structure and repetition? Similar for the sugar package structure; there's a toplevel package sugar with a subpackage named activity which itself contains a module named activity (and I think that defines a class Activity :-). I'm worried that this is going to cause confusion and hard-to-debug bugs where in a particular context it's hard to guess what the name 'activity' refers to. --Guido van Rossum |
* The word activity seems highly overloaded/overused; e.g. three different uses in "hello.activity/activity/activity.info". Is it too late to shorten this? Do we really need this much structure and repetition? Similar for the sugar package structure; there's a toplevel package sugar with a subpackage named activity which itself contains a module named activity (and I think that defines a class Activity :-). I'm worried that this is going to cause confusion and hard-to-debug bugs where in a particular context it's hard to guess what the name 'activity' refers to. --Guido van Rossum |
||
* As this page is under the "Getting Started" heading, perhaps somewhere.... |
|||
1) ...it could address the questions of "What language are activities written in?" (or make it more clear that all activities are run by an interpreter built into Sugar?) |
|||
2) ...and either explicitly say "There is no compiling of source code to do, the equivalent is part of the "bundling" process", or tell the reader more about the compiling. |
|||
The "source code" "heart" of the HelloWorld example is easy enough to find in what already exists. |
|||
==Image for Emulation Environment== |
==Image for Emulation Environment== |
||
Revision as of 07:36, 20 April 2007
sugar-install-bundle
This script does not exist. Install instructions should exist for:
- easy command-line install
- file-by-file instructions from a root shell
- install via the web browser
GTK and SDL
Not every app performs tolerably OK in Python. Some of us use C with GTK. Some of us use C with SDL. There should be "hello world" examples for these as well.
Critique
- The word activity seems highly overloaded/overused; e.g. three different uses in "hello.activity/activity/activity.info". Is it too late to shorten this? Do we really need this much structure and repetition? Similar for the sugar package structure; there's a toplevel package sugar with a subpackage named activity which itself contains a module named activity (and I think that defines a class Activity :-). I'm worried that this is going to cause confusion and hard-to-debug bugs where in a particular context it's hard to guess what the name 'activity' refers to. --Guido van Rossum
- As this page is under the "Getting Started" heading, perhaps somewhere....
1) ...it could address the questions of "What language are activities written in?" (or make it more clear that all activities are run by an interpreter built into Sugar?)
2) ...and either explicitly say "There is no compiling of source code to do, the equivalent is part of the "bundling" process", or tell the reader more about the compiling.
The "source code" "heart" of the HelloWorld example is easy enough to find in what already exists.
Image for Emulation Environment
- Which image should we be using to performance the helloworld exercise. I tried the livecd_sdk image with vmware and it didn't work.