api review for DataEngineConsumer
Aaron J. Seigo
aseigo at kde.org
Tue Sep 25 07:36:14 UTC 2012
On Monday, September 24, 2012 21:09:57 Marco Martin wrote:
> rationale to remove remoteDataEngine
the difference between dataEngine and remoteDataEngine was passing a QUrl for
the remote engine. it seemed natural to merge the two things. not only does
this give us just one method in the public API, but it also makes the split
between local/remote less evident / obvious, which is what should be worked
towards imho.
> and finishedWithEngine?
this was not in DataEngineConsumer (DEC), as DataEngine usage is tied to the
lifespan of a given DEC. the idea is to just delete the DEC when you are
finished with the engines loaded using it.
--
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120925/fb7c1f21/attachment.sig>
More information about the Plasma-devel
mailing list