Line 1: |
Line 1: |
| == Pippy Design Idea == | | == Pippy Design Idea == |
| | | |
| + | A running Pippy instance will contain the following user data: |
| + | *zero or more python zip bundles, |
| + | |
| + | List of changes: |
| *remove the examples widget from the main screen, provide it only as an "open an example bundle" function, | | *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, | | *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, |
Line 10: |
Line 14: |
| *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, |
| *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, |
| + | |
| + | <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. |