<div dir="ltr">+1 for option C but in the same time we should also have the "default" code snippet (only for the current variant) flow available. </div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 10, 2014 at 10:41 AM, Lukáš Fryč <span dir="ltr"><<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 Christos, <div><br></div><div>approach c) would add new screen (or rather modal) to the UI, but it would be most straightforward for users (and live coding demos!)</div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 10, 2014 at 9:07 AM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hi</div><div><br></div><div>answers inline,</div><div><br></div><div><div><span><div>On Nov 7, 2014, at 2:03 PM, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">Hey guys,<div><br></div><div>the feature of UPS Console where you can generate push-config.json under the Example implementation is pretty cool:</div><div><br></div><div><pre style="margin-top:0px;margin-bottom:10px;padding:0px;border:1px solid rgb(204,204,204);font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:11px;font-stretch:inherit;line-height:1.66666667;vertical-align:baseline;overflow:auto;word-break:break-all;word-wrap:break-word;color:rgb(51,51,51);border-top-left-radius:1px;border-top-right-radius:1px;border-bottom-right-radius:1px;border-bottom-left-radius:1px;background-color:rgb(85,85,85)!important"><code style="margin:0px;padding:0px;border-width:0px 0px 0px 2px;border-left-style:solid;border-left-color:rgb(17,17,17);font-size:12px;font-style:inherit;font-variant:inherit;font-weight:inherit;font-stretch:inherit;line-height:15px;vertical-align:baseline;color:rgb(238,238,238);border-top-left-radius:0px;border-top-right-radius:0px;border-bottom-right-radius:0px;border-bottom-left-radius:0px">{
"pushServerURL": "<a href="http://localhost:8080/ag-push/" target="_blank">http://localhost:8080/ag-push/</a>",
"android" : {
"senderID": "234",
"variantID": "a85cdfad-969c-4ab3-80bd-65a661bfd1a1",
"variantSecret": "da2ffc3a-96bf-4ee1-81fe-92721569c407"
}
}</code></pre></div><div>I would like to build on top of it.</div><div><br></div><div><br></div><div>Especially for demo purposes, it would be nice to generate multi-variant configs at once, such as bellow.</div><div><br></div><div>But the problem comes when you have more variants per one type, I have some ideas here:</div><div><br></div><div>a) generate multi-configs and include all variants with comments what config stands for what variant</div><div>b) generate multi-configs ONLY when there is at most one variant per type</div><div>c) use alternative approach and allow to generate push-config.json according to user-selected variants (selection such as in Send Push feature)</div></div></blockquote><div><br></div></span>not sure but if the purpose of 'push-config.json’ is to be consumed by client-sdk, having approach (c) may be preferable in the sense grabbing the 'selected' config and include in my ioS/Android/etc project </div><div><br></div><div>-</div><div>Christos</div><div><br><blockquote type="cite"><span><div dir="ltr"><div><br></div><div>WDYT?</div><div><br></div><div><pre style="margin-top:0px;margin-bottom:10px;padding:0px;border:1px solid rgb(204,204,204);font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:11px;font-stretch:inherit;line-height:1.66666667;vertical-align:baseline;overflow:auto;word-break:break-all;word-wrap:break-word;color:rgb(51,51,51);border-top-left-radius:1px;border-top-right-radius:1px;border-bottom-right-radius:1px;border-bottom-left-radius:1px;background-color:rgb(85,85,85)!important"><code style="margin:0px;padding:0px;border-width:0px 0px 0px 2px;border-left-style:solid;border-left-color:rgb(17,17,17);font-size:12px;font-style:inherit;font-variant:inherit;font-weight:inherit;font-stretch:inherit;line-height:15px;vertical-align:baseline;color:rgb(238,238,238);border-top-left-radius:0px;border-top-right-radius:0px;border-bottom-right-radius:0px;border-bottom-left-radius:0px">{
"pushServerURL": "<a href="http://localhost:8080/ag-push/" target="_blank">http://localhost:8080/ag-push/</a>",
"android" : {
"senderID": "234",
"variantID": "a85cdfad-969c-4ab3-80bd-65a661bfd1a1",
"variantSecret": "da2ffc3a-96bf-4ee1-81fe-92721569c407"
},
"ios" : {
...
},
"windows" : {
...
},
"firefoxos" : {
...
}
}</code></pre></div></div></span>
_______________________________________________<span><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></span></blockquote></div><br></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></div></div></div></div>
<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></blockquote></div><br></div>