[aerogear-dev] native ui

[Matthias Wessendorf]

On Tue, Jan 20, 2015 at 6:54 PM, Summers Pittman <supittma at redhat.com>
wrote:

>  On 01/20/2015 12:49 PM, Matthias Wessendorf wrote:
>
>
>
> On Tue, Jan 20, 2015 at 6:38 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> On 01/20/2015 04:40 AM, Erik Jan de Wit wrote:
>> >> Sounds like a good project for a student on the "Google Summer of
>> Code"?
>> >>
>> > Right, or I could do it while I ‘wait’ for iOS and android sync
>> libraries
>> Or you could help us with the sync libraries.
>>
>
>  that or anything else, is way higher priority
>
>
>>
>> Right now passos and I are discussing making APIs to connect with the
>> sync server and FeedHenry's services.
>
>
>  Not sure we should duplicate functionality that's already available
> inside of the FH SDK.
>  My pref. here is focusing on our real-time sync server first..... I
> don't get why using the FH SDK for accessing the sync framework from
> feedhenry is not good enough
>
> It may be enough.  I don't have enough information to make this claim
> however.  At the very least there will need to be shim code to make sure it
> plays nicely with the other Aerogear things.  For instance we may want to
> use a Keycloak OAuth solution to retrieve tokens to talk to FH.sync.  We
> will need to have enough support in AG.sync to pass those tokens to FH.sync.
>

Again, my preference here is to limit our current sync work on the
real-time stuff. We can do the FH 'adapter' always at a later time (e.g.
this summer or fall)

-Matthias



>
> Also the FH Android SDK is very incomplete right now and is missing
> features that are in the FH JS SDK and in AG Android.  They will need to be
> written at some point by someone.
>
>
>
>
>
>
>
>>   After we figure out what that
>> will look like from an API/usage standpoint we can begin designing that
>> code.  After that point we will need to figure out how to work it into
>> the Android Sync Adapter framework (which will probably require some
>> work on the auth/authz end).
>>
>> We've got a planning gist right now to define our epics before we make
>> individual JIRA tasks.
>>
>> https://gist.github.com/secondsun/68cbbc54366b653f57d6
>>
>> If you could become a FH sync expert this week it would do amazing
>> things for our ability to move forward.
>
>
>>
>>
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>> Summers Pittman
>> >>Phone:404 941 4698
>> >>Java is my crack.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Summers Pittman
> >>Phone:404 941 4698
> >>Java is my crack.
>
>


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150120/f57c765d/attachment.html