<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 25, 2014 at 3:06 PM, Hylke Bons <span dir="ltr"><<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div>
<div>On 25/02/2014 13:58, Sébastien Blanc
wrote:<br>
</div>
<blockquote type="cite">
<div><br>
<br>
Envoyé de mon iPhone</div>
<div><br>
Le Feb 25, 2014 à 14:36, Hylke Bons <<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>>
a écrit :<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>It's a good start.<br>
Before designing the actual form, maybe we should take a
step back and think about why we'd want to send a message?<br>
<br>
I can think of some cases:<br>
<br>
1. Testing whether your newly created app variant and push
network combination work correctly. It's good to have the
immediate confirmation right after you've created a new
application variant and have configured a push network. We
could have some kind of test dialogue, which can be skipped.<br>
</div>
</div>
</blockquote>
We can think about this bit most of the time just after creating
an app/variant you haven't any devices registered yet.<br>
<blockquote type="cite">
<div>
<div> </div>
</div>
</blockquote>
</blockquote></div>
No, but we need some code there to quickly register one as well, and
keep the setup flow going. We can link to the compose for from there
as well, we can decide on the details later once we decide if this
is something we'd like to have.</div></blockquote><div><br></div><div>Well, once you have a first device connected (which is most-likely the phone of the dude setting up the shindig), you can send a push.</div><div>
<br></div><div><br></div><div>Note, we also talked about generating markup (for the each variant overview) so the guy can copy/paste the code into his app, and launch it on the device:</div><div><a href="https://issues.jboss.org/browse/AGPUSH-260">https://issues.jboss.org/browse/AGPUSH-260</a><br>
</div><div><br></div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><br>
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">
<div>
<div>2. Debugging network issues and
general testing. A fixed message could do the trick, but
people may want to test all kinds of content to a variety of
devices to see if there are any issues.<br></div></div></blockquote></blockquote></div></div></blockquote><div>You can send a TEST to _your_ device (using the criteria (e.g. give it a funny unique alias/ID). That's already part of sebi's UI</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<div><blockquote type="cite"><blockquote type="cite"><div><div>
3. Code generation. Other than sending messages, Sebastien's
form looks like a good way to generate code that the backend
can use directly. It could be a sort of small visual design
tool, to make using the UPS even easier.<br></div></div></blockquote></blockquote></div></div></blockquote><div>Yes, we could generate the java-code for the backend. But really the goal is to also give apps an easy to actually deliver push (see original thread).</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<div><blockquote type="cite"><blockquote type="cite"><div><div>
</div>
</div>
</blockquote>
We have already some ideas around this ;) like generating the
client code for the registration (iOS/android/js) and also
generated curls for sending but that will be the next step.<br>
</blockquote></div>
Great!<span><font color="#888888"><br>
<br>
Hylke</font></span><div><div><br>
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">
<div>
<div> There may be more?<br>
Thoughts?<br>
<br>
Hylke<br>
<br>
<br>
<br>
On 25/02/2014 09:06, Sebastien Blanc wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div>I started to work on a new "Compose Message" page.
The idea is that you can add criterias to your message ,
as you can see here on this screenshot : </div>
<div><img src="http://s17.postimg.org/d6zfd2rqn/compose2.png" alt="compose2" height="420" width="388"><br>
</div>
<div class="gmail_extra">I've also deployed a live version
but *DICSLAIMER* this is just UI / Mockup work sending
will not work for now : <a href="http://newpush-sblanc.rhcloud.com" target="_blank">http://newpush-sblanc.rhcloud.com</a>
=> Select an App and you will have a "Copomse
Message" link on the next page.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Feedback is welcome.</div>
<div class="gmail_extra">Sebi</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Feb 24, 2014 at 1:25
PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>On Mon, Feb 24, 2014 at 12:52
PM, Hylke Bons <span dir="ltr"><<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Sounds good.<br>
Let me know if you need any help with
the mockup designs. ;)</div>
</div>
</blockquote>
</div>
<div>Sure, I will ASAP submit a "raw" mockup
on which you can work on.</div>
<div>What I would like is a dedicated page for
the "Compose Push Message" feature.</div>
<div><br>
</div>
<div>We wil have a criteria section to choose
to who we want to send the message. I really
like for instance how Jira do that like here
<a href="http://postimg.org/image/5ur2j9wh5/" target="_blank">http://postimg.org/image/5ur2j9wh5/</a> </div>
<div>In our case we could have the drop downs
for : "Variants", "Device Type", "Alias" and
"Categories"</div>
<div>And then below w will have a free text
area to send a custom value.</div>
<div>
<div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div> <span><font color="#888888"><br>
<br>
Hylke</font></span>
<div>
<div><br>
<br>
<br>
On 23/02/2014 12:08, Sebastien
Blanc wrote:<br>
</div>
</div>
</div>
<div>
<div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On
Sun, Feb 23, 2014 at 1:04
PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Hi,
<div><br>
</div>
<div>over the weekend
I spoke w/ a friend:
His company is doing
some mobile
(iOS/Android) apps
which also support
receiving push
notifications.</div>
<div><br>
</div>
<div>Two examples he
told me. After
receiving push
notification:<br>
</div>
<div><br>
</div>
<div>* One of their
apps basically
fetches the latest
version of a CSV
file, stored on a
public HTTP Server.<br>
</div>
<div><br>
</div>
<div>* Another app is
used to tell sales
guys new brochure
files (PDF) are
available on a
protected resource
of a webserver
(which they _can_
than download from
w/in the app, if the
like to)</div>
<div><br>
</div>
<div>The company build
a simple console
(PHP) which allows
them to send new
push messages, when
ever their customers
want to.<br>
</div>
<div><br>
</div>
<div>I showed them our
UnifiedPush Server
and its usage via
our AeroDoc example
(iOS / backend).
They really liked
the UnifiedPush
Server. Especially
that it does store
all the device
metadata. </div>
<div><br>
</div>
<div>But since a lot
of their mobile apps
don't have a backend
requirement, they
would still have to
use their own
console (which than
connects to UPS)
for submitting all
the push messages
they want.<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>This brings me to
[AGPUSH-38] and I
really think we
should implement
that feature. Not
only for sending
test messages! If
our UnifiedPush
Server allows its
users to simple send
push messages to all
of their mobile
apps, it would make
the server even more
attractive.</div>
<div><br>
</div>
<div>I regret a bit
that I was against
[AGPUSH-38] in the
beginning, I guess
that's due to my
Java enterprise
background, where
you typically find
complex setups, and
server talk to
servers :-(</div>
<div> <br>
</div>
<div>Anyways, now I
really think that
the UPS has to have
such a 'send push'
facility inside of
the Admin UI :-) I
believe that we
could reach way more
potential users with
something like that</div>
</div>
</blockquote>
<div>+9001 and I already
started thinking about
this for a while. I will
try to submit some
mockups/POCs this week
so we can discuss that
and I have quickly a
first working version on
master.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div> <br>
</div>
<div>Any thoughts?</div>
<div><br>
</div>
<div><br>
</div>
<div>Greetings,</div>
<div>Matthias </div>
<div><br>
</div>
<div><br>
</div>
<div>[AGPUSH-38] <a href="https://issues.jboss.org/browse/AGPUSH-38" target="_blank">https://issues.jboss.org/browse/AGPUSH-38</a></div>
<span><font color="#888888">
<div><br>
</div>
<div><br>
</div>
<div>-- <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>
</div>
</font></span></div>
<br>
_______________________________________________<br>
aerogear-dev mailing
list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
</blockquote>
</div>
</div>
</div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>aerogear-dev mailing list</span><br>
<span><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a></span><br>
<span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote></div><br><br clear="all"><div><br></div>-- <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>
</div></div>