[~sebastienblanc] [~agalante]
Guys, I'd like to know your opinion how this feature should be implemented. In the old UI, the "generate push-config.json" button is little bit independent from the rest of samples.
Andres, to get you into a picture, {{push-config.json}} is an alternative mechanism how to configure Cordova based applications. You need to pass store the JSON file such as [1] side by side your Cordova project sources. It will be loaded automatically when you don't specify configuration in your code.
But, the problem is that {{push-config.json}} contains configuration for several platforms, not just one (see the sample [1]). In the old UI we've decided to have a separated button that opened a dialog for variants selection for which you wanted to generate the {{push-config.json}}. Then you was able to download the configuration file or copy its contents.
You can see full discussion about this feature here: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Cordova-push-config-json-generated-in-UPS-Console-multiple-variants-tp9799p9824.html
My question is whether this is something we want to re-do in a new UI or something that should be re-designed. Could you possibly work this feature in the mockup?
[1] https://github.com/jboss-mobile/unified-push-helloworld/blob/master/cordova/www/push-config.json
|
