From kde-pim  Mon Mar 21 17:18:28 2005
From: Tobias Koenig <tokoe () kde ! org>
Date: Mon, 21 Mar 2005 17:18:28 +0000
To: kde-pim
Subject: Re: [Kde-pim] [RFC] KRES::Resource class for KDE 4.0
Message-Id: <20050321171828.GA1233 () ghostdog ! localnet>
X-MARC-Message: https://marc.info/?l=kde-pim&m=111142554116642
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0595290926=="


--===============0595290926==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC"
Content-Disposition: inline


--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 21, 2005 at 11:26:07AM +0100, Cornelius Schumacher wrote:
> On Saturday 19 March 2005 16:48, Tobias Koenig wrote:
Hi Cornelius,

> An alternative might be to delay the actual call of the do* functions and=
=20
> immediate error reporting until the code has returned to the event loop. =
So=20
> we wouldn't need the emit* functions but still could make sure that the=
=20
> signals aren't emitted during the load/save/open/close calls.
That's corrected now, like discussed on irc. Thanks for the idea!

> What about the identifier,
This is an interesting topic. In libkabc and I guess also in libkcal
exists classes which need an unique id.
So what do you think about an UniqueObject class (is the name ok?) that
can act as base class for all these classes?
It just has the methods

  void setUid( const QString& )
  QString uid() const

and uses QUuid for a real unique id.

> name, type, read-only information? This belongs to=20
> the Resource class even if we do the config handling externally.
Yes of course, will add it and resend the source for a review then.

> The active state should be handled externally, in my opinion, as it would=
 make=20
> it possible to have different active (or other) states of the same resour=
ces=20
> for different applications.
Sounds ok.

> Another problem we might want to address is the semantics of open/close i=
n=20
> relation to load/save. This isn't too well-defined right now. How is open=
=20
> actually used?
IMHO this differences are needed to provide a clean API for resources
that access servers. Most protocols know an open/close load/save state,
so that fits well.

Of course we should extend the API docu and write a
HOWTO.implement_resources.

> In practice I experienced more problems than benefit from=20
> having separate calls for open and load.
So what for example?

Ciao,
Tobias
--=20
Separate politics from religion and economy!
The Councile of the European Union is an undemocratic and illegal instituti=
on!

--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCPwHkSvFUKpY6VLARAgQtAJ4vqGE4t2a23VZDI52rHzVDPJLpOwCgn1t3
BJaXzBhQyvtZGVk4cizIuaU=
=Zecr
-----END PGP SIGNATURE-----

--wRRV7LY7NUeQGEoC--


--===============0595290926==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
--===============0595290926==--