Line 2: |
Line 2: |
| | | |
| === Purpose === | | === Purpose === |
| + | *a learner will be able to use examples to write more complex code, |
| + | *a learner will be able to use modules created by other learners to write more complex code, with or without changing the contributed module, |
| *increase code sharing, | | *increase code sharing, |
| *increase relevance to Python users, | | *increase relevance to Python users, |
− | *increase portability of code written. | + | *increase portability of code written, beyond Pippy and Sugar, |
| | | |
| === Data === | | === Data === |
Line 49: |
Line 51: |
| *provide a way to import zip bundles from journal into the current pippy instance, using the object chooser, | | *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> 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.
| |