Any good JavaScript testing framework?
by Yahor Radtsevich
Hello all!
I am from the JBoss Tools team, and I am developing CordovaSim - a
simulator for Cordova-based hybrid projects.
Now we are looking for a framework for JavaScript testing. We are planning
to use it mostly to test various Cordova API methods.
Which framework do you use in the Aerogear development?
How about Jasmine?
I will appreciate any suggestions.
--
Thank you in advance!
Yahor Radtsevich
13 years
Selective Send: Payload message object
by Matthias Wessendorf
Hi,
Right now, the "selective send" has (besides "query" components), one
"message" object, that contains the entire payload (see [1]).
That message/payload object does include the metadata for the SimplePush
clients:
"message": {
"key":"value",
"key2":"other value",
"alert":"HELLO!",
"simple-push":
{ "SomeCategory":"version=123", "anotherCategory":"version=456"}
}
I'd like to move the "simple-push" one level up, like:
"message": {
"key":"value",
"key2":"other value",
"alert":"HELLO!"},
"simple-push":{
"SomeCategory":"version=123",
........}
}
That way the "simple-push" data is not "pushed" to Android/iOS (that does
not make sense anyways :-)) It also makes writing "pure" simple-push
messages easier and also eases up processing on the server.
-Matthias
[1]
https://github.com/aerogear/aerogear.org/blob/master/docs/specs/aerogear-...
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
13 years
Aerogear-Android Push Branch with Maven
by Tommy McCarthy
Hey everyone,
I've been looking to rebuild aerogear-android for my OpenShift instance. Currently, the older master branch is live, and I want to update to the push branch due to the changes in the code (namely unifiedpush).
So, I'm trying to build aerogear-android's push branch with "mvn package". My repo is up to date.
The error I'm getting is:
"package com.google.android.gms.gcm does not exist", and then further has issues with Registrar.java, looking for the GCM classes that aren't there.
I have the SDK deployer installed, and the symlinks for "aapt" and other tools. I've tried a few things including changing the SDK version in the POM, and a few other things that my Google-fu has uncovered.
Any suggestions for me to be able to proceed? Thanks in advance!
Apologies if it's something simple I'm overlooking ;)
---
Tommy McCarthy
13 years
ProDoctor rename (was: Re: Repo Names (was: Re: Push "all inclusive" demo))
by Matthias Wessendorf
As said somewhere (mailing list thread), IRC, not only the repo would need
a rename, the project itself as well.
So, feel free to suggested new names for this "topic demo"
-Matthias
On Fri, Jun 28, 2013 at 10:55 PM, Jay Balunas <jbalunas(a)redhat.com> wrote:
>
> On Jun 28, 2013, at 2:54 AM, Corinne Krych wrote:
>
> > According to that thread:
> >
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-project-d...
> >
> > it's a topic example to be more exact :)
> >
> > * Topic examples: I believe these should have a similar requirement as
> the showcase example. The point of the topic example is to cover a
> specific topic, not specific individual clients.
> >
> > Should we have a naming convention?
> >
> > I suggest something like:
> >
> > aerogear-topic-example-prodoctor-*
>
> I think we could likely just go with:
>
> aerogear-prodoctor-* as I don't think the distinction between example
> files will mean much to most people. The README should address the
> difference imo though.
>
> This also leads to the repo planning thread we discussed creating. Lets
> kick that off early next week as I think for the most part we are in
> general agreement with the "example planning thread".
>
> > aerogear-topic-example-todo-*
> >
> > By the way I put TODO "demo" in the same category. Do you all agree?
> > Given we find another name for ProDoctor, maybe TensioLeads or just
> Leads because the business focus could be anything else.
> >
> > wdyt?
> >
> > ++
> > Corinne
> >
> > On Jun 28, 2013, at 7:57 AM, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
> >
> >> On Thu, Jun 27, 2013 at 11:11 PM, Summers Pittman <supittma(a)redhat.com>
> wrote:
> >>> On 06/27/2013 03:23 PM, Corinne Krych wrote:
> >>>> Hello all,
> >>>>
> >>>> Before renaming, I suggest we choose which category we want to tag
> ProDoctor. From Jay proposal:
> >>>> - showcase demo
> >>>> - topics demos
> >>>> - quickstart
> >>>> - one off examples.
> >>>>
> >>>> Given those categories, I think ProDoctor is between topics demos and
> a first draft for showcase demo.
> >>> +1 to it being a topics demo.
> >>
> >> I agree on topic demo.
> >>
> >>
> >>
> >>>>
> >>>> Do we want to keep the topics demos category ? As Pete Muir pointed
> out, does it make sense?
> >>>>
> >>>> or do we prefer to enhance our quick start/tutorials with different
> scenarios? Maybe working on the recipes/cookbook approach as defined by
> passos.
> >>>>
> >>>> We could recycle ProDoctor into several quickstarts (simplify code)
> and make difference cases: selective push, broadcast etc…
> >>>> We could also reuse some material for showcase demo and off course
> make it blogpost.
> >>>>
> >>>> Several options. Depending on the choice we then get a name.
> >>>> Just wondering which category does the TODO app falls in?
> >>>>
> >>>> ++
> >>>> Corinne
> >>>>
> >>>>
> >>>> On Jun 27, 2013, at 7:08 PM, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
> >>>>
> >>>>> On Thu, Jun 27, 2013 at 7:01 PM, Kris Borchers <kris(a)redhat.com>
> wrote:
> >>>>>> On Jun 27, 2013, at 11:57 AM, Matthias Wessendorf <
> matzew(a)apache.org> wrote:
> >>>>>>
> >>>>>>> Any more thoughts on this ?
> >>>>>>>
> >>>>>>> Looks like right now the favorite is:
> >>>>>>> aerogear-prodoctor-**
> >>>>>> Definitely thought we were changing the name so probably not good
> to name the repo that.
> >>>>> exactly :)
> >>>>>
> >>>>> name (and repo) needs to be changed :)
> >>>>>
> >>>>> Any "proposals" ?
> >>>>>
> >>>>>>> Perhaps we can find something "better" for the "prodoctor"...
> >>>>>>>
> >>>>>>> On Tue, Jun 25, 2013 at 11:40 AM, Matthias Wessendorf <
> matzew(a)apache.org> wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Tue, Jun 25, 2013 at 10:52 AM, Corinne Krych <
> corinnekrych(a)gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>> It's depend what we want to do with it.
> >>>>>>>>>
> >>>>>>>>> If it's to demo Push feature only I would suggest:
> >>>>>>>>> aerogear-push-demo-backend/ios/web/android
> >>>>>>>>>
> >>>>>>>>> If we want to demo more features we could call it simply
> >>>>>>>>> aerogear-prodoctor-…
> >>>>>>>>
> >>>>>>>> yeah, works for me too. It's simple :)
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> ++
> >>>>>>>>> Corinne
> >>>>>>>>>
> >>>>>>>>> On Jun 25, 2013, at 9:54 AM, Matthias Wessendorf <
> matzew(a)apache.org>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> this is not really a quick start :) So I am asking for new names.
> >>>>>>>>>
> >>>>>>>>> Once have have decided on "better" repo names for this, I'll
> create a JIRA
> >>>>>>>>> so that the repos will be renamed to better reflect what they
> actually
> >>>>>>>>> are...
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Thoughts?
> >>>>>>>>>
> >>>>>>>>> -Matthias
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Jun 11, 2013, at 10:45 AM, Sebastien Blanc <
> scm.blanc(a)gmail.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hey !
> >>>>>>>>>> We would like to provide, in a quite short delay (coming 2
> weeks) a demo
> >>>>>>>>>> showing all the different bits of the "push" world , meaning :
> >>>>>>>>>> client | push server | JEE Backend App
> >>>>>>>>>>
> >>>>>>>>>> We already have the push server (aerogear-unified-push-server)
> : so we
> >>>>>>>>>> need a client (iOS and maybe also Android) and a simple JEE
> backend
> >>>>>>>>>> application. The backend app will mostly be scaffolded and
> will use the
> >>>>>>>>>> aerogear-unified-push-java-client to send messages to the Push
> Server.
> >>>>>>>>>>
> >>>>>>>>>> Then of course, we need to think about an idea of the
> application itself.
> >>>>>>>>>> It needs to stay really simple, show how we can send
> selectively and should
> >>>>>>>>>> be a bit "business" related.
> >>>>>>>>>>
> >>>>>>>>>> So, I came up with an idea this morning that we can discuss
> here, of
> >>>>>>>>>> course if you have any other idea don't hesitate to share it.
> >>>>>>>>>>
> >>>>>>>>>> Push Demo
> >>>>>>>>>>
> >>>>>>>>>> Introduction
> >>>>>>>>>>
> >>>>>>>>>> Prodoctor is a company in the health care industry, selling a
> >>>>>>>>>> revolutionary tensiometer. Their clients are doctors. Prodoctor
> has several
> >>>>>>>>>> sales agents all over the United States. At the headquarters,
> they have
> >>>>>>>>>> their "first line" sales department doing cold calls all along
> the day. As
> >>>>>>>>>> soon they have a concrete lead, they use their Prodoctor Admin
> app to filter
> >>>>>>>>>> out available sales Agents available in the lead area. They can
> then send
> >>>>>>>>>> them a push notification.
> >>>>>>>>>>
> >>>>>>>>>> The sales agent receives the notification on their mobile
> device that a
> >>>>>>>>>> new lead is available. The agent will handle the lead by
> "accepting" the
> >>>>>>>>>> notification informing the other agents that the lead has been
> processed.
> >>>>>>>>>>
> >>>>>>>>>> The client app
> >>>>>>>>>>
> >>>>>>>>>> The client consist of a list of leads : a lead can be "open" or
> "in
> >>>>>>>>>> process", leads "in process" of other sales are not visible.
> >>>>>>>>>>
> >>>>>>>>>> optional : when the client tap a lead it appears on a map
> >>>>>>>>>>
> >>>>>>>>>> The client has a status that he can set: STANDBY | WITH_CLIENT
> |PTO
> >>>>>>>>>> The client has a location
> >>>>>>>>>> The client has an alias
> >>>>>>>>>>
> >>>>>>>>>> Prodoctor Admin client
> >>>>>>>>>>
> >>>>>>>>>> The admin client can create a new lead :
> >>>>>>>>>>
> >>>>>>>>>> A lead consist of a name and a location
> >>>>>>>>>>
> >>>>>>>>>> The admin client can query for Sales Agents based on :
> >>>>>>>>>>
> >>>>>>>>>> Status
> >>>>>>>>>> Location
> >>>>>>>>>>
> >>>>>>>>>> The admin client can assign a lead to a selection (1..n) of
> sales agents,
> >>>>>>>>>> this will send out the notifications.
> >>>>>>>>>>
> >>>>>>>>>> The admin client manage the Sales Agents DB.
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>>
> >>>>>>>>>> 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
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> 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
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> 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
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >
> >
> > _______________________________________________
> > 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
13 years
aerogear-unified-push-java-client 0.1.0 released
by Bruno Oliveira
Good morning peeps,
Just to let you know, aerogear-unified-push-java-client 0.1.0 was
released. Now we just need to be patient and wait for maven central.
Congrats to Sebi and Matthias.
--
abstractj
13 years
Push "all inclusive" demo
by Sebastien Blanc
Hey !
We would like to provide, in a quite short delay (coming 2 weeks) a demo
showing all the different bits of the "push" world , meaning :
client | push server | JEE Backend App
We already have the push server (aerogear-unified-push-server) : so we need
a client (iOS and maybe also Android) and a simple JEE backend application.
The backend app will mostly be scaffolded and will use the
aerogear-unified-push-java-client to send messages to the Push Server.
Then of course, we need to think about an idea of the application itself.
It needs to stay really simple, show how we can send selectively and
should be a bit "business" related.
So, I came up with an idea this morning that we can discuss here, of course
if you have any other idea don't hesitate to share it.
Push Demo <https://gist.github.com/sebastienblanc/5755548#introduction>
Introduction
Prodoctor is a company in the health care industry, selling a revolutionary
tensiometer. Their clients are doctors. Prodoctor has several sales agents
all over the United States. At the headquarters, they have their "first
line" sales department doing cold calls all along the day. As soon they
have a concrete lead, they use their Prodoctor Admin app to filter out
available sales Agents available in the lead area. They can then send them
a push notification.
The sales agent receives the notification on their mobile device that a new
lead is available. The agent will handle the lead by "accepting" the
notification informing the other agents that the lead has been processed.
<https://gist.github.com/sebastienblanc/5755548#the-client-app>The client
app
1. The client consist of a list of leads : a lead can be "open" or "in
process", leads "in process" of other sales are not visible.
- optional : when the client tap a lead it appears on a map
1. The client has a status that he can set: STANDBY | WITH_CLIENT |PTO
2. The client has a location
3. The client has an alias
<https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>Prodoctor
Admin client
1. The admin client can create a new lead :
- A lead consist of a name and a location
1. The admin client can query for Sales Agents based on :
- Status
- Location
1.
The admin client can assign a lead to a selection (1..n) of sales
agents, this will send out the notifications.
2.
The admin client manage the Sales Agents DB.
13 years
Android: Eclipse issue with the "Push"
by Matthias Wessendorf
Hi,
I did a download of the latest Android SDK
(adt-bundle-mac-x86_64-20130522), and did follow our instructions here:
https://github.com/aerogear/aerogear-android/blob/push/README.md
I did the maven-sdk-deployer etc, all good. the branch was compiling with
Maven. Great!
Now, with Eclipse, I did follow these instructions:
http://staging.aerogear.org/docs/guides/GetStartedAndroidEclipse/
But once I finished these steps, I am getting compiler errors. For instance
on the Pipeline.java, I am getting these issues:
import android.app.Fragment;
import android.support.v4.app.FragmentActivity;
import com.google.common.collect.HashMultimap;
import com.google.common.collect.Multimap;
While I think that the android.** related import issues are most likely
related to the fact that this is perhaps now wrong (2.3.3):
http://staging.aerogear.org/docs/guides/img/android_eclipse_import_005.png
But the Google Collections are also not resolving.
I guess the "Import" in Eclipse is not really reflecting the description of
the guava dependency in the pom.xml file.
Besides the google collections, I also noticed that other classes (like "
com.google.android.gms.gcm.GoogleCloudMessaging") are not being resolved.
Is there a way that all these "required" dependencies are picked up
automatically, by the Eclipse IDE? Or do I have to import all
dependencies, by hand ?
Thanks!
Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
13 years
