--===============2068782082==
Content-Type: multipart/signed;
  boundary="nextPart7553458.iZGGLD5y7f";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart7553458.iZGGLD5y7f
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 25 July 2007 5:09:04 pm Andre Duffeck wrote:
> Am Dienstag, 24. Juli 2007 22:23:45 schrieb Trever Fischer:
> > On Tuesday 24 July 2007 6:20:27 am Andre Duffeck wrote:
> > > Oh, you succeeded in downloading the twitter stuff with QHttp. I did
> > > not with KIO and ended up implementing it on top of QTcpSocket...
> >
> > I wanted to start somewhere simple, as how to stuff all the data into
> > such a restrictive design was my main priority. Using KIO would be a
> > great idea because then proxy settings would be honored.
> >
> > > I can't say much to the way of implementation, because i have hardly
> > > looked at the DataEngine stuff at all, but besides that i think i'd
> > > rather want to retrieve the raw XML in the Timeline and Timeline:user
> > > data source instead of the ids only.
> >
> > That doesn't seem to make much sense to me. If you just wanted the engi=
ne
> > to return raw XML, making a HTTP/KIO data engine that returns the
> > contents of a file would be the same thing.
> >
> > > Having one source per tweet seems a little overkill for
> > > me, but that's just my opinion and maybe others can comment on that,
> > > too?
> >
> > I had other ideas for how to stuff such a complicated data structure in=
to
> > a DataSource, and this seemed to make the most sense to me. Another idea
> > I had was to use a QList of QMaps but /that/ seemed like overkill to me.
> > The idea would have been to create the same structure in the Update:
> > elements, but in a QMap and in a user's timeline. It didn't seem right =
to
> > me to use some made-up storage format, when there are already tools
> > available. I use DataEngine's auto-expiration property to limit the tot=
al
> > sources to 30 though.
> >
> > > Besides i'd like to use your engine in the applet...
> >
> > Thanks :)
>
> Ok, i had not understood the dataengine concept. It now makes more sense
> and if you don't mind i'd import your engine into svn and start using it.
> Or do you have a svn account?

Nope, I don't have a(n) svn account. If I had one, I wouldn't use it much=20
anyways. Go ahead and put it in there :)

=2D-=20
PGP Key ID: 0x35EB69FB
Keyserver: wwwkeys.us.pgp.net

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.0

=2D----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT/CM/CS/CC/M/IT/S d--(-) s++:- a--- C++ UL++++>$ P+ L+++ !E W+++
 N o+ K w@ O? M?> V? PS+ PE+@ Y+ PGP++ t 5? X- R-- tv b+ DI+ D?
  G e>++++ h! r>++ y
=2D-----END GEEK CODE BLOCK------

--nextPart7553458.iZGGLD5y7f
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iD8DBQBGqAqoiUbx4zXrafsRAoNdAJ463LtzP2oopeZNoBgZkMHgwZPY/wCfbBQl
tgyYy+RnGMrTaCeI8ZW/j4w=
=MP+O
-----END PGP SIGNATURE-----

--nextPart7553458.iZGGLD5y7f--

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

_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel

--===============2068782082==--