Features/TableView Widget: Difference between revisions

(21 intermediate revisions by 3 users not shown)

Line 1:

<noinclude>{{TOCright}}

[[Category:Feature ~~Page Incomplete~~]]

[[Category:Feature Accepted 0.88]]

[[Category:~~Feature~~|~~<Feature Name>~~]]

[[Category:FeatureObsoleted|TableView Widget]]

</noinclude>

== Summary ==

~~''A sentence or two summarizing what this feature is and what it will do~~. ~~This information is used for the overall feature summary page for each release~~.''

GTK widget to replace gtk.TreeView in Journal.

== Owner ==

~~''This should link to your home wiki page so we know who you are''~~

* Name: [[User:AcountName| Your Name]]

~~''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''~~

* Name: [[User:alsroot| Aleksey Lim]]

* Email: ~~<your~~ email ~~address so we can contact you, invite you to meetings, etc.>~~

* Email: [[Special:Emailuser/alsroot|send an email]]

== Current status ==

* Targeted release: ~~(SUGAR_VERSION)~~

* Targeted release: 0.88

* Last updated: ~~(DATE)~~

* Last updated: Mon Jan 11 21:15:02 UTC 2010

* Percentage of completion: XX%

* Percentage of completion: 90%

== Detailed Description ==

''~~Expand on the summary, if appropriate~~. ~~A couple of sentences suffices to explain the goal, but the more details you can provide the better~~.''

Feature introduced two new classes - SmoothTable and TableView.

=== SmoothTable class ===

Model less implementation. The real widget consists of ''visible-columns'' * (''visible-rows'' + 2) identical widgets (constructor is passed to SmoothTable during creation) and while scrolling (by pixel); SmoothTable shifts these widgets.

=== TableView class ===

Just adds gtk.TreeModel support.

== Benefit to Sugar ==

''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

''~~Make sure~~ to ~~note here as well if this feature has been requested by a specific deployment~~, ~~or if it has emerged from a bug report~~.''

Standard gtk components are not designed to be lazy. Third party widgets, I managed to find, uses scheme with renders (like gtk components), introduced component uses widgets instead (could have performance penalties, I guess, in common case but we don't have many rows in Journal view, so should be ok for us).

Benefits we have for such scheme:

* coding cells is more useful by using widgets than renders, we can reuse our existing custom widgets instead of coding sugarized cell renders

* in some cases it's hard to sugarize cells theme (we still have ugly progress bar for Journal entries), with new widget, we use just gtk.ProgressBar

== Scope ==

~~''What work do the developers have to accomplish to complete the feature in time~~ for ~~release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''~~

* new widget for [http://git.sugarlabs.org/projects/sugar-toolkit/repos/tableview sugar-toolkit]

==UI Design==

~~''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions~~.''

Nothing.

== How To Test ==

{{:{{PAGENAME}}/Testing}}

== User Experience ==

~~''If this feature is noticeable by its target audience, how~~ will ~~their experiences change as a result? Describe what they will see or notice~~.''

Nothing will be changed in case of user experience.

== Dependencies ==

''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

* regular glucose dependencies

== Contingency Plan ==

~~''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "~~None necessary, revert to previous release behaviour.~~" Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''~~

None necessary, revert to previous release behaviour.

== Documentation ==

@@ Line 1: / Line 1: @@
 <noinclude>{{TOCright}}
-[[Category:Feature Page Incomplete]]
+[[Category:Feature Accepted 0.88]]
-[[Category:Feature|<Feature Name>]]
+[[Category:FeatureObsoleted|TableView Widget]]
 </noinclude>
 == Summary ==
-''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''
+GTK widget to replace gtk.TreeView in Journal.
 == Owner ==
-''This should link to your home wiki page so we know who you are''
-* Name: [[User:AcountName| Your Name]]
-''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
+* Name: [[User:alsroot| Aleksey Lim]]
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Email: [[Special:Emailuser/alsroot|send an email]]
 == Current status ==
-* Targeted release: (SUGAR_VERSION)
+* Targeted release: 0.88
-* Last updated: (DATE)
+* Last updated: Mon Jan 11 21:15:02 UTC 2010
-* Percentage of completion: XX%
+* Percentage of completion: 90%
 == Detailed Description ==
-''Expand on the summary, if appropriate.  A couple of sentences suffices to explain the goal, but the more details you can provide the better.''
+Feature introduced two new classes - SmoothTable and TableView.
+=== SmoothTable class ===
+Model less implementation. The real widget consists of ''visible-columns'' * (''visible-rows'' + 2) identical widgets (constructor is passed to SmoothTable during creation) and while scrolling (by pixel); SmoothTable shifts these widgets.
+=== TableView class ===
+Just adds gtk.TreeModel support.
 == Benefit to Sugar ==
-''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
-''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''
+Standard gtk components are not designed to be lazy. Third party widgets, I managed to find, uses scheme with renders (like gtk components), introduced component uses widgets instead (could have performance penalties, I guess, in common case but we don't have many rows in Journal view, so should be ok for us).
+Benefits we have for such scheme:
+* coding cells is more useful by using widgets than renders, we can reuse our existing custom widgets instead of coding sugarized cell renders
+* in some cases it's hard to sugarize cells theme (we still have ugly progress bar for Journal entries), with new widget, we use just gtk.ProgressBar
 == Scope ==
-''What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''
+* new widget for [http://git.sugarlabs.org/projects/sugar-toolkit/repos/tableview sugar-toolkit]
 ==UI Design==
-''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''
+Nothing.
 == How To Test ==
 {{:{{PAGENAME}}/Testing}}
 == User Experience ==
-''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
+Nothing will be changed in case of user experience.
 == Dependencies ==
-''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
+* regular glucose dependencies
 == Contingency Plan ==
-''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''
+None necessary, revert to previous release behaviour.
 == Documentation ==