Difference between revisions of "User:Quozl"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
== Pippy Design Idea == | == Pippy Design Idea == | ||
− | A running Pippy instance will contain the following | + | Purpose: |
+ | *increase code sharing, | ||
+ | *increase relevance to Python users. | ||
+ | |||
+ | A running Pippy instance will contain the following data: | ||
*zero or more python zip bundles, | *zero or more python zip bundles, | ||
+ | *each python zip bundle will include a setup.py capable of creating the zip bundle output, | ||
+ | |||
+ | Pippy may read from: | ||
+ | *a saved instance of Pippy, in the journal, | ||
+ | *example zip bundles included with Pippy, | ||
+ | |||
+ | Pippy may write to: | ||
+ | *a saved instance of Pippy, in the journal, | ||
+ | *a zip bundle in the journal. | ||
List of changes: | List of changes: | ||
Line 12: | Line 25: | ||
*on standard sugar save, save all zip bundles and files in a sugar journal entry, | *on standard sugar save, save all zip bundles and files in a sugar journal entry, | ||
*provide an export zip bundle button that creates a sugar journal entry of type zip bundle, for sharing, | *provide an export zip bundle button that creates a sugar journal entry of type zip bundle, for sharing, | ||
− | *provide a way to import zip bundles from journal into the current pippy instance, | + | *provide a way to import zip bundles from journal into the current pippy instance, using the object chooser, |
*on execution of a bundle, allow access to all other currently loaded bundles via import, and access to system bundles via import, | *on execution of a bundle, allow access to all other currently loaded bundles via import, and access to system bundles via import, | ||
+ | == Discussion Log == | ||
<Quozl> pippy screen might contain a series of zip bundles. each bundle might contain multiple files, including the setup.py perhaps hidden. learner might load some bundles into pippy, then write a program as a new bundle that imports the other bundles. | <Quozl> pippy screen might contain a series of zip bundles. each bundle might contain multiple files, including the setup.py perhaps hidden. learner might load some bundles into pippy, then write a program as a new bundle that imports the other bundles. | ||
<Quozl> i think the program output window might be separate to the main view ... something that pops up when "run" is pressed. | <Quozl> i think the program output window might be separate to the main view ... something that pops up when "run" is pressed. |
Revision as of 18:44, 9 March 2011
Pippy Design Idea
Purpose:
- increase code sharing,
- increase relevance to Python users.
A running Pippy instance will contain the following data:
- zero or more python zip bundles,
- each python zip bundle will include a setup.py capable of creating the zip bundle output,
Pippy may read from:
- a saved instance of Pippy, in the journal,
- example zip bundles included with Pippy,
Pippy may write to:
- a saved instance of Pippy, in the journal,
- a zip bundle in the journal.
List of changes:
- remove the examples widget from the main screen, provide it only as an "open an example bundle" function,
- remove the output window from the main screen, provide it only when a program is run, and only if the program generates stdout or reads from stdin,
- enlarge the program text entry widget to be nearly full screen,
- encapsulate the program text entry widget in tabs for files in a zip bundle,
- encapsulate the bundle in tabs for zip bundles loaded into pippy instance,
- on standard sugar save, save all zip bundles and files in a sugar journal entry,
- provide an export zip bundle button that creates a sugar journal entry of type zip bundle, for sharing,
- provide a way to import zip bundles from journal into the current pippy instance, using the object chooser,
- on execution of a bundle, allow access to all other currently loaded bundles via import, and access to system bundles via import,
Discussion Log
<Quozl> pippy screen might contain a series of zip bundles. each bundle might contain multiple files, including the setup.py perhaps hidden. learner might load some bundles into pippy, then write a program as a new bundle that imports the other bundles. <Quozl> i think the program output window might be separate to the main view ... something that pops up when "run" is pressed. <Quozl> i think the series of examples takes up space unnecessarily. <m_anish> Quozl yep, and an activity for a kid could be to use the existing examples in a bundle to write more complex code <Quozl> yes. <m_anish> Quozl agree <Quozl> each of the samples would be a bundle.