so... I guess... my bet would be aligning more with the JS layer ?<br><br><div class="gmail_quote">On Tue, Mar 26, 2013 at 4:39 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">ideally the JS API is similar to the Android/Java API...<div><br></div><div>sure to some degree there are differences, based on the underlying platform, but having it fundamentally different (e.g. Factory/IDGenerator) etc is a bit... :)</div>
<div><br></div><div>Things like that could haven been added in an overloaded ctor - perhaps we can align the API a bit more, post 1.0.0 <div><div class="h5"><br><br><div class="gmail_quote">On Tue, Mar 26, 2013 at 8:34 AM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi guys,<br>
<br>
I want to create wrappers around aerogear-js to be able to use the Aerogear from Erria. What this task comes down to is to create a java api that calls the aerogear-js api. But then I rembered seeing an example in a presentation that you kept the apis the same on all platforms. So my work is already done I just have to look at the api defined in android. The only problem is there are some differences, for instance DataManager on the js side it can be created by passing some config object, but on the android side there is a need for an IdGenerator and a StoreFactory. So what do you guys think should I stick closer to the js api and really try to create a minimal wrapper that is close to that, or should I stick with the android api and maybe use parts of Errai to implement a bridge?<br>
<br>
Cheers,<br>
Erik Jan<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>