[aerogear-dev] Push "all inclusive" demo

Sat Jun 15 11:31:16 EDT 2013

Well, yeah , my 70% of reusability was for sure a bit optimistic but in the
end, admin client and "simple" client will speak against the same API set
(where some services are only accessible by the admin (thx to the excellent
ag-sec support ;) ) )

On Sat, Jun 15, 2013 at 5:24 PM, Kris Borchers <kborcher at redhat.com> wrote:

>
>
> On Jun 15, 2013, at 10:17, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>
> And as a side note, the "admin" client used for the backend-app is also
> using areogear-js under the cover ;) . So it would be easy to write a web
> client, 70% of the code is already available :)
>
> I don't think I agree with that since a demo client will not interact with
> the interfaces an admin client would and vice versa.
>
>
>
> On Sat, Jun 15, 2013 at 5:13 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>>
>>
>>
>> On Sat, Jun 15, 2013 at 5:09 PM, Kris Borchers <kborcher at redhat.com>wrote:
>>
>>>
>>>
>>> On Jun 15, 2013, at 10:02, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>
>>> It will come for sure, we just have to discuss "the planning" ;)
>>> Seb
>>>
>>>
>>> But isn't that what this discussion is? If the goal is not to have
>>> similar functionality between the native and web demos then I guess it's
>>> not a big deal but I assume we do want that similar functionality so all
>>> demos should be included from the beginning to avoid wasted time by having
>>> duplicate conversations.
>>>
>>
>> again, right now there is just the demo. Zero lines are written for the
>> clients.
>> The overall story works on all the different platforms.
>>
>>
>>>
>>>
>>>
>>>
>>> On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher at redhat.com>wrote:
>>>
>>>> Maybe I missed off list discussions but is there any reason an "all
>>>> inclusive" push demo doesn't include JS (SimplePush) in any of this
>>>> discussion?
>>>>
>>>> On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>>
>>>> Service has been added :
>>>>
>>>> PUT /leads/{id}
>>>>
>>>> Update a Lead, typically used if a Sale Agent wants to assign a lead to
>>>> him.
>>>>
>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39
>>>>
>>>> returns no data
>>>>
>>>>
>>>> On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>>>>
>>>>> Exactly ! That is the "public" set needed by the client : login/logout
>>>>> , get leads, update location/status
>>>>>
>>>>> Oh ! I miss one "assign lead to user" , I will update the doc
>>>>> Seb
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> nice!
>>>>>>
>>>>>> that should be enough for the mobile clients, right ?
>>>>>>
>>>>>>
>>>>>> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc at gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Ok,
>>>>>>> We got here a first set of services which should be enough for the
>>>>>>> demo purposes :
>>>>>>>
>>>>>>>  POST /login
>>>>>>>
>>>>>>> Login service, mandatory for all further request.
>>>>>>>
>>>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json"
>>>>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login
>>>>>>>
>>>>>>> It will return the user :
>>>>>>>
>>>>>>>  {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"}
>>>>>>>
>>>>>>> POST /logout
>>>>>>>
>>>>>>> Logout service.
>>>>>>>
>>>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json"
>>>>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout
>>>>>>>
>>>>>>> returns no data
>>>>>>> GET /leads
>>>>>>>
>>>>>>> Obtain a list of leads.
>>>>>>>
>>>>>>>  curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json"
>>>>>>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads
>>>>>>>
>>>>>>> You will get a list of leads :
>>>>>>>
>>>>>>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}]
>>>>>>>
>>>>>>> PUT /saleagents/{id}
>>>>>>>
>>>>>>> update a SaleAgent, the service will only update the status and the
>>>>>>> location for now.
>>>>>>>
>>>>>>>  curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb21360ff684
>>>>>>>
>>>>>>> returns no data
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf <
>>>>>>> matzew at apache.org> wrote:
>>>>>>>
>>>>>>>> w00t!!!!
>>>>>>>>
>>>>>>>>
>>>>>>>> On Friday, June 14, 2013, Sebastien Blanc wrote:
>>>>>>>>
>>>>>>>>> A quick update :
>>>>>>>>>
>>>>>>>>> A first version of the backend application has been created and be
>>>>>>>>> found here
>>>>>>>>> https://github.com/sebastienblanc/aerogear-push-quickstart-backend/
>>>>>>>>>
>>>>>>>>> You can create Leads, then query for Sale Agents and send them a
>>>>>>>>> push notification containing the lead information.
>>>>>>>>>
>>>>>>>>> The readme contains all the intructions. We made some tests with
>>>>>>>>> Matzew yesterday and we were able to send notification from the backend app
>>>>>>>>> to an Android Device, using of course, the Push Server : this means we have
>>>>>>>>> the complete loop working , yeah !
>>>>>>>>>
>>>>>>>>> I will now work on the API of the Prodoctor app that will be used
>>>>>>>>> by the Native Clients.
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf <
>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>
>>>>>>>>> Repo suggestions:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>    - aerogear-push-quickstart-android
>>>>>>>>>    - aerogear-push-quickstart-backend
>>>>>>>>>    - aerogear-push-quickstart-ios
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <
>>>>>>>>> matzew at apache.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <
>>>>>>>>> supittma at redhat.com> wrote:
>>>>>>>>>
>>>>>>>>>  On 06/12/2013 09:26 AM, Corinne Krych wrote:
>>>>>>>>>
>>>>>>>>> I like summers idea of replacing the popup when app is open with
>>>>>>>>> leads list.
>>>>>>>>> If you are in the leads list, the list could be updated but we
>>>>>>>>> still need some visual effect to say "new lead" maybe bold font with new
>>>>>>>>> icon.
>>>>>>>>>
>>>>>>>>> In the Google Plus application the refresh button becomes
>>>>>>>>> highlighted if there is new data. (As a suggestion).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Or... confirm the "popup" and have the list refresh. A color (on
>>>>>>>>> the new lead) is fading out :)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Or we could add the entry and have a special style applied.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 12 June 2013 15:20, Summers Pittman <supittma at redhat.com>wrote:
>>>>>>>>>
>>>>>>>>>  In Android land you wouldn't do a popup.  If the app is in the
>>>>>>>>> background you would put a notification in the drawer which the user may
>>>>>>>>> dismiss or interact with.
>>>>>>>>>
>>>>>>>>> If you are in the application it would probably be better to
>>>>>>>>> update the leads data store and send an update event.  If the Leads are
>>>>>>>>> being browsed they can be updated.  If they aren't then a badge could
>>>>>>>>> appear on the leads action.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote:
>>>>>>>>>
>>>>>>>>> Ok, there seems to be some agreement on the idea, Nice !
>>>>>>>>> Let's focus a bit on the Mobile App. As said before, it must stay
>>>>>>>>> really simple, so basically that's what the apps does :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matthias Wessendorf
>>>>>>>>
>>>>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>>>>> twitter: http://twitter.com/mwessendorf
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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 list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> _______________________________________________
>>> 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 list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130615/51b0d71f/attachment-0001.html 