Changes

A running Pippy instance will contain the following data:

A running Pippy instance will contain the following data:

*zero or more modules,

*zero or more modules,

**(either pure python modules, packages, or distutil source distributions, though not a sugar bundle),

**(either pure python modules, packages, or distutils source distributions, though not a sugar bundle),

*each module will include zero, one (pure python modules) or more (packages or distutil source distributions) source files,

*each module will include zero, one (pure python modules) or more (packages or distutils source distributions) source files,

*each module will include a source file setup.py capable of creating the python distutil source distribution output, but unless the user has asked to edit the setup.py, it will not be shown, instead a default will be used, created and maintained by Pippy,

*each module will include a source file setup.py capable of creating the python distutils source distribution output, but unless the user has asked to edit the setup.py, it will not be shown, instead a default will be used, created and maintained by Pippy,

A shared Pippy will contain the same data as above on each laptop.

A shared Pippy will contain the same data as above on each laptop.

*a module in the journal, (which may have come from a teacher, another learner, or a server), using the object chooser,

*a module in the journal, (which may have come from a teacher, another learner, or a server), using the object chooser,

**in pure python module form, as a single source file,

**in pure python module form, as a single source file,

**in distutil source distribution form, as multiple source files inside a tar or zip container,  

**in distutils source distribution form, as multiple source files inside a tar or zip container,  

*pristine example modules included with Pippy, using a button and an example chooser.

*pristine example modules included with Pippy, using a button and an example chooser.

*a pure python module or package module, which will start the Pippy activity in an execution only mode that behaves in the same way as the "run" button, displaying a VTE (only if stdout is written to, or stdin is read from), and if not exiting immediately, without creating a journal entry.

*a pure python module or package module, which will start the Pippy activity in an execution only mode that behaves in the same way as the "run" button, displaying a VTE (only if stdout is written to, or stdin is read from), and if not exiting immediately, without creating a journal entry.

=== Display ===

=== Display - Editing ===

Display will contain:

Display will contain:

*toolbar,

*toolbar,

(the series of tabs encapsulated in another series of tabs is potentially difficult for a learner to comprehend, but an alternative tree view is thought inappropriate because of the horizontal space consumed, and because use of a module should be constrained to the public API of the module).

(the series of tabs encapsulated in another series of tabs is potentially difficult for a learner to comprehend, but an alternative tree view is thought inappropriate because of the horizontal space consumed, and because use of a module should be constrained to the public API of the module).

Activity canvas GTK+ widget hierarchy:

Activity canvas GTK+ widget hierarchy, assuming two modules open, modules "main" and "test", of which "main" has a file "file.py", and "test" has a file "test.py":

*gtk.Notebook (for viewing and writing code, one page per module)

 

**gtk.Notebook (one page per file in each module)

*gtk.Notebook (tab labels "main", "test", "+")

***GtkSourceView (one for each file in each module)

***notebook page label "setup", a GtkSourceView for "setup.py", hidden if not yet edited by learner,

***notebook page label "+", creates a new file, prompts for file name, defaults to .py,

**notebook page label "test", a gtk.Notebook (tab labels "__doc__", "test.py", "setup.py", "+")

***notebook page label "__doc__", a GtkSourceView in read-only mode, hidden if __doc__ is empty,

***notebook page label "setup", a GtkSourceView for "setup.py", hidden if not yet edited by learner,

 

(if the page "+" technique does not work, then toolbar buttons will be required to create a new module, create a new file in a module, or import an example module).

=== Process ===

=== Display - Running ===

When run is pressed, display will contain:

When run is pressed, display will contain:

*toolbar,

*toolbar,

*stdout stdin vte, (only if stdout is written to, or stdin is read from),

*stdout stdin vte, (only if stdout is written to, or stdin is read from),

*a stop button.

*a stop button.

=== Changes ===

=== Changes ===

Partial list of changes to bring Pippy existing source to a state consistent with the design above:

Partial list of changes to bring Pippy existing source to a state consistent with the design above:

*remove the examples tree widget from the main screen, provide it only as an "open an example bundle" function,

*remove the examples tree widget from the main screen, provide it only as an "open an example bundle" function, this will permit the GtkSourceView widget to be full screen width,

*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, this will permit the GtkSourceView widget to be nearly the full height available,

*provide multiple text entry widgets, once for each file in each module,

*provide multiple GtkSourceView widgets, once for each file in each module, within gtk.Notebook within gtk.Notebook,

**the outermost tabs will be module names,

**the outermost tabs will be module names,

**the innermost tabs will be file names within each module.

**the innermost tabs will be file names within each module,

*enlarge the program text entry widgets to be nearly full screen width,

*on toolbar save button, save all modules and files in a journal entry,

*on toolbar save button, save all modules and files in a journal entry,

*when a module is selected, provide an export button that creates a sugar journal entry for a distutils source distribution of the package, for sharing,

*when a module is selected, provide an export button that creates a sugar journal entry for a distutils source distribution package, for sharing,

*provide a way to import zip bundles from journal into the current pippy instance, using the object chooser, successful import will add to the modules displayed,

*provide a way to import pure python module or distutils source distribution package from journal into the current Pippy instance, using the object chooser, successful import will add to the modules displayed,

*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 module, allow import of all other currently displayed modules, modules included with Pippy (such as the existing pippy module), and system modules,

=== Alternative ===

=== Alternative ===