User:Quozl - Revision history

Quozl at 02:17, 25 January 2025

2025-01-25T02:17:11Z

← Older revision		Revision as of 22:17, 24 January 2025
Line 1:		Line 1:
	== Pippy Design Idea 2011-03-10 ==		== Old - Pippy Design Idea 2011-03-10 ==

	=== Usage ===		=== Usage ===

Quozl: /* Changes */

2011-03-10T05:24:30Z

Changes

← Older revision		Revision as of 01:24, 10 March 2011
Line 107:		Line 107:
	*when a module is selected, provide an export button that creates a sugar journal entry for a distutils source distribution 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 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,		*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 module, allow import of all other currently displayed modules, modules included with Pippy (such as the existing pippy module), and system modules.		*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,
			*convert the examples to either pure python module or package form.

	=== Alternative ===		=== Alternative ===

Quozl: /* Changes */

2011-03-10T05:21:30Z

Changes

← Older revision		Revision as of 01:21, 10 March 2011
Line 100:		Line 100:
	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, this will permit the GtkSourceView widget to be full screen width,		*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 GtkSourceView 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,

Quozl: /* Changes */

2011-03-10T05:19:34Z

Changes

Quozl: /* Display - Editing */

2011-03-10T04:56:49Z

Display - Editing

← Older revision		Revision as of 00:56, 10 March 2011
Line 66:		Line 66:
	(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 "main", a gtk.Notebook (tab labels "__doc__", "file.py", "setup.py", "+")
			***notebook page label "__doc__", a GtkSourceView in read-only mode, hidden if __doc__ is empty,
			***notebook page label "file", a GtkSourceView for "file.py",
			***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 "test", a GtkSourceView for "test.py",
			***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 "+", creates a new module, prompts for module name.

			(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).

	=== Display - Running ===		=== Display - Running ===

Quozl at 04:39, 10 March 2011

2011-03-10T04:39:02Z

← Older revision		Revision as of 00:39, 10 March 2011
Line 29:		Line 29:
	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.
Line 40:		Line 40:
	*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.

Quozl at 04:29, 10 March 2011

2011-03-10T04:29:56Z

← Older revision		Revision as of 00:29, 10 March 2011
Line 57:		Line 57:
	*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,
Line 71:		Line 71:
	***GtkSourceView (one for each file in each module)		***GtkSourceView (one for each file in each module)

	=== ~~Process~~ ===		=== Display - Running ===
	When run is pressed, display will contain:		When run is pressed, display will contain:
	*toolbar,		*toolbar,

Quozl: /* Process */

2011-03-10T04:28:00Z

Process

← Older revision		Revision as of 00:28, 10 March 2011
Line 76:		Line 76:
	*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.

			Activity canvas GTK+ widget hierarchy:
			*gtk.Container
			**gtk.VBox
			***gtk.HBox
			****gtk.VScrollbar
			****vte.Terminal
			***gtk.Button Stop

	=== Changes ===		=== Changes ===

Quozl: /* Display */

2011-03-10T04:25:30Z

Display

← Older revision		Revision as of 00:25, 10 March 2011
Line 65:		Line 65:

	(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:
			*gtk.Notebook (for viewing and writing code, one page per module)
			**gtk.Notebook (one page per file in each module)
			***GtkSourceView (one for each file in each module)

	=== Process ===		=== Process ===

Quozl: /* Changes */

2011-03-10T03:52:33Z

Changes

← Older revision		Revision as of 23:52, 9 March 2011
Line 74:		Line 74:
	=== 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 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,
	*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,
	*~~enlarge the program~~ text entry ~~widget to be nearly full screen~~,		*provide multiple text entry widgets, once for each file in each module,
	*~~encapsulate~~ the ~~program text entry widget in~~ tabs ~~for files in a zip bundle~~,		**the outermost tabs will be module names,
	*~~encapsulate~~ the ~~bundle in~~ tabs ~~for zip bundles loaded into pippy instance~~,		**the innermost tabs will be file names within each module.
	*on ~~standard sugar~~ save, save all ~~zip bundles~~ and files in a ~~sugar~~ journal entry,		*enlarge the program text entry widgets to be nearly full screen width,
	*provide an export ~~zip bundle~~ button that creates a sugar journal entry of ~~type zip bundle~~, for sharing,		*on toolbar save button, save all modules and files in a journal entry,
	*provide a way to import zip bundles from journal into the current pippy instance, using the object chooser,		*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,
			*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,
	*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,

← Older revision		Revision as of 01:19, 10 March 2011
Line 99:		Line 99:
	=== 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,
	*provide multiple ~~text entry~~ widgets, once for each file in each module,		*provide multiple GtkSourceView widgets, once for each file in each module,
	**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 ===