<br><br><div class="gmail_quote">On Mon, Oct 19, 2009 at 4:14 PM, Thomas Baumgart <span dir="ltr"><<a href="mailto:thb@net-bembel.de">thb@net-bembel.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<div class="im"><br>
on Monday 19 October 2009 Alvaro Soliverez wrote:<br>
<br>
<br>
> Michaël,<br>
> can you send the class to the list, so we have an example?<br>
><br>
> All, this is somewhat related to the issue we had in the saveFile method.<br>
> Moving those methods to the engine will have multiple benefits, as we can<br>
> see.<br>
> In my case, I'm interested on Akonadi for calendar and the FinanceStack and<br>
> a datasource for Plasma (a quick entry plasmoid, anyone?). And from an<br>
> architecture point of view, it's best to keep the layers separate.<br>
> So, with Michaël's help we could check which methods need to be changed,<br>
> and then work on them to split GUI and engine tasks.<br>
> What's your thought on this?<br>
<br>
</div>Not sure how much of Akonadi we can really use in the FinanceStack. But<br>
otherwise, count me in on it.<br>
<br></blockquote></div><br><div>For those not in the loop, since it has never been discussed here, FinanceStack is a planned engine to share info among financial applications. I think that using Akonadi may be a way to go, because it is a storage engine designed to share data among applications and that way we avoid having to implement something ourselves, but things may turn otherwise due to performance or other issues.</div>
<div>However it may be, making it easy for other application to access KMM data can lead to exciting opportunities, and also iron out our architecture for future use cases. I have had the idea of a Plasmoid for some time and this may be a good starting point for that.</div>