Sugar Labs

Features/GTK3/Desktop Summit activities: Difference between revisions

← Older edit
No edit summary
Rgs (talk | contribs)
39 edits
 
(3 intermediate revisions by 3 users not shown)
Line 12: Line 12:
# Launch sugar-jhbuild under F15, and launch Terminal
# Launch sugar-jhbuild under F15, and launch Terminal
# Write a little "hello world" PyGI standalone app (not activity) that has (say) a GtkButton and a GtkEntry.
# Write a little "hello world" PyGI standalone app (not activity) that has (say) a GtkButton and a GtkEntry.
# Launch that app. Since it uses PyGI/GTK3, we expect it to not pick up the Sugar theme.
# Launch that app from the Terminal activity. Since it uses PyGI/GTK3, we expect it to not pick up the Sugar theme.
# See what can be done to start getting the theme working, applied to that application.
# See what can be done to start getting the theme working, applied to that application.


Line 20: Line 20:


Some of this work is invasive and involves API changes and breaks activities like Chat, but if there are any self-contained changes, could they be upstreamed for 0.94? Particularly in sugar-toolkit. This would help decrease the complexity of the task.
Some of this work is invasive and involves API changes and breaks activities like Chat, but if there are any self-contained changes, could they be upstreamed for 0.94? Particularly in sugar-toolkit. This would help decrease the complexity of the task.
Repos:
[http://git.collabora.com/git/user/rgs/sugar Raul's Sugar repo]
[http://git.sugarlabs.org/~walter/sugar/no-hippo-sugar Walter's Sugar repo]
[http://git.sugarlabs.org/~walter/sugar/no-hippo-toolkit Walter's Sugar Toolkit repo]


=== Initial PyGI experiment ===
=== Initial PyGI experiment ===
Retrieved from "https://wiki.sugarlabs.org/go/Features/GTK3/Desktop_Summit_activities"