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

List:       kopete-devel
Subject:    Re: [kopete-devel] Status Manager
From:       Gustavo Pichorim Boiko <gustavo.boiko () kdemail ! net>
Date:       2007-07-30 12:49:21
Message-ID: 200707300949.21999.gustavo.boiko () kdemail ! net
[Download RAW message or body]

A Friday 27 July 2007 16:24:30, Roman Jarosz escreveu:
> Hi,
>
> I've been working on Kopete status manager, the basic stuff (functional) is
> ready. Don't pay attention to some class names because this will change to
> something more consistent, and also I'll clean up the code. It's not
> polished because I'm going tomorrow on vacation for a week and I wanted to
> post it before I go.
>
> Ok so what's new.
>
> We have status manager and status manager dialog, which is currently in
> configure dialog (see screenshots).

While I think the idea of a status manager is indeed very nice, I don't like 
the interface at all. We are trying to simplify kopete interface a bit, and 
this is just too complex to handle.
Why not keeping it simple?

> Status manager can contain two types of items Status and StatusGroup.
> StatusGroup is used for grouping statuses like in Adium, it has title and
> category. Status has title, category and message. The number of groups and
> statuses and group sub levels aren't limited. Every status item has unique
> id, so we can remember the last status and restore it on startup. Status
> and StatusGroup structure is stored in xml file.

I'm ok for status groups, but I would vote against nested groups. I think just 
one group level do the job, and it is much simpler to configure and to 
implement even :)

> In status manager dialog items can be reorganized/moved with drag&drop so
> it's really easy.

This is nice, drag-and-drop is something that should "just work" TM ;)
And nice you are taking care of that since the beginning :)

> In Kopete main window menu a "Set Status Message" menu was removed. We only
> have Set Status menu, in that menu are items that you have in status
> manager dialog. If you select any item from that menu, than status, message
> and title from that item will be set in all accounts (title isn't
> propagated to protocols yet). A status type is determined from category.
>
> A protocol menu have in sub menus all items from status manager but the
> category is ignored and insted KopeteOnlineStatus form top level item is
> used.

Agreed, but having nested status groups makes this unusable.

> I added two more version of that menu (the code is already there but it's
> not enabled) 1) Menu have only items with the same category as top level
> KOS category. 2) The top level KOS items are removed and the menu look like
> Global Set Status menu.
>
> I don't have to have the 3 alternatives in the final version.
>
> The bottom left "Status Message" menu will change, don't know have yet :)

Maybe it will even go away after the identity_refactory is done ;)

> I put this mail together really quickly so I hope you have understand it.
> Btw I'm open to any cool new ideas or suggestions.
>
> screenshots:
> http://kedge.wz.cz/kopete1.png
> http://kedge.wz.cz/kopete2.png

Really nice job, but I would just try to simplify the interface as most as 
possible so that kopete doesn't look like a beast (as it is right now) :)

Cheers
-- 
Gustavo Pichorim Boiko
-----------------------------------
KDE Developer      www.kde.org
Mandriva Labs      www.mandriva.com
_______________________________________________
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]