Ah my bad. I was assuming the quickstarts were in Java.
On 7 April 2014 15:05, Matthias Wessendorf <matzew(a)apache.org> wrote:
On Mon, Apr 7, 2014 at 2:59 PM, Daniel Bevenius <daniel.bevenius(a)gmail.com
> wrote:
> For the package name, was that meant to be uppercase?
> "org.jboss.aerogear.unifiedpush.HelloWorld"
>
nope - not really; iOS app:name -> HelloWord; package "o.j.a.u"
>
>
>
>
> On 7 April 2014 14:54, Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>> Since we start w/ the Hello World example, let's make sure we agree on a
>> name :-)
>>
>> I'd suggest we name it "AeroGear UnifiedPush HelloWorld".
>>
>> For packages / bundle Identifier, I'd vote for
>> "org.jboss.aerogear.unifiedpush.HelloWorld"
>>
>>
>> -Matthias
>>
>>
>> On Mon, Apr 7, 2014 at 2:44 PM, Matthias Wessendorf
<matzew(a)apache.org>wrote:
>>
>>> the GH repos have been created:
>>> *
https://github.com/aerogear/aerogear-push-helloworld
>>> *
https://github.com/aerogear/aerogear-push-quickstarts
>>>
>>> I edited the README to 'define' the (sub)folder structure
>>>
>>>
>>>
>>> On Tue, Apr 1, 2014 at 6:27 PM, Matthias Wessendorf
<matzew(a)apache.org>wrote:
>>>
>>>> Hello,
>>>>
>>>> here are the JIRAs (tasks and epics (which have sub-tasks) for this,
>>>> so far:
>>>>
>>>> Github repo work:
>>>>
https://issues.jboss.org/browse/AGPUSH-586
>>>>
https://issues.jboss.org/browse/AGPUSH-587
>>>>
>>>> Hello-World Example work (epic):
>>>>
https://issues.jboss.org/browse/AGPUSH-588
>>>>
>>>>
>>>> Quickstart-server (epic):
>>>>
https://issues.jboss.org/browse/AGPUSH-596
>>>>
>>>> Quickstart-client (epic):
>>>>
https://issues.jboss.org/browse/AGPUSH-604
>>>>
>>>>
>>>>
>>>> It's totally valid to:
>>>> - add more sub-tasks, or break sub-tasks out into epics (e.g. if they
>>>> have several work units).
>>>>
>>>>
>>>> Greetings,
>>>> Matthias
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Mar 31, 2014 at 3:25 PM, Matthias Wessendorf <
>>>> matzew(a)apache.org> wrote:
>>>>
>>>>> Hello there,
>>>>>
>>>>> we recently had talks about creating some simplified quickstarts and
>>>>> hello-word demos, related to the UnifiedPush Server and JBoss AS
developers:
>>>>>
>>>>> * Hello World (No Server Code - just client receiving push, no fancy
>>>>> (complex) UI on the client, nor integrated into a Cookbook or
something
>>>>> that has "dependencies")
>>>>> ** Cordova
>>>>> ** Android
>>>>>
>>>>> For iOS that is already there:
>>>>>
https://github.com/aerogear/aerogear-push-ios-demo
>>>>>
>>>>> Yes, just usage of the "Push Registration SDKs", is the
goal here:
>>>>> keep it simple, since native push can be a complicated use-case all
on its
>>>>> own and so it will be good to make sure we cover the basics here.
>>>>>
>>>>>
>>>>> Beyond the Hello-World, we wanted some different quickstarts. The
>>>>> "server" components that come to mind would be:
>>>>>
>>>>> *Secured CRUD + Push Integration (Java Sender)
>>>>> ** JAX-RS + PicketLink
>>>>> ** SpringMVC/Spring Security
>>>>> ** JAX-RS + Apache Camel
>>>>>
>>>>> These need to function on both JBoss AS 7.X and EAP.
>>>>>
>>>>> Josh, from the JDF team, has already said he wants to help on the
>>>>> server projects (especially the JAX-RS/PL and Spring ones). yay!
>>>>> Note: Josh already has a simple backend started that is used in JDF
>>>>> quickstarts that would be good to re-use to make it easier for
developers
>>>>> to transition from one to other.
>>>>>
>>>>>
>>>>> The goal would be the SERVER acts same to outside (identical REST
>>>>> endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring
vs.
>>>>> Camel))
>>>>>
>>>>> For these different servers, there would be mobile apps needed:
>>>>> * Android
>>>>> * Cordova
>>>>> * iOS
>>>>>
>>>>>
>>>>> The idea would be to keep them simple and straightforward as well,
>>>>> e.g. for iOS that means plain usage of NSURLConnection /
NSURLSession. But
>>>>> for the "push registration" of the client,
>>>>> the iOS-push SDK would be used (same/similar would apply to Cordova
>>>>> or Android). Similar to the above 'Hello World', the
quickstarts are going
>>>>> to be focused only on Push functionality, so for these we would leave
out
>>>>> pipes and such until later versions.
>>>>>
>>>>>
>>>>> I will be creating Epics and subtasks in JIRA for this.
>>>>>
>>>>> For the location of all these projects, I had this "uber
repo"
>>>>> location in mind:
>>>>> *
https://github.com/aerogear/aerogear-push-helloworld
>>>>> *
https://github.com/aerogear/aerogear-push-quickstarts
>>>>>
>>>>> Greetings,
>>>>> Matthias
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog:
http://matthiaswessendorf.wordpress.com/
>>>>> sessions:
http://www.slideshare.net/mwessendorf
>>>>> twitter:
http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog:
http://matthiaswessendorf.wordpress.com/
>>>> sessions:
http://www.slideshare.net/mwessendorf
>>>> twitter:
http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog:
http://matthiaswessendorf.wordpress.com/
>>> sessions:
http://www.slideshare.net/mwessendorf
>>> twitter:
http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog:
http://matthiaswessendorf.wordpress.com/
>> sessions:
http://www.slideshare.net/mwessendorf
>> twitter:
http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev