On Mon, 08 Oct 2007 01:39:56 +0200, Olivier Goffart <[EMAIL PROTECTED]> wrote:
> Le dimanche 7 octobre 2007, Roman Jarosz a écrit : >> Hi, >> >> I have finished the Status Manager. (I was really busy so I couldn't finish >> it faster) > > Thanks... > > >> >> Here are some screenshots: >> http://kedge.wz.cz/kopete/sm1.png - Status Manager >> http://kedge.wz.cz/kopete/sm2.png - Auto Away setting with title edit box >> http://kedge.wz.cz/kopete/sm3.png - Protocol status menu settings > > All the status options should go in the status page Ok >> http://kedge.wz.cz/kopete/sm4.png - Global status menu > >> http://kedge.wz.cz/kopete/sm5.png - Global status menu with open >> message/title editor > > Wouldn't this editor be better in a simple dialog? It wouldn't be difficult to change it. I like better the menu but I'm ok with the dialog too. Let see what others think. >> http://kedge.wz.cz/kopete/sm6.png - Protocol menu with >> "All statuses with parent category" http://kedge.wz.cz/kopete/sm7.png - >> Protocol menu with "Only statuses with matching category" >> http://kedge.wz.cz/kopete/sm7.png - Protocol menu with "As global status >> menu" Btw the last screenshot should be http://kedge.wz.cz/kopete/sm8.png > One if the idea behind identities it to make the status global per identity, > not per account anymore. > >> Main features: >> - New status manager >> - Only one group level (as requested by Matt and Boiko) >> - Drag & drop >> - Three types of protocol menu (don't know which should be as default) >> - Quick message/title editor in status menu and in bottom left corner of >> Kopete main window. >> >> Below is a list of new and some changed classes with short description. >> >> Any comments/questions are welcome! >> >> Regards, >> Roman >> >> P.S. I didn't described too many details, because I'm really tired. >> --------------------------------------------------------------------------- >>--- New libkopete classes: > > Class in libkopete should have a complete documentation (and even if the > class is not in libkopete this is generally good) I agree and will document it. >> Kopete::Status::StatusItem >> Kopete::Status::Status >> Kopete::Status::StatusGroup >> - These three classes are used to build status tree and >> hold all necessary data e.g. title, category, message. > > I don't like the namespace Status. Well I didin't like Kopete::Status::Status but haven't come up with anything better and than I forgot about it. Any ideas how to change it? >> Kopete::StatusRootAction >> Kopete::StatusGroupAction >> Kopete::StatusAction >> - Actions for global/protocol status menu. >> >> Kopete::StatusEditAction >> - Status message and title editor for status menu > > Should theses class be in libkopete API? > I think they belong to the kopete application. > > In fact, i think the whole StatusManager belong to the Kopete application, and > not to libkpoete, which is the interface with plugins and protocols. But > there may be a reason I ignore. Theses classes have to be in libkopete because we use them when we create protocol menu in OnlineStatusManager::createAccountStatusActions(...) >> Kopete::StatusManager >> - Manages status tree >> - Saves/loads status data tree >> - Saves/loads last status >> - Set auto away >> >> Kopete::IdleTimer >> - Global idle timer, used for auto away in StatusManager. >> >> Kopete::OnlineStatusManager >> - add functions >> Categories category( const OnlineStatus& status ); //return the >> category for given status static KIcon iconForCategory( Categories category >> ); //return icon for given category >> >> Kopete::StatusMessage >> - add title >> >> New kopete classes: >> >> KopeteStatusConfig >> - status configuration >> >> KopeteStatusModel >> - status model for status view in KopeteStatusConfig class _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
