<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 11, 2014 at 1:36 PM, Andres Galante <span dir="ltr"><<a href="mailto:agalante@redhat.com" target="_blank">agalante@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Better show than tell, but I have nothing to show at the moment :(<br>
<br>
The problem with the current console is that the sidebar as a main navigation doesn't allow for sub navigation or expansions. We are researching with Matt and Gabriel applying paternally and how to adapt it to mobile products. </blockquote><div><br></div><div>ah, you mean generic - not specific to this POC.</div><div><br></div><div>For this POC, let's just focus on the RESTful endpoints, not the UI at the moment - it's a proof of concepts, not more</div><div><br></div><div>-M</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There has been a lot of talk internally in the UX team but I haven't been able to start with it until yesterday.<br>
<br>
Since changing the console is not a short term goal, please give me a couple of days to work on it and I'll share as I have things to share.<br>
<span class="im HOEnZb"><br>
----- Original Message -----<br>
From: "Matthias Wessendorf" <<a href="mailto:matzew@apache.org">matzew@apache.org</a>><br>
To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
</span><div class="HOEnZb"><div class="h5">Sent: Thursday, December 11, 2014 4:53:28 AM<br>
Subject: Re: [aerogear-dev] [POC] Unified Geo Server<br>
<br>
<br>
<br>
On Wed, Dec 10, 2014 at 9:04 PM, Andres Galante < <a href="mailto:agalante@redhat.com">agalante@redhat.com</a> > wrote:<br>
<br>
<br>
+1<br>
We are thinking of this kind of scenarios for the next step on the console UI.<br>
<br>
Can you explain more?<br>
<br>
<br>
<br>
The way we have the navigation now it is not flexible enough. Hopefully I'll have updates on console UX to share with you soon :)<br>
<br>
<br>
----- Original Message -----<br>
From: "Corinne Krych" < <a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a> ><br>
To: "AeroGear Developer Mailing List" < <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> ><br>
Sent: Wednesday, December 10, 2014 4:55:56 PM<br>
Subject: Re: [aerogear-dev] [POC] Unified Geo Server<br>
<br>
Nice POC indeed, it makes things more concrete.<br>
<br>
Looking at the the similar process for UGS and UPS and thinking we might need similar mini/micro services, I think eventually we will benefit having a form of aggregator where you say: create an app for UPS with plugin UGS, under the cover, 2 app ids are created and unified with one appId + a map of corresponding app ids.<br>
With the same idea some of the admin console for creating app could be mutualised.<br>
<br>
This is more a ‘for the future’ improvement and does not interfere with your POC.<br>
<br>
++<br>
Corinne<br>
<br>
> On 10 Dec 2014, at 17:12, Sebastien Blanc < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> > wrote:<br>
><br>
><br>
><br>
> On Wed, Dec 10, 2014 at 4:46 PM, Andres Galante < <a href="mailto:agalante@redhat.com">agalante@redhat.com</a> > wrote:<br>
> Nice work Sebastien!<br>
> If you I can help with app or console design, please let me know.<br>
> Thanks ! A good strategy would probably to follow the Push Server and LiveOak (Angular/patternfly) model.<br>
><br>
> ----- Original Message -----<br>
> From: "Sebastien Blanc" < <a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a> ><br>
> To: "AeroGear Developer Mailing List" < <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> ><br>
> Sent: Wednesday, December 10, 2014 12:28:43 PM<br>
> Subject: Re: [aerogear-dev] [POC] Unified Geo Server<br>
><br>
><br>
><br>
> On Wed, Dec 10, 2014 at 4:23 PM, Erik Jan de Wit < <a href="mailto:edewit@redhat.com">edewit@redhat.com</a> > wrote:<br>
><br>
><br>
> Really nice, looks great already, one question how do I use the data<br>
> from the geo search to send push notifications?<br>
> When the device registers to the geo server, it also provides an "alias". The idea is that the developer has to use the same "alias" when registering to the UPS, then it's up to the backend app to retrieve the aliases for the geoserver and use these as criteria when sending a push notif to UPS.<br>
> It tried to described that here : <a href="https://github.com/sebastienblanc/unified-geo-server#integration-with-push" target="_blank">https://github.com/sebastienblanc/unified-geo-server#integration-with-push</a><br>
><br>
> One idea for the alias, is to use the Keycloak (or whatever auth system) username as alias to have it somehow "unified"<br>
><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
<br>
--<br>
Matthias Wessendorf<br>
<br>
blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div>