[aerogear-dev] UPS: Wizard usage issue?

Sébastien Blanc scm.blanc at gmail.com
Wed Jun 24 13:18:13 EDT 2015



Envoyé de mon iPhone

> Le 24 juin 2015 à 19:13, Lukáš Fryč <lukas.fryc at gmail.com> a écrit :
> 
> +1 agree with Sebi
> 
> we can add a note that more variants can be added later once the wizard is finished
+1 good idea
> 
> st 24. 6. 2015 v 16:48 odesílatel Matthias Wessendorf <matzew at apache.org> napsal:
>> Ok, fair enough - I was just wondering, since we discussed that earlier and I just realized it, while working on the doc
>> 
>> 
>> 
>>> On Wed, Jun 24, 2015 at 4:42 PM, Daniel Passos <dpassos at redhat.com> wrote:
>>> I agree with Sebi. 90% (or more) will add only only variant, anyway I can't see any problem in go to the app and add another only (after wizard finished)
>>> 
>>>> On Wed, Jun 24, 2015 at 11:30 AM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>> I can see the need but honestly I think that 90% of the time when someone sets up a Push Application, he will start with only one variant to test. Then since he already knows how it works, he can add another variant the "raw" way.
>>>> We could add it but that could happen later (1.2 ?) but that is just my opinion.
>>>> 
>>>> Sebi
>>>> 
>>>> 
>>>>> On Wed, Jun 24, 2015 at 4:00 PM, Matthias Wessendorf <matzew at apache.org> wrote:
>>>>> Hi,
>>>>> 
>>>>> I just noticed (working on the doc) that when clicking through the wizard, I can only add one variant
>>>>> 
>>>>> Now, I am wondering if we should update the wizard, so that I can also add another vairant, inside of the wizard ? 
>>>>> 
>>>>> Or is that something we have done on design? That we just want just one variant to be created on the wizard - and for a second (and third, etc) variant, the user must go to the puah-app and add it there ? 
>>>>> 
>>>>> Thanks,
>>>>> Matze
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matthias Wessendorf 
>>>>> 
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> sessions: http://www.slideshare.net/mwessendorf
>>>>> twitter: http://twitter.com/mwessendorf
>>>>> 
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>> 
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> 
>>> 
>>> 
>>> -- 
>>> -- Passos
>>> 
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150624/b6c76c9e/attachment-0001.html 


More information about the aerogear-dev mailing list