[sugar] Clipboard Notification

[Tomeu Vizoso]

On Tue, Apr 15, 2008 at 5:08 AM, Eric Burns <ericjosephburns at gmail.com> wrote:
> While trying to create an instance of NotificationIcon() in the
> _object_added_cb function in clipboardtray.py I couldn't get the path to the
> icon from the ClipboardIcon() instance because it isn't set until
> _object_state_changed_cb is called.
>
> Is there a way I can get the path to the icon?

You are right, I suggest creating the notification in
ClipboardIcon._object_state_changed_cb instead, when the percent
reaches 100. At that point you should already have the icon (not path
but just icon name).

Good luck,

Tomeu

> On Mon, Apr 14, 2008 at 11:44 AM, Eben Eliason <eben.eliason at gmail.com>
> wrote:
> >
> > On Mon, Apr 14, 2008 at 12:39 PM, Gary C Martin <gary at garycmartin.com>
> wrote:
> > > On 14 Apr 2008, at 15:04, Mikus Grinbergs wrote:
> > >
> > >  > Personal note:  Been running the "new look" Sugar/Joyride for a
> > >  > while.  [It does what you describe when an Activity is launched.]
> > >  >
> > >  > I've now trained myself to notice the pulsing icon in the top left
> > >  > hand corner -- but I think that is an easily-overlooked location
> > >  > (particularly since current notification icons have the same
> > >  > background color as the "border" in which they sit).
> > >
> > >  I also find the new 'activity launch notification' less than
> > >  satisfying. Launching an activity is a very distinct action  taken by
> > >  a user, and the current pulsing notification is not enough of an
> > >  indication of the result. It's also odd if you do happen to have the
> > >  frame open as you see 2 pulsing icons for the launching activity (one
> > >  the notification and one in the actual frame).
> > >
> > >  I'd like to suggest, again, that the activity launching metaphor be
> > >  one where:
> > >
> > >  1) Kid clicks on activity icon to launch
> > >  2) Sugar immediately opens a fullscreen canvas with just the large
> > >  pulsing icon (i.e a activity zoom view)
> > >  3) Canvas is occupied by the activity once it has loaded
> >
> > This is in fact the very approach we aim to implement, hopefully in
> > the near future.  I'm in agreement with all of the interactions you
> > mention below.  The one which may not be trivial to add (though again,
> > I would strongly prefer) is the ability to prevent the launched
> > activity from stealing focus if the user has since switched away, but
> > we'll take things one step at a time.
> >
> > - Eben
> >
> >
> >
> >
> > >  This provides:
> > >
> > >  - immediate and clear feedback to the kid that an activity is indeed
> > >  launching
> > >  - prevents casual/impatient clicks on other activity icons while the
> > >  first loads
> > >  - allows access to the frame, and for the kid to switch back to
> > >  neighbourhood/group/home if needed
> > >  - if the kid does intentionally switch away, the background activity
> > >  launch does not suddenly drag them back once complete
> > >  - the slide out launch notification is not needed, but the pulsing
> > >  frame activity icon would stay
> > >
> > >  If at some future point we get usable Sugar compositing, a nice zoom
> > >  animation could be added to the launched activity so that from where
> > >  ever it was clicked, it scales up and into the centre of the screen
> > >  and starts to pulse, while the rest of the screen content fades out.
> > >
> > >  Gary
> > >
> > >  _______________________________________________
> > >  Sugar mailing list
> > >  Sugar at lists.laptop.org
> > >  http://lists.laptop.org/listinfo/sugar
> > >
> > _______________________________________________
> > Sugar mailing list
> > Sugar at lists.laptop.org
> > http://lists.laptop.org/listinfo/sugar
> >
>
>
> _______________________________________________
>  Sugar mailing list
>  Sugar at lists.laptop.org
>  http://lists.laptop.org/listinfo/sugar
>
>