<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Hi,</span></div><div><br><span></span></div><div><span>I'm planning to begin the redesign stating with next week, so if you have time to join it will be great !</span></div><div><br><span></span></div><div><span>Cheers,</span></div><div><span>BogDan.</span></div><div><span><br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Robert Schuster <r.schuster@tarent.de><br><b><span style="font-weight: bold;">To:</span></b> Espen Riskedal <espen@cutehacks.com><br><b><span
style="font-weight: bold;">Cc:</span></b> necessitas-devel@kde.org<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, September 20, 2011 10:19 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: Java part rework - concept<br></font><br>Hi Espen,<br>first of all: Sorry, for the delay. I did not see this post until now<br>and was on vacation last week.<br><br>Am 31.08.2011 14:54, schrieb Espen Riskedal:<br>> I've been reading throught this and have some questions.<br>Cool!<br><br>> The Bridge code is obviously tied to a spesific Qt release and<br>> promises no compibility. But what about the Loader code?<br>The Loader code interacts with a the Bridge, that's right. However the<br>interface<br>between the two is under our control.<br><br>> As I understand the app will ask for a minimum version of the Loader,<br>> and if the Loader is of a later version that Loader will still promise<br>> backward compatibility
for earlier Loader versions?<br>The App will ask Ministro for a minimum version of the Loader and Ministro<br>will provide an implementation that fits. For the moment I suggest we<br>bundle our Loader with Ministro (packaging it as a raw resource). The<br>Loader is very small and we can easily put 3 or more of them into<br>Ministro's APK. If we want more flexibility we put the Loaders in an<br>online repository and let Ministro download them when requested. When we<br>do that we gain two more things:<br>a) we can update the Loader implementation under the hood (e.g. when a<br>change of the Loader-Bridge interface was necessary)<br>b) the Loader levels Ministro supports is dependent on what is in the<br>repository not on Ministro itself.<br><br>> But, is there not a connection between the Loader code and the<br>> Bridge/Qt Qt code as well? When looking at<br>> <a
href="https://github.com/thebohemian/necessitas-android-poc/blob/master/loader/src/eu/licentia/necessitas/loader1/Activity4.java" target="_blank">https://github.com/thebohemian/necessitas-android-poc/blob/master/loader/src/eu/licentia/necessitas/loader1/Activity4.java</a><br>> I guess these stubs calls something in the end? Also, how is a newer<br>> version of a Loader created - as a subclass of the previous version or<br>> as a parallelle subclass implementing an Interface or?<br>This depends solely on us. The App only sees the Java interface that we<br>defined<br>not how it is implemented. Subclassing sounds reasonable to me when the<br>new Loader just implements more methods. If it works radically different<br>I'd go for a new class.<br><br>> Another general question I was thinking of - does this add more<br>> complexity to debugging an app with gdb etc?<br>Not at all.<br><br>> And another question - will this setup make it harder
for developers<br>> to add their own Java code to an app?<br>Yes and no.<br><br>The Android PoC contains two variants of an App. One of them is the<br>generic app template that all programs should use. It does the minimum<br>of what is necessary do interact with Ministro and the Loader. But there<br>is also 'appv1'. This one was my initial code for the app and it<br>contains code which logs the things happening during the Ministro and<br>Loader interaction. One could see that as a major modification of the<br>normal app-template code. In other words, if some rules are followed<br>there is room for custom Java/Android code.<br><br>> It's pretty complex stuff :)<br>So is the qt-port for me. :)<br><br>Regards,<br>Robert<br><br>-- <br>tarent solutions GmbH Niederlassung Berlin<br>Thiemannstr. 36 a, D-12059 Berlin • <a href="http://www.tarent.de/" target="_blank">http://www.tarent.de/</a><br>Tel: +49 30 3187969-999 • Fax: +49 228 54881-314
(Bonn)<br><br>Rochusstraße 2-4, D-53123 Bonn • <a href="http://www.tarent.de/" target="_blank">http://www.tarent.de/</a><br>Tel: +49 228 54881-313 • Fax: +49 228 54881-314<br>HRB AG Bonn 5168 • USt-ID (VAT): DE122264941<br>Geschäftsführer: Boris Esser, Elmar Geese<br><br><br><br>_______________________________________________<br>Necessitas-devel mailing list<br><a ymailto="mailto:Necessitas-devel@kde.org" href="mailto:Necessitas-devel@kde.org">Necessitas-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/necessitas-devel" target="_blank">https://mail.kde.org/mailman/listinfo/necessitas-devel</a><br><br><br></div></div></blockquote></div></div></body></html>