Hi Andre, welcome to the mailing list! And thanks for the clarification..
Ok, well I can understand now what the subtle difference is.. although I
don't believe it will particularly confuse people... but if you
(MontBlanc/anyone) can send us a patch, you're welcome to do so.. I will
merge it when I can! :)
KaKaRoTo
On Wed, Jul 8, 2009 at 11:51 AM, Montblanc <toto...@gmail.com> wrote:
> Yeah, I know I must have exposed what I meant very unclearly. I'm sorry.
> I was talking about differentiating the uonline and online keys, which
> both are "Online", so that the when a user "comes online" or "changes
> status" from busy/away/ecc. to online the user is not going to get
> confused while scrolling the event bar.
>
> So, changing online key from "Online" to "Available" would be the
> first solution (which I recommend) and the EVENT BAR should print:
>
> "$user online" -----> Buddy Available ----> when he switches status to
> Available
> "$user uonline" -------> Buddy Online -------> when he logs in,
> meaning you can find him in the Online group
> "$user offline" -----> Buddy Offline -------> when he logs out OR
> switches to Invisibile (we can't know that for sure, so just one key).
>
> In the second email I talked about another way to differentiate coming
> online and switching to online, so while the event bar should always
> print "$user online" (Buddy Available) when Buddy changes status to
> Available, it should print "$user logsin" (Buddy has just signed in)
> when Buddy logs in (and "$user logsout" when he logs out, obviously")
>
> "$user online" ----> Buddy Available ----> when he switches status to
> Available
> "$user logsin" ----> Buddy has just signed in -----> when he logs in,
> meaning you can find him in the Online group
> "$user logsout" ----> Buddy has just signed out -------> when he logs
> out OR switches to Invisibile (we can't know that for sure, so just
> one key).
>
> I really hope I explained it in a clearer way. ^__^"
> Bye!
>
> Montblanc
>
> 2009/7/8 André Ventura <andr...@gmail.com>:
> > Hello :) (first email, yay :p)
> >
> > I think I understood what Montblanc meant:
> >
> > There is uonline (user logs in or changes status from invisible to
> online)
> > and online (user changes status from busy/idle/etc. to online), if I
> > understood right.
> > At the moment they are both translated as "$user Online" and should be
> > translated to, respectively, "$user Online" and "$user Available".
> >
> > At the second email I think he meant that uonline could become logsin, to
> > avoid confusions because uonline and online are very similar. :)
> >
> > afv
> >
> > On Wed, Jul 8, 2009 at 2:52 AM, Youness Alaoui
> > <kakar...@kakaroto.homelinux.net> wrote:
> >>
> >> humm.. I'm really not sure i understand the problem, you sent two mails
> >> and both were very confusing and hard to understand... could you try to
> make
> >> it any more clear ?
> >> either way, i don't really see any reason why there would be confusion
> for
> >> the user or that we would need to change keys... (for now)
> >> KKRT
> >> On Sun, Jul 5, 2009 at 3:40 PM, Montblanc <toto...@gmail.com> wrote:
> >>>
> >>> Hello again,
> >>> First of all, sorry for spamming your mailbox!
> >>> I just thought about a simpler alternative: the event bar could just
> >>> display the same thuings the event window is displaying when a contact
> >>> logs in and out. It should just use the 'logsin' and 'logsout' keys:
> >>>
> >>> username + logsin
> >>> username + logsout
> >>>
> >>> I think it's much better and should avoid confusions between users
> >>> logging in/out and changing status! I'll be waiting for your feedback.
> >>> Best Regards!
> >>>
> >>> Montblanc
> >>>
> >>> 2009/7/2 Montblanc <toto...@gmail.com>:
> >>> > Hello everybody,
> >>> >
> >>> > A little idea bumped up in my mind when I was fixing langit (I still
> >>> > am, actually...). I think we might need to differentiate groups from
> >>> > statuses.
> >>> > Let me explain: when I take a look at the event bar I see something
> >>> > like "Username Online" which can be quite confusing if I both set
> aMSN
> >>> > to show me users status changes and switch notification windows off.
> >>> > "online" and "uonline" are both translated as "Online", but we could
> >>> > let uonline be Online (meaning the Online group) and call the online
> >>> > key "Available". This way, aMSN should print a "username uonline" or
> >>> > "username uoffline" when the user is connecting or disconnecting, and
> >>> > "username online" when he/she switches to Available status.
> >>> > I think there's no need to differentiate uoffline and offline too,
> >>> > since we can't know whether he/she's switching to Invisible or
> >>> > disconnecting.
> >>> > I suppose WLM 2009 has already switched the Online status to
> >>> > Available, so we just need to change the online key to look like
> >>> > "online Available" and have the event bar to discriminate between
> >>> > online and uonline appropriately.
> >>> >
> >>> > I know you're all kinda busy and you'll soon be attending the GC
> >>> > Desktop Summit (yeah!), so please just tell me what do you think
> about
> >>> > it, when you'll have some spare time!
> >>> > Greetings,
> >>> >
> >>> > Montblanc
> >>> >
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> _______________________________________________
> >>> Amsn-devel mailing list
> >>> Amsn-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/amsn-devel
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Enter the BlackBerry Developer Challenge
> >> This is your chance to win up to $100,000 in prizes! For a limited time,
> >> vendors submitting new applications to BlackBerry App World(TM) will
> have
> >> the opportunity to enter the BlackBerry Developer Challenge. See full
> >> prize
> >> details at: http://p.sf.net/sfu/Challenge
> >> _______________________________________________
> >> Amsn-devel mailing list
> >> Amsn-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/amsn-devel
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > Enter the BlackBerry Developer Challenge
> > This is your chance to win up to $100,000 in prizes! For a limited time,
> > vendors submitting new applications to BlackBerry App World(TM) will have
> > the opportunity to enter the BlackBerry Developer Challenge. See full
> prize
> > details at: http://p.sf.net/sfu/Challenge
> > _______________________________________________
> > Amsn-devel mailing list
> > Amsn-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/amsn-devel
> >
> >
>
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
