DialogReplacement - Revision history

BryceHarrington at 18:46, 8 November 2006

BryceHarrington — Wed, 08 Nov 2006 18:46:31 GMT

← Older revision		Revision as of 18:46, 8 November 2006
Line 12:		Line 12:

	And... instead of a dialog holding a single item, a notebook could hold several panels in different tabs.		And... instead of a dialog holding a single item, a notebook could hold several panels in different tabs.

			[[Category:Wiki Attic]]

Conversion script: link fix

Conversion script — Sun, 22 Jan 2006 02:32:54 GMT

link fix

← Older revision		Revision as of 02:32, 22 January 2006
Line 6:		Line 6:


	Basically, instead of subclassing Dialog, we'd subclass panel instead. We'd have a class that keeps track of the control panels, and is in charge of viewing them. When you'd want the FillAndStroke control panel, for example, the manager would check to see if an instance is around. If not, it would create the panel and then plop it in the proper container. By default that could be the dumb Dialog class that only holds things, however it could easily put it in a different part of the UI. Swatches, for example, could go in a panel in the bottom of the window instead of popping up in a dialog, etc.		Basically, instead of subclassing Dialog, we'd subclass panel instead. We'd have a class that keeps track of the control panels, and is in charge of viewing them. When you'd want the [[FillAndStroke]] control panel, for example, the manager would check to see if an instance is around. If not, it would create the panel and then plop it in the proper container. By default that could be the dumb Dialog class that only holds things, however it could easily put it in a different part of the UI. Swatches, for example, could go in a panel in the bottom of the window instead of popping up in a dialog, etc.


	Panel implements the 'Dockable' interface. Anything that might hold one would implement the 'DockFillable' interface.		Panel implements the 'Dockable' interface. Anything that might hold one would implement the '[[DockFillable]]' interface.

	And... instead of a dialog holding a single item, a notebook could hold several panels in different tabs.		And... instead of a dialog holding a single item, a notebook could hold several panels in different tabs.

JonCruz: *

JonCruz — Thu, 07 Apr 2005 04:27:03 GMT

← Older revision		Revision as of 04:27, 7 April 2005
Line 3:		Line 3:
	Here's a rough plan		Here's a rough plan

	upload:Panels.png		<center>upload:Panels.png</center>


			Basically, instead of subclassing Dialog, we'd subclass panel instead. We'd have a class that keeps track of the control panels, and is in charge of viewing them. When you'd want the FillAndStroke control panel, for example, the manager would check to see if an instance is around. If not, it would create the panel and then plop it in the proper container. By default that could be the dumb Dialog class that only holds things, however it could easily put it in a different part of the UI. Swatches, for example, could go in a panel in the bottom of the window instead of popping up in a dialog, etc.


			Panel implements the 'Dockable' interface. Anything that might hold one would implement the 'DockFillable' interface.

			And... instead of a dialog holding a single item, a notebook could hold several panels in different tabs.

JonCruz: *

JonCruz — Thu, 07 Apr 2005 04:07:19 GMT

← Older revision		Revision as of 04:07, 7 April 2005
Line 1:		Line 1:
	Starting a bit of scratch-pad for the new way of getting away from subclassing Dialog		Starting a bit of scratch-pad for the new way of getting away from subclassing Dialog

	[upload:Panels.png]		Here's a rough plan

			upload:Panels.png

JonCruz: initial diagram

JonCruz — Thu, 07 Apr 2005 04:04:34 GMT

initial diagram

New page

Starting a bit of scratch-pad for the new way of getting away from subclassing Dialog

[upload:Panels.png]