[Sugar-devel] [PATCH] GtkLabel: make the background transparent
From: Simon Schampijer si...@laptop.org
The GtkLabel does respect background css properties now [1][2]. Drawing
them transparent by default gives us the same behavior us before.
Signed-off-by: Simon Schampijer si...@laptop.org
[1]
http://git.gnome.org/browse/gtk+/commit/?id=03bf85ba07f455a92283a3030fb8441b776b7e38
[2] https://bugzilla.gnome.org/show_bug.cgi?id=670743
---
gtk3/theme/gtk-widgets.css.em | 4
1 file changed, 4 insertions(+)
diff --git a/gtk3/theme/gtk-widgets.css.em b/gtk3/theme/gtk-widgets.css.em
index 5549970..96aa3fa 100644
--- a/gtk3/theme/gtk-widgets.css.em
+++ b/gtk3/theme/gtk-widgets.css.em
@@ -138,6 +138,10 @@ icon_large = icon_base * 5
color: @black;
}
+GtkLabel, GtkLabel:insensitive {
+background-color: transparent;
+}
+
/* Handle this differently? */
.window *:insensitive {
background-color: @panel_grey;
--
1.7.11.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] GtkLabel: make the background transparent
Yes I've seen we need this, I have a patched artwork in the shell
port with it. Please push.
2012/8/29 Simon Schampijer si...@schampijer.de:
From: Simon Schampijer si...@laptop.org
The GtkLabel does respect background css properties now [1][2]. Drawing
them transparent by default gives us the same behavior us before.
Signed-off-by: Simon Schampijer si...@laptop.org
[1]
http://git.gnome.org/browse/gtk+/commit/?id=03bf85ba07f455a92283a3030fb8441b776b7e38
[2] https://bugzilla.gnome.org/show_bug.cgi?id=670743
---
gtk3/theme/gtk-widgets.css.em | 4
1 file changed, 4 insertions(+)
diff --git a/gtk3/theme/gtk-widgets.css.em b/gtk3/theme/gtk-widgets.css.em
index 5549970..96aa3fa 100644
--- a/gtk3/theme/gtk-widgets.css.em
+++ b/gtk3/theme/gtk-widgets.css.em
@@ -138,6 +138,10 @@ icon_large = icon_base * 5
color: @black;
}
+GtkLabel, GtkLabel:insensitive {
+background-color: transparent;
+}
+
/* Handle this differently? */
.window *:insensitive {
background-color: @panel_grey;
--
1.7.11.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Views: search behavior (was Re: [PATCH sugar] Views: move the ViewToolbar to the HomeWindow instead of having one in each View)
On 08/28/2012 05:53 PM, Gary Martin wrote:
Hi Simon,
On 28 Aug 2012, at 14:12, Simon Schampijer si...@schampijer.de wrote:
On 08/28/2012 02:14 PM, Manuel Quiñones wrote:
So now the filtering is shared between the three views. I think this
is worth noting in the commit message.
Thanks for the review and catching this! I did note it in the commit message
before pushing.
Gary, we did discuss the following:
There seem to be three options how the search now that we have a search entry
in each view could work:
- if you did a search in View A and then switch to View B the entry will be
cleared leaving you with no search applied in B
- if you did a search in View A and then switch to View B the search from A
will be applied to B (behavior which landed in 0.97.2)
- if you did a search in View A and then switch to View B the search from A
will not be applied in B, if you switch back to A the search you did before in
A has been cached and is still applied (behavior before 0.97.2)
Thanks for raising this change! I'll need to give it some more though and test
the patches.
My gut reaction so far would be for the clearing behaviour,
You can use the attached patch to test that behavior. I think I like
that behavior as well. Preferred over caching, as you say it may lead to
unexpected behaviors.
second choice would be the caching behaviour. My reasons against the
0.97.2 behaviour change would be that different views contain dissimilar
enough objects that a search in one is not often useful in another (e.g.
searching for a buddy or access point, and switching to home), and that
will drop the user in an unexpected UI state. A reason for clearing the
search when switching views is that it prevents issues for novice users
who leave a query in place unintentionally, and return to find a view in
an unexpected state without realising they need to clear the old search
query manually. Though so far, caching previous search queries in a view
is just what we've been doing in the shell. FWIW: home list view is the
worst offender as it shows a blank white canvas when a query has no
matches, should really behave like the Journal with the 'No matching
entries' UI. The 0.97.2 change may well lead to an increase in my icons
are all grey/gone type support reports, especially from young users who
may randomly press keys and generate a shel query without realising it.
Thanks Gary, good catch about the needed feedback in the list view,
filed as [1] (feel free to add there wordings/icon to use etc). Once the
shell port is done, it should be straight forward to add.
Btw, re Activity list view. We said at one point that the date displayed
in the list has not much meaning (at least at the moment). Did we have
an idea for a replacement?
Thanks,
Simon
[1] http://bugs.sugarlabs.org/ticket/3838
diff --git a/src/jarabe/desktop/homewindow.py b/src/jarabe/desktop/homewindow.py
index c4f1401..840f19c 100644
--- a/src/jarabe/desktop/homewindow.py
+++ b/src/jarabe/desktop/homewindow.py
@@ -192,16 +192,19 @@ class HomeWindow(gtk.Window):
if level == ShellModel.ZOOM_HOME:
self._box.pack_start(self._home_box)
self._home_box.show()
+self._toolbar.search_entry.set_text('')
self._toolbar.search_entry.grab_focus()
self._toolbar.show_view_buttons()
elif level == ShellModel.ZOOM_GROUP:
self._box.pack_start(self._group_box)
self._group_box.show()
+self._toolbar.search_entry.set_text('')
self._toolbar.search_entry.grab_focus()
self._toolbar.hide_view_buttons()
elif level == ShellModel.ZOOM_MESH:
self._box.pack_start(self._mesh_box)
self._mesh_box.show()
+self._toolbar.search_entry.set_text('')
self._toolbar.search_entry.grab_focus()
self._toolbar.hide_view_buttons()
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity sandbox
On 2012-08-28, at 15:53, Gonzalo Odiard gonz...@laptop.org wrote: On Tue, Aug 28, 2012 at 10:49 AM, blekros sugar blekros.su...@gmail.com wrote: I'd like to use Eclipse with PyDev on Windows to try to build activities. Has the Sugar shell been ported to Windows (x86) or Android or iOS or as a chrome / firefox plugin so that I can use my existing environments without VMWare or VirtualBox? No. Sugar run in a linux os. Right. Sugar activities do not only require the Sugar Shell to run. They are full-fledged Linux applications that follow a few additional conventions to function well in Sugar. But that means that they need a full Linux + X11 operating system stack to work. I can't find anything resembling an object model, or class diagram that shows the architectural breakdown of Sugar. Where to look? Sadly, our documentation is not in a good shape. Today, the best doc is the code itself. Well, there still is *some* documentation for activity authors. We have a nice book: http://en.flossmanuals.net/make-your-own-sugar-activities/ And for a more low-level understanding there is this documentation page: http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API More documentation resources are listed at http://wiki.sugarlabs.org/go/Activity_Team/Resources - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Views: search behavior (was Re: [PATCH sugar] Views: move the ViewToolbar to the HomeWindow instead of having one in each View)
Btw, re Activity list view. We said at one point that the date displayed in the list has not much meaning (at least at the moment). Did we have an idea for a replacement? +1 I know is not a trivial change, but IMHO, would be great have a short description here. We can add it in the activity.info file, and get it translated as the activity name today. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Views: search behavior (was Re: [PATCH sugar] Views: move the ViewToolbar to the HomeWindow instead of having one in each View)
Hi Gonzalo, On 29 Aug 2012, at 13:51, Gonzalo Odiard gonz...@laptop.org wrote: Btw, re Activity list view. We said at one point that the date displayed in the list has not much meaning (at least at the moment). Did we have an idea for a replacement? +1 I know is not a trivial change, but IMHO, would be great have a short description here. We can add it in the activity.info file, and get it translated as the activity name today. +1 FWIW I'm sure I saw this working in an alpha build once (I remember being surprised when I looked in list view, just a few activities had text extra minimal descriptions showing). I don't remember who was responsible but I did have a little dig and found the below existing strings in some activity.info files: Garys-Computer:All Activities archive gary$ grep -r summary */activity/activity.info CartoonBuilder.activity/activity/activity.info:summary = Make a cartoon by creating a sequence of poses inside a filmstrip Chat.activity/activity/activity.info:summary = Text chat FlipSticks.activity/activity/activity.info:summary = Using keyframes, program a stick figure to twist and dance ImageViewer.activity/activity/activity.info:summary = The Image Viewer activity is a simple and fast image viewer tool Speak.activity/activity/activity.info:summary = An animated face that speaks whatever you type TamTamEdit.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamJam.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamMini.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamSynthLab.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TuxPaint.activity/activity/activity.info:summary = Drawing program designed for young children Perhaps we could officially adopt the summary keyword if we go this route? I put together a quick mockup [1] using some of the above strings and close to the descriptions as found on ASLO to give an idea for what type of strings misc developers would probably fill this with. Note that an ellipsis ... is used for clipping overly long strings. We would want to provide a style guide for that text, so it is a short, friendly, and as succinct as possible (i.e. say what it does, or what you can do with it in less than 7-10 words). Regards, --Gary [1] http://wiki.sugarlabs.org/go/File:Home_list_view_comment_summary_mockup.png Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity sandbox
Thanks, I'll check out the documentation and get up to speed a little more. Meantime -- I just want to make sure I understand: 1. Sugar activities *are* Python scripts -- but they use Linux-specific packages, instead of using os.* or sys.* packages, which wrap the OS that lies beneath. Same for GTK+. The GUI cannot be made to use ported versions of the GTK+ API. 2. The Sugar shell is not a service layer between the bare metal Linux OS and Sugar presentation (its desktop) . In other words, the shell cannot be updated to plug into to modern device OSes such as I/Pad or Android. 3. No one has attempted to port Activities, i.e. the FUN stuff, to Browser apps (HTML 5 + Javascript) so any kid with a smart phone could play with, say, Physics, or Turtle. Brad On Wed, Aug 29, 2012 at 7:15 AM, Bert Freudenberg b...@freudenbergs.dewrote: On 2012-08-28, at 15:53, Gonzalo Odiard gonz...@laptop.org wrote: On Tue, Aug 28, 2012 at 10:49 AM, blekros sugar blekros.su...@gmail.com wrote: I'd like to use Eclipse with PyDev on Windows to try to build activities. Has the Sugar shell been ported to Windows (x86) or Android or iOS or as a chrome / firefox plugin so that I can use my existing environments without VMWare or VirtualBox? No. Sugar run in a linux os. Right. Sugar activities do not only require the Sugar Shell to run. They are full-fledged Linux applications that follow a few additional conventions to function well in Sugar. But that means that they need a full Linux + X11 operating system stack to work. I can't find anything resembling an object model, or class diagram that shows the architectural breakdown of Sugar. Where to look? Sadly, our documentation is not in a good shape. Today, the best doc is the code itself. Well, there still is *some* documentation for activity authors. We have a nice book: http://en.flossmanuals.net/make-your-own-sugar-activities/ And for a more low-level understanding there is this documentation page: http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API More documentation resources are listed at http://wiki.sugarlabs.org/go/Activity_Team/Resources - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity sandbox
On Wed, Aug 29, 2012 at 12:01 PM, blekros sugar blekros.su...@gmail.comwrote: Thanks, I'll check out the documentation and get up to speed a little more. Meantime -- I just want to make sure I understand: 1. Sugar activities *are* Python scripts -- but they use Linux-specific packages, instead of using os.* or sys.* packages, which wrap the OS that lies beneath. Same for GTK+. The GUI cannot be made to use ported versions of the GTK+ API. Are python scripts, but use a few python specific stuff, like dbus, and sugar specific services, like the journal or the collaboration stuff. 2. The Sugar shell is not a service layer between the bare metal Linux OS and Sugar presentation (its desktop) . In other words, the shell cannot be updated to plug into to modern device OSes such as I/Pad or Android. The Sugar shell is a service layer. Can be ported, but is not a trivial task. And maintain a more abstract service layer will add cost, that is the reason was not done. 3. No one has attempted to port Activities, i.e. the FUN stuff, to Browser apps (HTML 5 + Javascript) so any kid with a smart phone could play with, say, Physics, or Turtle. Porting from python to html + javascript, is like... start again from zero :) You can do it, of course. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity sandbox
On 2012-08-29, at 17:01, blekros sugar blekros.su...@gmail.com wrote: Thanks, I'll check out the documentation and get up to speed a little more. Meantime -- I just want to make sure I understand: 1. Sugar activities *are* Python scripts ... usually. Any programming language is fine for writing Sugar activities, as long as it can connect to D-Bus and provide an X11 user interface. But writing them in Python is a lot simpler because you can make use of the Sugar Toolkit (a Python library used by. One example of an activity not written in Python is Etoys. -- but they use Linux-specific packages, instead of using os.* or sys.* packages, which wrap the OS that lies beneath. Same for GTK+. The GUI cannot be made to use ported versions of the GTK+ API. That's pretty much correct. At least no-one has seriously tried to make Sugar work elsewhere. 2. The Sugar shell is not a service layer between the bare metal Linux OS and Sugar presentation (its desktop) . In other words, the shell cannot be updated to plug into to modern device OSes such as I/Pad or Android. Well porting the shell is maybe not that hard, but that wouldn't mean the activities simply work, too. That's because activities are not coded purely against the Sugar API but may make use of stuff more generally available in Linux. OTOH some simple activities might just work. 3. No one has attempted to port Activities, i.e. the FUN stuff, to Browser apps (HTML 5 + Javascript) so any kid with a smart phone could play with, say, Physics, or Turtle. It wouldn't be so much porting as reimplementing. Also you would need a framework for collaboration and journaling first (which is what distinguishes Sugar most from other environments). Individual activities aren't all that interesting IMHO, equivalent apps can be found for pretty much any platform. The way activities are assembled into a whole learning environment is Sugar's raison d'etre. - Bert - Brad On Wed, Aug 29, 2012 at 7:15 AM, Bert Freudenberg b...@freudenbergs.de wrote: On 2012-08-28, at 15:53, Gonzalo Odiard gonz...@laptop.org wrote: On Tue, Aug 28, 2012 at 10:49 AM, blekros sugar blekros.su...@gmail.com wrote: I'd like to use Eclipse with PyDev on Windows to try to build activities. Has the Sugar shell been ported to Windows (x86) or Android or iOS or as a chrome / firefox plugin so that I can use my existing environments without VMWare or VirtualBox? No. Sugar run in a linux os. Right. Sugar activities do not only require the Sugar Shell to run. They are full-fledged Linux applications that follow a few additional conventions to function well in Sugar. But that means that they need a full Linux + X11 operating system stack to work. I can't find anything resembling an object model, or class diagram that shows the architectural breakdown of Sugar. Where to look? Sadly, our documentation is not in a good shape. Today, the best doc is the code itself. Well, there still is *some* documentation for activity authors. We have a nice book: http://en.flossmanuals.net/make-your-own-sugar-activities/ And for a more low-level understanding there is this documentation page: http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API More documentation resources are listed at http://wiki.sugarlabs.org/go/Activity_Team/Resources - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity sandbox
On Tue, August 28, 2012 9:49 am, blekros sugar wrote: I'd like to use Eclipse with PyDev on Windows to try to build activities. There are Free Software Python IDEs such as Idle for Linux. Have you looked at them? Has the Sugar shell been ported to Windows (x86) or Android or iOS or as a chrome / firefox plugin so that I can use my existing environments without VMWare or VirtualBox? Sugar has not been ported to Windows for fundamental reasons. http://wiki.laptop.org/go/Controversies#Porting_Sugar_to_Windows I can't find anything resembling an object model, or class diagram that shows the architectural breakdown of Sugar. Where to look? I have not seen anything in those forms. This is what I am aware of. http://wiki.laptop.org/go/Sugar_Architecture Thanks, Brad ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Edward Mokurai (默雷/निशब्दगर्ज/نشبدگرج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://wiki.sugarlabs.org/go/Replacing_Textbooks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Views: search behavior (was Re: [PATCH sugar] Views: move the ViewToolbar to the HomeWindow instead of having one in each View)
I am pretty sure Aleksey knows who was involved :) There are more info here [1] and here [2] Solve the packaging issues (specially the dependencies required) is another different beast, but we can add the following without problem: summary (will be translated) license homepage And at the risk of starting a never ending thread, I propose: authors (we see the need of recognition to the work volunteers do) repository (will enable improve development process in the future) Right now, this information will not be visible, but in the future, we can add a tab in the show source window, or find another place to show it. Should be good agree at least in the proposed info, and start to add to the activities, if not is ever a chicken and egg problem, do not add the info because is not useful, and not show the info because is not available... Gonzalo [1] http://wiki.sugarlabs.org/go/Platform_Team/Guide/Sweets_Packaging [2] http://wiki.sugarlabs.org/go/Features/Feature_ActivityInfo On Wed, Aug 29, 2012 at 11:45 AM, Gary Martin garycmar...@googlemail.comwrote: Hi Gonzalo, On 29 Aug 2012, at 13:51, Gonzalo Odiard gonz...@laptop.org wrote: Btw, re Activity list view. We said at one point that the date displayed in the list has not much meaning (at least at the moment). Did we have an idea for a replacement? +1 I know is not a trivial change, but IMHO, would be great have a short description here. We can add it in the activity.info file, and get it translated as the activity name today. +1 FWIW I'm sure I saw this working in an alpha build once (I remember being surprised when I looked in list view, just a few activities had text extra minimal descriptions showing). I don't remember who was responsible but I did have a little dig and found the below existing strings in some activity.info files: Garys-Computer:All Activities archive gary$ grep -r summary */activity/ activity.info CartoonBuilder.activity/activity/activity.info:summary = Make a cartoon by creating a sequence of poses inside a filmstrip Chat.activity/activity/activity.info:summary = Text chat FlipSticks.activity/activity/activity.info:summary = Using keyframes, program a stick figure to twist and dance ImageViewer.activity/activity/activity.info:summary = The Image Viewer activity is a simple and fast image viewer tool Speak.activity/activity/activity.info:summary = An animated face that speaks whatever you type TamTamEdit.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamJam.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamMini.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamSynthLab.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TuxPaint.activity/activity/activity.info:summary = Drawing program designed for young children Perhaps we could officially adopt the summary keyword if we go this route? I put together a quick mockup [1] using some of the above strings and close to the descriptions as found on ASLO to give an idea for what type of strings misc developers would probably fill this with. Note that an ellipsis ... is used for clipping overly long strings. We would want to provide a style guide for that text, so it is a short, friendly, and as succinct as possible (i.e. say what it does, or what you can do with it in less than 7-10 words). Regards, --Gary [1] http://wiki.sugarlabs.org/go/File:Home_list_view_comment_summary_mockup.png Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] activity sandbox
On 28 Aug 2012, at 14:49, blekros sugar blekros.su...@gmail.com wrote: I'd like to use Eclipse with PyDev on Windows to try to build activities. Has the Sugar shell been ported to Windows (x86) or Android or iOS or as a chrome / firefox plugin so that I can use my existing environments without VMWare or VirtualBox? I can't find anything resembling an object model, or class diagram that shows the architectural breakdown of Sugar. Where to look? Here's another couple places [1] [2], to start at, though they don't go into great depth and are somewhat dated now. I also had a quick, somewhat gaudy, stab at this some years back [3] but it doesn't add much useful vs. the ascii art: Regards, --Gary [1] http://wiki.sugarlabs.org/go/Sugar_System_Stack [2] http://wiki.sugarlabs.org/go/Development_Team/Architecture [3] http://youtu.be/xVV_OnBS6O4 Thanks, Brad ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Views: search behavior (was Re: [PATCH sugar] Views: move the ViewToolbar to the HomeWindow instead of having one in each View)
On 29 Aug 2012, at 18:19, Gonzalo Odiard gonz...@laptop.org wrote: I am pretty sure Aleksey knows who was involved :) There are more info here [1] and here [2] Solve the packaging issues (specially the dependencies required) is another different beast, but we can add the following without problem: summary (will be translated) license homepage And at the risk of starting a never ending thread, I propose: authors (we see the need of recognition to the work volunteers do) repository (will enable improve development process in the future) Right now, this information will not be visible, but in the future, we can add a tab in the show source window, or find another place to show it. Should be good agree at least in the proposed info, and start to add to the activities, if not is ever a chicken and egg problem, do not add the info because is not useful, and not show the info because is not available... Hmmm... You really want others now as well? Not busy enough ;) Summary is the one I'd focus on if we are moving forward with this and show them in the list view. If there is no direct exposure/need the rest will all just bit rot and go stale, like much of the rest of the 'standard' activity file spam that tries to have much of the same information repeated yet again – HACKING, AUTHORS, NEWS, README, TODO – I gave up looking, changing them some time back. Regards, --Gary Gonzalo [1] http://wiki.sugarlabs.org/go/Platform_Team/Guide/Sweets_Packaging [2] http://wiki.sugarlabs.org/go/Features/Feature_ActivityInfo On Wed, Aug 29, 2012 at 11:45 AM, Gary Martin garycmar...@googlemail.com wrote: Hi Gonzalo, On 29 Aug 2012, at 13:51, Gonzalo Odiard gonz...@laptop.org wrote: Btw, re Activity list view. We said at one point that the date displayed in the list has not much meaning (at least at the moment). Did we have an idea for a replacement? +1 I know is not a trivial change, but IMHO, would be great have a short description here. We can add it in the activity.info file, and get it translated as the activity name today. +1 FWIW I'm sure I saw this working in an alpha build once (I remember being surprised when I looked in list view, just a few activities had text extra minimal descriptions showing). I don't remember who was responsible but I did have a little dig and found the below existing strings in some activity.info files: Garys-Computer:All Activities archive gary$ grep -r summary */activity/activity.info CartoonBuilder.activity/activity/activity.info:summary = Make a cartoon by creating a sequence of poses inside a filmstrip Chat.activity/activity/activity.info:summary = Text chat FlipSticks.activity/activity/activity.info:summary = Using keyframes, program a stick figure to twist and dance ImageViewer.activity/activity/activity.info:summary = The Image Viewer activity is a simple and fast image viewer tool Speak.activity/activity/activity.info:summary = An animated face that speaks whatever you type TamTamEdit.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamJam.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamMini.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TamTamSynthLab.activity/activity/activity.info:summary = A music and sound exploration application for Sugar TuxPaint.activity/activity/activity.info:summary = Drawing program designed for young children Perhaps we could officially adopt the summary keyword if we go this route? I put together a quick mockup [1] using some of the above strings and close to the descriptions as found on ASLO to give an idea for what type of strings misc developers would probably fill this with. Note that an ellipsis ... is used for clipping overly long strings. We would want to provide a style guide for that text, so it is a short, friendly, and as succinct as possible (i.e. say what it does, or what you can do with it in less than 7-10 words). Regards, --Gary [1] http://wiki.sugarlabs.org/go/File:Home_list_view_comment_summary_mockup.png Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Views: search behavior (was Re: [PATCH sugar] Views: move the ViewToolbar to the HomeWindow instead of having one in each View)
Hi Simon, On 29 Aug 2012, at 12:41, Simon Schampijer si...@schampijer.de wrote: On 08/28/2012 05:53 PM, Gary Martin wrote: Hi Simon, On 28 Aug 2012, at 14:12, Simon Schampijer si...@schampijer.de wrote: On 08/28/2012 02:14 PM, Manuel Quiñones wrote: So now the filtering is shared between the three views. I think this is worth noting in the commit message. Thanks for the review and catching this! I did note it in the commit message before pushing. Gary, we did discuss the following: There seem to be three options how the search now that we have a search entry in each view could work: - if you did a search in View A and then switch to View B the entry will be cleared leaving you with no search applied in B - if you did a search in View A and then switch to View B the search from A will be applied to B (behavior which landed in 0.97.2) - if you did a search in View A and then switch to View B the search from A will not be applied in B, if you switch back to A the search you did before in A has been cached and is still applied (behavior before 0.97.2) Thanks for raising this change! I'll need to give it some more though and test the patches. My gut reaction so far would be for the clearing behaviour, You can use the attached patch to test that behavior. I think I like that behavior as well. Preferred over caching, as you say it may lead to unexpected behaviors. second choice would be the caching behaviour. My reasons against the 0.97.2 behaviour change would be that different views contain dissimilar enough objects that a search in one is not often useful in another (e.g. searching for a buddy or access point, and switching to home), and that will drop the user in an unexpected UI state. A reason for clearing the search when switching views is that it prevents issues for novice users who leave a query in place unintentionally, and return to find a view in an unexpected state without realising they need to clear the old search query manually. Though so far, caching previous search queries in a view is just what we've been doing in the shell. FWIW: home list view is the worst offender as it shows a blank white canvas when a query has no matches, should really behave like the Journal with the 'No matching entries' UI. The 0.97.2 change may well lead to an increase in my icons are all grey/gone type support reports, especially from young users who may randomly press keys and generate a shel query without realising it. Thanks Gary, good catch about the needed feedback in the list view, filed as [1] (feel free to add there wordings/icon to use etc). Once the shell port is done, it should be straight forward to add. Fab. Done. Have added a mockup screen shot and comment to the ticket. Regards, --Gary Btw, re Activity list view. We said at one point that the date displayed in the list has not much meaning (at least at the moment). Did we have an idea for a replacement? Thanks, Simon [1] http://bugs.sugarlabs.org/ticket/3838 view_toolbar_search_behavior.patch ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Design] Accelerometer icon
Hi Gonzalo, Some weeks back you requested an icon to represent an accelerometer, or accelerometer data. Can you give a little more context as to where you'd like to use this icon? I'm currently thinking you might possibly want it in the Memorize toolbar as a data source, in the Maze toolbar as an alternative controller, Walter might want it if he implements a Newtonian Turtles feature, and in the Physics toolbar as a way of enabling manual gravity control – OK so that last one was mine ;) Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Accelerometer icon
On Wed, Aug 29, 2012 at 8:42 PM, Gary C Martin garycmar...@googlemail.com wrote: Hi Gonzalo, Some weeks back you requested an icon to represent an accelerometer, or accelerometer data. Can you give a little more context as to where you'd like to use this icon? I'm currently thinking you might possibly want it in the Memorize toolbar as a data source, in the Maze toolbar as an alternative controller, Walter might want it if he implements a Newtonian Turtles feature, and in the Physics toolbar as a way of enabling manual gravity control – OK so that last one was mine ;) Regards, --Gary If Walter starts making turtles out of neutronium we're going to need that anti-grav control in Physics. I would imagine the XO robot warriors (multiple platforms and packages) would like to implement readings from the accelerometer as well. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Accelerometer icon
I was thinking in Maze and Physics. Probably used in a ToggleButton, to enable/disable the use of the accelerometer data. Gonzalo On Wed, Aug 29, 2012 at 9:42 PM, Gary C Martin garycmar...@googlemail.comwrote: Hi Gonzalo, Some weeks back you requested an icon to represent an accelerometer, or accelerometer data. Can you give a little more context as to where you'd like to use this icon? I'm currently thinking you might possibly want it in the Memorize toolbar as a data source, in the Maze toolbar as an alternative controller, Walter might want it if he implements a Newtonian Turtles feature, and in the Physics toolbar as a way of enabling manual gravity control – OK so that last one was mine ;) Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
