10:31 a.m.
Hey everyone,
Here's my initial version of the AeroGeer Unified Push Server Admin UI:
https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push...
This work is based off of the features/usecases and lexicon described in
http://aerogear.org/docs/specs/aerogear-server-push/ and Matthias's
earlier wireframes.
Features:
* Developer can register a |Push Application|
* Developer can add a |Mobile Variant| for different operation systems
* Developer can remove a |Mobile Variant|
* Developer can remove |Push Application|
Currently Missing features (these will be added in the next iteration):
* Enroll |Developer|
* Remove |Developer|
* |Developer| can disable Push Notifications to selected |Mobile
Variant Instances|
* |Developer| sends /Push Notification Messages/
Potentially controversial changes:
- Using "(Hybrid Web)" as a variant name instead of "SimplePush".
Matthias and I already had a short exchange here on the mailing list
about this change, hopefully the way this is used in these wireframes
will shed some light on why I think this is a better choice.
- Checkboxes instead of a list box for variants. Since there are only
a few variant types, we don't need a full fledged list, and we can
simply use some checkboxes to toggle variants.
Let me know if you have any comments or questions!
Sources can be found in https://github.com/hbons/aerogear-design.
Looking forward to your feedback,
Hylke
12:11 p.m.
Hi Hylke,
Nice work! I like the look of the Admin UI
- Using "(Hybrid Web)" as a variant name instead of
"SimplePush".
I'd vote for changing "Hybrid Web" to just
"Web". For me the UI is pretty
clear that this is about adding/configuring Push Networks, and I would not
know what a "Hybrid Web" push network is.
/Dan
On 3 June 2013 17:31, Hylke Bons <hbons(a)redhat.com> wrote:
Hey everyone,
Here's my initial version of the AeroGeer Unified Push Server Admin UI:
https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push...
This work is based off of the features/usecases and lexicon described in
http://aerogear.org/docs/specs/aerogear-server-push/ and Matthias's
earlier wireframes.
Features:
- Developer can register a Push Application
- Developer can add a Mobile Variant for different operation systems
- Developer can remove a Mobile Variant
- Developer can remove Push Application
Currently Missing features (these will be added in the next iteration):
- Enroll Developer
- Remove Developer
- Developer can disable Push Notifications to selected Mobile Variant
Instances
- Developer sends *Push Notification Messages*
Potentially controversial changes:
- Using "(Hybrid Web)" as a variant name instead of "SimplePush".
Matthias and I already had a short exchange here on the mailing list about
this change, hopefully the way this is used in these wireframes will shed
some light on why I think this is a better choice.
- Checkboxes instead of a list box for variants. Since there are only a
few variant types, we don't need a full fledged list, and we can simply use
some checkboxes to toggle variants.
Let me know if you have any comments or questions!
Sources can be found in https://github.com/hbons/aerogear-design.
Looking forward to your feedback,
Hylke
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
12:21 p.m.
On 03/06/2013 18:11, Daniel Bevenius wrote:
Hi Hylke,
Nice work! I like the look of the Admin UI
Thanks Daniel!
>- Using "(Hybrid Web)" as a variant name instead of
"SimplePush".
I'd vote for changing "Hybrid Web" to just "Web". For me the UI
is
pretty clear that this is about adding/configuring Push Networks, and
I would not know what a "Hybrid Web" push network is.
/Dan
Yes, I tend to agree. Perhaps we can add a short description of what
"Web" entails (Cordova, "plain" web etc.). Compared to the other
platforms, this may not be immediately clear from the beginning.
Something to think about.
Thanks,
Hylke
On 3 June 2013 17:31, Hylke Bons <hbons(a)redhat.com
<mailto:hbons@redhat.com>> wrote:
Hey everyone,
Here's my initial version of the AeroGeer Unified Push Server
Admin UI:
https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push...
This work is based off of the features/usecases and lexicon
described in http://aerogear.org/docs/specs/aerogear-server-push/
and Matthias's earlier wireframes.
Features:
* Developer can register a |Push Application|
* Developer can add a |Mobile Variant| for different operation
systems
* Developer can remove a |Mobile Variant|
* Developer can remove |Push Application|
Currently Missing features (these will be added in the next
iteration):
* Enroll |Developer|
* Remove |Developer|
* |Developer| can disable Push Notifications to selected |Mobile
Variant Instances|
* |Developer| sends /Push Notification Messages/
Potentially controversial changes:
- Using "(Hybrid Web)" as a variant name instead of
"SimplePush". Matthias and I already had a short exchange here on
the mailing list about this change, hopefully the way this is used
in these wireframes will shed some light on why I think this is a
better choice.
- Checkboxes instead of a list box for variants. Since there are
only a few variant types, we don't need a full fledged list, and
we can simply use some checkboxes to toggle variants.
Let me know if you have any comments or questions!
Sources can be found in https://github.com/hbons/aerogear-design.
Looking forward to your feedback,
Hylke
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@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
12:41 p.m.
Oops. I had this response sitting here and I never sent it. I agree with Dan though.
On Jun 3, 2013, at 10:31 AM, Hylke Bons <hbons(a)redhat.com> wrote:
Hey everyone,
Here's my initial version of the AeroGeer Unified Push Server Admin UI:
https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push...
This work is based off of the features/usecases and lexicon described in
http://aerogear.org/docs/specs/aerogear-server-push/ and Matthias's earlier
wireframes.
Features:
Developer can register a Push Application
Developer can add a Mobile Variant for different operation systems
Developer can remove a Mobile Variant
Developer can remove Push Application
Currently Missing features (these will be added in the next iteration):
Enroll Developer
Remove Developer
Developer can disable Push Notifications to selected Mobile Variant Instances
Developer sends Push Notification Messages
Potentially controversial changes:
- Using "(Hybrid Web)" as a variant name instead of "SimplePush".
Matthias and I already had a short exchange here on the mailing list about this change,
hopefully the way this is used in these wireframes will shed some light on why I think
this is a better choice.
I think I would prefer to call this Web / Hybrid or something like that. The way it's
written now somewhat implies to me it's only hybrid but maybe that's just me.
Also, I would not use "Mozilla SimplePush URL" since you could, and for a while,
would likely have your own SimplePush server. Eventually, we hopefully would have to add
entries for Mozilla Network, Chrome Network, etc.… but until then it will likely be our
server to allow cross-browser web push.
- Checkboxes instead of a list box for variants. Since there are
only a few variant types, we don't need a full fledged list, and we can simply use
some checkboxes to toggle variants.
Let me know if you have any comments or questions!
Sources can be found in https://github.com/hbons/aerogear-design.
Looking forward to your feedback,
Hylke
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
12:45 p.m.
Yes, I tend to agree. Perhaps we can add a short description of what
"Web" entails (Cordova, "plain" web etc.).
I would treat Cordova native:
-Cordova-Android-Variant
-Cordova-iOS-Variant
Of course, with SimplePush, the apps can receive notifications as well, but
the "background" (not actively running), would not be possible (at least
now)
-Matthias
Compared to the other platforms, this may not be immediately clear
from
the beginning. Something to think about.
Thanks,
Hylke
On 3 June 2013 17:31, Hylke Bons <hbons(a)redhat.com> wrote:
> Hey everyone,
>
> Here's my initial version of the AeroGeer Unified Push Server Admin UI:
>
>
https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push...
>
> This work is based off of the features/usecases and lexicon described in
> http://aerogear.org/docs/specs/aerogear-server-push/ and Matthias's
> earlier wireframes.
>
>
> Features:
>
> - Developer can register a Push Application
> - Developer can add a Mobile Variant for different operation systems
> - Developer can remove a Mobile Variant
> - Developer can remove Push Application
>
> Currently Missing features (these will be added in the next iteration):
>
> - Enroll Developer
> - Remove Developer
> - Developer can disable Push Notifications to selected Mobile Variant
> Instances
> - Developer sends *Push Notification Messages*
>
>
> Potentially controversial changes:
>
> - Using "(Hybrid Web)" as a variant name instead of
"SimplePush".
> Matthias and I already had a short exchange here on the mailing list about
> this change, hopefully the way this is used in these wireframes will shed
> some light on why I think this is a better choice.
> - Checkboxes instead of a list box for variants. Since there are only a
> few variant types, we don't need a full fledged list, and we can simply use
> some checkboxes to toggle variants.
>
> Let me know if you have any comments or questions!
> Sources can be found in https://github.com/hbons/aerogear-design.
>
> Looking forward to your feedback,
>
> Hylke
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing
listaerogear-dev@lists.jboss.orghttps://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
12:48 p.m.
On 03/06/2013 18:41, Kris Borchers wrote:
I think I would prefer to call this Web / Hybrid or something like
that. The way it's written now somewhat implies to me it's only hybrid
but maybe that's just me. Also, I would not use "Mozilla SimplePush
URL" since you could, and for a while, would likely have your own
SimplePush server. Eventually, we hopefully would have to add entries
for Mozilla Network, Chrome Network, etc.... but until then it will
likely be our server to allow cross-browser web push.
Fair point, I will remove "Mozilla" from the wireframe. It would indeed
be nice to have some presets in the future and we have room to that.
Thanks,
Hylke
12:49 p.m.
Hi,
over all this looks really nice!
A few comments:
* (Hybrid) Web ===> Web
* Moz SimplePush URL ===> SimplePush Network URL
at least that's my current thought about the "terms" :-)
-MAtthias
On Mon, Jun 3, 2013 at 5:31 PM, Hylke Bons <hbons(a)redhat.com> wrote:
Hey everyone,
Here's my initial version of the AeroGeer Unified Push Server Admin UI:
https://raw.github.com/hbons/aerogear-design/master/aerogear_unified_push...
This work is based off of the features/usecases and lexicon described in
http://aerogear.org/docs/specs/aerogear-server-push/ and Matthias's
earlier wireframes.
Features:
- Developer can register a Push Application
- Developer can add a Mobile Variant for different operation systems
- Developer can remove a Mobile Variant
- Developer can remove Push Application
Currently Missing features (these will be added in the next iteration):
- Enroll Developer
- Remove Developer
- Developer can disable Push Notifications to selected Mobile Variant
Instances
- Developer sends *Push Notification Messages*
Potentially controversial changes:
- Using "(Hybrid Web)" as a variant name instead of "SimplePush".
Matthias and I already had a short exchange here on the mailing list about
this change, hopefully the way this is used in these wireframes will shed
some light on why I think this is a better choice.
- Checkboxes instead of a list box for variants. Since there are only a
few variant types, we don't need a full fledged list, and we can simply use
some checkboxes to toggle variants.
Let me know if you have any comments or questions!
Sources can be found in https://github.com/hbons/aerogear-design.
Looking forward to your feedback,
Hylke
_______________________________________________
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
12:53 p.m.
On 03/06/2013 18:45, Matthias Wessendorf wrote:
I would treat Cordova native:
-Cordova-Android-Variant
-Cordova-iOS-Variant
Of course, with SimplePush, the apps can receive notifications as
well, but the "background" (not actively running), would not be
possible (at least now)
-Matthias
So do Cordova hybrid based apps use their respective "native" push
networks (Apple's/Google's) SimplePush only? (or either?) I guess
non-hybrid Web apps can only use SimplePush?
Hylke
12:59 p.m.
On Mon, Jun 3, 2013 at 7:53 PM, Hylke Bons <hbons(a)redhat.com> wrote:
On 03/06/2013 18:45, Matthias Wessendorf wrote:
> I would treat Cordova native:
> -Cordova-Android-Variant
> -Cordova-iOS-Variant
>
> Of course, with SimplePush, the apps can receive notifications as
> well, but the "background" (not actively running), would not be
> possible (at least now)
>
> -Matthias
>
So do Cordova hybrid based apps use their respective "native" push
networks (Apple's/Google's) SimplePush only? (or either?) I guess
non-hybrid Web apps can only use SimplePush?
I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
variants.
You can use our SimplePush libraries, with Cordova. But.... you would NOT
receive a notification, if the application is not running/open
SimplePush is perfect, right now, for "Mobile Web", and would be fine for
Cordova, where we do (yet) support the native bindings (e.g. BlackBerry,
Windoze etc)
-Matthias
Hylke
_______________________________________________
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
1 p.m.
Once Mozilla sticks SimplePush into FirefoxOS - you will also receive
messages, on a FFOS devices, when the app is NOT running :)
But, we are very early here :)
Ideally, there will be native support in Chrome etc, in the near future, as
Kris already mentioned
-M
On Mon, Jun 3, 2013 at 7:59 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
On Mon, Jun 3, 2013 at 7:53 PM, Hylke Bons <hbons(a)redhat.com> wrote:
> On 03/06/2013 18:45, Matthias Wessendorf wrote:
> > I would treat Cordova native:
> > -Cordova-Android-Variant
> > -Cordova-iOS-Variant
> >
> > Of course, with SimplePush, the apps can receive notifications as
> > well, but the "background" (not actively running), would not be
> > possible (at least now)
> >
> > -Matthias
> >
>
> So do Cordova hybrid based apps use their respective "native" push
> networks (Apple's/Google's) SimplePush only? (or either?) I guess
> non-hybrid Web apps can only use SimplePush?
>
I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
variants.
You can use our SimplePush libraries, with Cordova. But.... you would NOT
receive a notification, if the application is not running/open
SimplePush is perfect, right now, for "Mobile Web", and would be fine for
Cordova, where we do (yet) support the native bindings (e.g. BlackBerry,
Windoze etc)
-Matthias
>
> Hylke
> _______________________________________________
> 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
1:03 p.m.
On 03/06/2013 18:59, Matthias Wessendorf wrote:
So do Cordova hybrid based apps use their respective
"native" push
networks (Apple's/Google's) SimplePush only? (or either?) I guess
non-hybrid Web apps can only use SimplePush?
I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
variants.
You can use our SimplePush libraries, with Cordova. But.... you would
NOT receive a notification, if the application is not running/open
SimplePush is perfect, right now, for "Mobile Web", and would be fine
for Cordova, where we do (yet) support the native bindings (e.g.
BlackBerry, Windoze etc)
-Matthias
Thanks, that makes sense.
I'll keep this in mind for the next iteration and think about how we
want to represent Cordova in these categories (if at all, perhaps it's a
client implementation detail).
Hylke
1:06 p.m.
On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com> wrote:
On 03/06/2013 18:59, Matthias Wessendorf wrote:
So do Cordova hybrid based apps use their respective "native" push
> networks (Apple's/Google's) SimplePush only? (or either?) I guess
> non-hybrid Web apps can only use SimplePush?
>
I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
variants.
You can use our SimplePush libraries, with Cordova. But.... you would
NOT receive a notification, if the application is not running/open
SimplePush is perfect, right now, for "Mobile Web", and would be fine
for Cordova, where we do (yet) support the native bindings (e.g.
BlackBerry, Windoze etc)
-Matthias
Thanks, that makes sense.
I'll keep this in mind for the next iteration and think about how we want
to represent Cordova in these categories (if at all, perhaps it's a client
implementation detail).
yeah, I'd probably not even mention Cordova in the UI;
In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush).
Hylke
_______________________________________________
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
1:32 a.m.
Hello Hylke,
here is the "Admin UI" epic (incl. its sub-tasks):
https://issues.jboss.org/browse/AGPUSH-66
can you update, e.g. assign issues to yourself, add new one, modify
existing tickets, as needed ?
Thanks!
Matthias
On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com> wrote:
> On 03/06/2013 18:59, Matthias Wessendorf wrote:
>
> So do Cordova hybrid based apps use their respective "native" push
>> networks (Apple's/Google's) SimplePush only? (or either?) I guess
>> non-hybrid Web apps can only use SimplePush?
>>
>
> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
> variants.
>
> You can use our SimplePush libraries, with Cordova. But.... you would
> NOT receive a notification, if the application is not running/open
>
>
> SimplePush is perfect, right now, for "Mobile Web", and would be fine
> for Cordova, where we do (yet) support the native bindings (e.g.
> BlackBerry, Windoze etc)
>
> -Matthias
>
>
> Thanks, that makes sense.
>
> I'll keep this in mind for the next iteration and think about how we want
> to represent Cordova in these categories (if at all, perhaps it's a client
> implementation detail).
>
yeah, I'd probably not even mention Cordova in the UI;
In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush).
>
>
> Hylke
>
> _______________________________________________
> 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
7:16 a.m.
For the admin UI, do we have a browser(s) target. If this is possibly going to be a
"module" in AS , then developers in certain enterprises might be stuck using old
versions of IE( < than 9 )
On Jun 4, 2013, at 2:32 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
Hello Hylke,
here is the "Admin UI" epic (incl. its sub-tasks):
https://issues.jboss.org/browse/AGPUSH-66
can you update, e.g. assign issues to yourself, add new one, modify existing tickets, as
needed ?
Thanks!
Matthias
On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org> wrote:
On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com> wrote:
On 03/06/2013 18:59, Matthias Wessendorf wrote:
> So do Cordova hybrid based apps use their respective "native" push
> networks (Apple's/Google's) SimplePush only? (or either?) I guess
> non-hybrid Web apps can only use SimplePush?
>
> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova variants.
>
> You can use our SimplePush libraries, with Cordova. But.... you would NOT receive a
notification, if the application is not running/open
>
>
> SimplePush is perfect, right now, for "Mobile Web", and would be fine for
Cordova, where we do (yet) support the native bindings (e.g. BlackBerry, Windoze etc)
>
> -Matthias
>
Thanks, that makes sense.
I'll keep this in mind for the next iteration and think about how we want to
represent Cordova in these categories (if at all, perhaps it's a client implementation
detail).
yeah, I'd probably not even mention Cordova in the UI;
In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush).
Hylke
_______________________________________________
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
7:49 a.m.
On Jun 4, 2013, at 7:16 AM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
For the admin UI, do we have a browser(s) target. If this is
possibly going to be a "module" in AS , then developers in certain enterprises
might be stuck using old versions of IE( < than 9 )
Well, AeroGear doesn't support IE < 9 so ...
On Jun 4, 2013, at 2:32 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
> Hello Hylke,
>
> here is the "Admin UI" epic (incl. its sub-tasks):
> https://issues.jboss.org/browse/AGPUSH-66
>
> can you update, e.g. assign issues to yourself, add new one, modify existing tickets,
as needed ?
>
> Thanks!
> Matthias
>
>
>
>
> On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>
> On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com> wrote:
> On 03/06/2013 18:59, Matthias Wessendorf wrote:
>
>> So do Cordova hybrid based apps use their respective "native" push
>> networks (Apple's/Google's) SimplePush only? (or either?) I guess
>> non-hybrid Web apps can only use SimplePush?
>>
>> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
variants.
>>
>> You can use our SimplePush libraries, with Cordova. But.... you would NOT receive
a notification, if the application is not running/open
>>
>>
>> SimplePush is perfect, right now, for "Mobile Web", and would be fine
for Cordova, where we do (yet) support the native bindings (e.g. BlackBerry, Windoze etc)
>>
>> -Matthias
>>
>
> Thanks, that makes sense.
>
> I'll keep this in mind for the next iteration and think about how we want to
represent Cordova in these categories (if at all, perhaps it's a client implementation
detail).
>
> yeah, I'd probably not even mention Cordova in the UI;
> In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush).
>
>
>
>
> Hylke
>
> _______________________________________________
> 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
8:03 a.m.
PLUS PLUS
On Tue, Jun 4, 2013 at 2:49 PM, Kris Borchers <kris(a)redhat.com> wrote:
On Jun 4, 2013, at 7:16 AM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
For the admin UI, do we have a browser(s) target. If this is possibly
going to be a "module" in AS , then developers in certain enterprises might
be stuck using old versions of IE( < than 9 )
Well, AeroGear doesn't support IE < 9 so ...
On Jun 4, 2013, at 2:32 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
Hello Hylke,
here is the "Admin UI" epic (incl. its sub-tasks):
https://issues.jboss.org/browse/AGPUSH-66
can you update, e.g. assign issues to yourself, add new one, modify
existing tickets, as needed ?
Thanks!
Matthias
On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
>
>
> On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com> wrote:
>
>> On 03/06/2013 18:59, Matthias Wessendorf wrote:
>>
>> So do Cordova hybrid based apps use their respective "native" push
>>> networks (Apple's/Google's) SimplePush only? (or either?) I guess
>>> non-hybrid Web apps can only use SimplePush?
>>>
>>
>> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
>> variants.
>>
>> You can use our SimplePush libraries, with Cordova. But.... you would
>> NOT receive a notification, if the application is not running/open
>>
>>
>> SimplePush is perfect, right now, for "Mobile Web", and would be fine
>> for Cordova, where we do (yet) support the native bindings (e.g.
>> BlackBerry, Windoze etc)
>>
>> -Matthias
>>
>>
>> Thanks, that makes sense.
>>
>> I'll keep this in mind for the next iteration and think about how we
>> want to represent Cordova in these categories (if at all, perhaps it's a
>> client implementation detail).
>>
>
> yeah, I'd probably not even mention Cordova in the UI;
> In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush).
>
>
>
>>
>>
>> Hylke
>>
>> _______________________________________________
>> 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
_______________________________________________
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
8:09 a.m.
I'm all for IE > 9 ( actually would be nice to kill that too, but… ) , just
wanted to see if this had a different requirement
On Jun 4, 2013, at 9:03 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
PLUS PLUS
On Tue, Jun 4, 2013 at 2:49 PM, Kris Borchers <kris(a)redhat.com> wrote:
On Jun 4, 2013, at 7:16 AM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
> For the admin UI, do we have a browser(s) target. If this is possibly going to be a
"module" in AS , then developers in certain enterprises might be stuck using old
versions of IE( < than 9 )
Well, AeroGear doesn't support IE < 9 so ...
>
>
>
>
> On Jun 4, 2013, at 2:32 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>> Hello Hylke,
>>
>> here is the "Admin UI" epic (incl. its sub-tasks):
>> https://issues.jboss.org/browse/AGPUSH-66
>>
>> can you update, e.g. assign issues to yourself, add new one, modify existing
tickets, as needed ?
>>
>> Thanks!
>> Matthias
>>
>>
>>
>>
>> On Mon, Jun 3, 2013 at 8:06 PM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>>
>>
>> On Mon, Jun 3, 2013 at 8:03 PM, Hylke Bons <hbons(a)redhat.com> wrote:
>> On 03/06/2013 18:59, Matthias Wessendorf wrote:
>>
>>> So do Cordova hybrid based apps use their respective "native" push
>>> networks (Apple's/Google's) SimplePush only? (or either?) I guess
>>> non-hybrid Web apps can only use SimplePush?
>>>
>>> I'd use the native Push APIs (GCM / APNs), for my iOS/Android Cordova
variants.
>>>
>>> You can use our SimplePush libraries, with Cordova. But.... you would NOT
receive a notification, if the application is not running/open
>>>
>>>
>>> SimplePush is perfect, right now, for "Mobile Web", and would be
fine for Cordova, where we do (yet) support the native bindings (e.g. BlackBerry, Windoze
etc)
>>>
>>> -Matthias
>>>
>>
>> Thanks, that makes sense.
>>
>> I'll keep this in mind for the next iteration and think about how we want to
represent Cordova in these categories (if at all, perhaps it's a client implementation
detail).
>>
>> yeah, I'd probably not even mention Cordova in the UI;
>> In a later guide, we can show, how to do Cordova (APNs/GCM/SimplePush).
>>
>>
>>
>>
>> Hylke
>>
>> _______________________________________________
>> 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
_______________________________________________
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
4006
days inactive
4009
days old
17 comments
6 participants
participants (6)
-
Daniel Bevenius -
Douglas Campos -
Hylke Bons -
Kris Borchers -
Lucas Holmquist -
Matthias Wessendorf