Difference between revisions of "Features/Toolbar utils"
(Created page with "<noinclude> Category:Feature Page Incomplete Toolbar utils </noinclude> == Summary == I use a collection of toolbar helper methods in all of my activiti...") |
|||
| Line 19: | Line 19: | ||
I use a collection of toolbar helper methods in all of my activities. It is proposed to make these utils part of the toolkit. It makes it easier for me both to manage the details of creating toolbar items and for managing the slight differences between primary and secondary toolbars. Also, since it is only in the utils that I directly reference the GTK classes, the conversion from GTK2 to GTK3 can be made essentially transparent to my activities from at least the toolbar perspective. And it makes my code much more compact (and arguably easier to read). | I use a collection of toolbar helper methods in all of my activities. It is proposed to make these utils part of the toolkit. It makes it easier for me both to manage the details of creating toolbar items and for managing the slight differences between primary and secondary toolbars. Also, since it is only in the utils that I directly reference the GTK classes, the conversion from GTK2 to GTK3 can be made essentially transparent to my activities from at least the toolbar perspective. And it makes my code much more compact (and arguably easier to read). | ||
| − | I am no programmer, so I would expect someone to have a better idea how to implement all of this, but that is exactly my point: by unburdening the activity developer from worrying about these repetitive details, we'll have a more robust, more easily maintained platform. | + | The last 10%: I am no programmer, so I would expect someone to have a better idea how to implement all of this, but that is exactly my point: by unburdening the activity developer from worrying about these repetitive details, we'll have a more robust, more easily maintained platform. |
See [http://git.sugarlabs.org/portfolio/portfolio/blobs/master/toolbar_utils.py] for the current version of the utilities. | See [http://git.sugarlabs.org/portfolio/portfolio/blobs/master/toolbar_utils.py] for the current version of the utilities. | ||
Latest revision as of 09:54, 18 November 2011
Summary
I use a collection of toolbar helper methods in all of my activities. It is proposed to make these utils part of the toolkit.
Owner
- Name: Walter Bender
- Email: Walter --AT-- sugarlabs.org
Current status
- Targeted release: 0.96
- Last updated:
- Percentage of completion: 90%
Detailed Description
I use a collection of toolbar helper methods in all of my activities. It is proposed to make these utils part of the toolkit. It makes it easier for me both to manage the details of creating toolbar items and for managing the slight differences between primary and secondary toolbars. Also, since it is only in the utils that I directly reference the GTK classes, the conversion from GTK2 to GTK3 can be made essentially transparent to my activities from at least the toolbar perspective. And it makes my code much more compact (and arguably easier to read).
The last 10%: I am no programmer, so I would expect someone to have a better idea how to implement all of this, but that is exactly my point: by unburdening the activity developer from worrying about these repetitive details, we'll have a more robust, more easily maintained platform.
See [1] for the current version of the utilities.
Benefit to Sugar
Anything we can do to make it easier to develop and maintain activities is of benefit to Sugar.
Scope
I have "factory" methods for buttons, radio buttons, separators, combos, entries, spinners, labels, and images.
UI Design
No impact
How To Test
Features/Toolbar utils/Testing
User Experience
No impact
Dependencies
Contingency Plan
None needed as there is no requirement to use these utilities.