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

List:       kopete-devel
Subject:    Re: [Kopete-devel] Autoaway plugin
From:       Ladislav Strojil <Ladislav.Strojil () seznam ! cz>
Date:       2002-05-04 13:22:11
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 04 May 2002 15:00, Martijn Klingens wrote:
> On Saturday 04 May 2002 12:51, Ladislav Strojil wrote:
> > The idea behind is that kopeteplugin defines method storeStatus and
> > restoreStatus.
>
> Please make that something like
>
> KopeteStatus status() const;
> void setStatus( const KopeteStatus &status );

Unfortunatelly, there is nothing like KopeteStatus class.
The functions I defined do not return anything, status is stored internally in 
each of protocol plugins. As the representation of status is not common (or 
at least so it seems) it can't be done outside.

> or so. That's much more generic to reuse.

I am not getting your point. You would like the status() method to return 
current status? Again, since there is not uniform representation, this does 
not make currently much sense. 

> QValueList<KopeteStatus> allStatuses() const;
> void setAllStatuses( const QValueList<KopeteStatus> &statuses );
>
> > Introducing KopeteStatus class looks like a good idea, the set of
> > possible statuses is probably very similar with each protocol.
>
> Not really. The idea was to have KopeteStatus reflect the basic statuses
> (Online, Offline, Away, Busy) and the more verbose plugin-specific statuses
> being internal. I.e., they can be queried with status() and restored with
> an associated setStatus() call, but the enum that holds the four basic
> statuses cannot be used in the simplified
>
> enum KopeteStatus::Status { Online, Offline, Away, Busy };
> void setStatus( KopteStatus::Status status );
>
> function. The away code can call setStatus( KopeteStatus::Away );, but the
> restore code has to provide an explicit KopeteStatus object instead.
>
> But those were the ideas, I have no idea if Ryan already had time to
> implement them. Seems he didn't. Nor do I have time to do this anywhere
> soon.

This looks good, but where is the KopeteStatus class? :-) 
Should I go and implement it from scratch? Or is it somewhere half-finished 
and waiting? :-)

Cheers,
Lada
 
- -- 
    ~       Ladislav Strojil, MFF UK
  ' v '               
 //   \\              
/(     )\    Powered by Penguin.
  ^ ' ^
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE80+CGTnMZPFqq4nwRAv1sAKCyNCCoo+WAZQEfGcvjRMRCbt5riwCfXRzr
9D12Y7lvFhXV/WXnC/9+ifY=
=ICJP
-----END PGP SIGNATURE-----

_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]