[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    Re: [kopete-devel] changeGlobalStatusMessage and
From:       adrian <iamcalvo () gmail ! com>
Date:       2007-04-26 18:14:39
Message-ID: 200704262014.40675.iamcalvo () gmail ! com
[Download RAW message or body]

On Thursday 26 April 2007 14:25:38 Will Stephenson wrote:
> On Tuesday 24 April 2007, adrian said:
> > Functionallity changed:
> > -	Before when the global nickname was edited it changed its color to red
> > indicating your changes weren't saved. When you pressed return it's color
> > returned to black indicating your changes were saved. This feedback is
> > explict but hard to understand (why is it red?ah it's not saved, how do i
> > save it?) the first time. Also I was missing it when I edited my global
> > status message.
> > 	Now both input boxes behave the same way: when you edit the text the
> > save icon shows an enabled state(colorfull). When you press return or
> > click on the save icon it shows disabled state and the lineedit loses
> > keyboard focus.
>
> Ok, so it doesn't change the behaviour of the global status message system,
> just improves the not saved feedback mechanism.

Yes, that was my goal :). I've been the most cautious as I'm just begining 
with Qt/KDE and i'm not familiar yet with kopete.

> > -	Edit Global Identity toolbar is now thiner as it's margins were
> > reduced.
> >
> > -	Now selecting "No message" as global status message works.
> >
> > -	Now selecting a recent global status message works.
>
> It didn't before (asking as the one of the other hackers of the global
> status message system)?
>

Well, when selecting "No message" it did set an empty status message across 
all accounts but couldn't update Kopete::Away::awayMessage as 
setGlobalAwayMessage checked for it not being empty, causing a inconsistency.

There also was a missed ++ (although it existed in previous revisions) foreach 
recent-message-menu-item inserted so them all picked 1 as index thus setting 
last message either one activated.

Last, when that was solved, it incurred in an strange behaviour with signals 
and slots which forced to disconect activated(int) signal from previous slot 
(sorry it's dificult to explain in englsh :), don't doubt asking if 
interested).

So yes, it worked before and now it works again :).

> > Functionality added:
> > -	Now Edit Global Status Message lineedit shows your current global
> > status message (http://bugs.kde.org/show_bug.cgi?id=124161 and
> > http://bugs.kde.org/show_bug.cgi?id=130924).
> >
> > -	Now users can update the global nickname or status message pressing on
> > a button in the lineedit (see screenshots).
>
> IMO we need to redo the status message system and leave the 'queue' of
> status messages to have a manageable list of messages (like we had in the
> old days). This would be a better fit for server side custom away states.
>
> Something like
>
> add status message
> delete status message
> associate status with message (always go "Away" when selecting "Walking the
> Dog")
>
> Will

Yes yes we have some ideas here: http://bugs.kde.org/show_bug.cgi?id=111532.

It should somehow relate 
away_status - message_title/concept - account -  status_message
for example:
[away] - [Eating] - [icq(Professional)] - [... lunch break. I'll be avaliable 
at ...].
 Or:
[away] - [Eating] - [yahoo(Friends)] - [ Recharging my batteries! ].

When I have some time I'll do some diagrams or such (i'm some confused right 
now, haven't yet understood kopete. Also noted that there is some 
branches/work being done i should look).

Well, I'd like to hear some opinions about first mail questions now you have 
screenshots.

PS: I've been lately in #kopete as iamcalvo, don't doubt shouting to me :).
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]