5:37 a.m.
On Mon, Nov 10, 2014 at 10:42 AM, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
Burr, I feel the push-config.json is the best thing to avoid
maintenance
nightmare, since you can generate one config for all the platforms and
avoid different platform language hassle.
same here.
Or I totally miss something obvious, but avoiding all the hassle was one of
the reasons for the file. Also JSON is pretty much easy to import for every
"Cordova developer IDE" (I mean if that IDE does not understand JSON, it's
a more serious issue for the actual IDE)
On Fri, Nov 7, 2014 at 8:29 PM, Burr Sutter <bsutter(a)redhat.com> wrote:
> My only caution would be to avoid a “maintenance nightmare” - making sure
> these snippets match the needs of
> - Xcode developer
> - android studio developer
> - visual studio developer
> - Jboss developer studio with hybrid mobile tools developer
> - the cordova developer using their CLI
> - the ionic developer using their CLI
>
>
> On Nov 7, 2014, at 6:03 AM, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
>
> Hey guys,
>
> the feature of UPS Console where you can generate push-config.json under
> the Example implementation is pretty cool:
>
> {
> "pushServerURL": "http://localhost:8080/ag-push/",
> "android" : {
> "senderID": "234",
> "variantID": "a85cdfad-969c-4ab3-80bd-65a661bfd1a1",
> "variantSecret": "da2ffc3a-96bf-4ee1-81fe-92721569c407"
> }
> }
>
> I would like to build on top of it.
>
>
> Especially for demo purposes, it would be nice to generate multi-variant
> configs at once, such as bellow.
>
> But the problem comes when you have more variants per one type, I have
> some ideas here:
>
> a) generate multi-configs and include all variants with comments what
> config stands for what variant
> b) generate multi-configs ONLY when there is at most one variant per type
> c) use alternative approach and allow to generate push-config.json
> according to user-selected variants (selection such as in Send Push feature)
>
> WDYT?
>
> {
> "pushServerURL": "http://localhost:8080/ag-push/",
> "android" : {
> "senderID": "234",
> "variantID": "a85cdfad-969c-4ab3-80bd-65a661bfd1a1",
> "variantSecret": "da2ffc3a-96bf-4ee1-81fe-92721569c407"
> },
> "ios" : {
> ...
> },
> "windows" : {
> ...
> },
> "firefoxos" : {
> ...
> }
> }
>
> _______________________________________________
> 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