[cordova] Push Plugin : externalise Push config
by Sebastien Blanc
Hi all,
I was thinking of that : as we are adding more and more support for Push
Networks (iOS, Android, Microsoft, firefoxOS, Amazon), the configuration
list is getting longer and longer in the code. What about creating a
separate json file containing this config that the plugin could consume ?
like, pushconfig.json :
{
pushServerURL: "https://javaoneups-sblanc.rhcloud.com/ag-push/",
android: {
senderID: "313664704978",
variantID: "39d64fb1-6c82-4638-9d02-3fbbbad5ba28",
variantSecret: "d2e4e60a-e3d9-4db7-acee-0d18abc953a4"
},
ios : {
....
},
simplePush : {
...
},
microsoft : {
...
},
amazon : {
...
}
}
That should not be mandatory as we could still use the "inline" style.
wdyt ?
Sebi
10 years, 12 months
hello world branch
by Erik Jan de Wit
Hi,
As we already added new functionality to the hello world example ( windows support) there is a branch for the 1.0.x version. When you fix some issues be sure to specify in you PR that it should go to the 1.0.x branch as well as master!
Cheers,
Erik Jan
10 years, 12 months
some cookbook recipes need some backend
by Corinne Krych
Hello Guys
To complete our cookbook repositories: iOS, web, android and cordova (still under eric private repo), I’d like to have a aerogear-backend-cookbook. We already have some demos which requires backend. I’ve put them together in:
https://github.com/corinnekrych/aerogear-backend-cookbook
Each app has a separate build and is independent. For new I’ve put together:
AeroDoc
PushQuickstart (as submodules)
Buddies
ProductInventory (oauth2 keycloak) kind of helloWorld app, very simple
Next addition, I’m thinking to do a Shoot’nShare file upload Server using Keycloak. So we can have a more complete demo of AeroGear OAuth2 and Keycloak.
Thoughts?
++
Corinne
10 years, 12 months
Handling 1.x repositories
by Christos Vasilakis
Hi all,
as we approach 2.0 releases in iOS we are evaluating the faith of our 1.x repository [1]. Currently the functionality has been splitted in separate repositories[2][3] with more to come in subsequent releases . Since other platforms follow the same approach of separation, would like to get your view on how you will handle the ‘1.x’ repo?
We were thinking to:
a) promote the master repo to an '1.x branch’ and update the repos README.md to be clear that is our 1.x branch
b) use the ‘master’ branch with just a single README.md that provides links to the different repos.
Wdyth?
-
Christos
[1] https://github.com/aerogear/aerogear-ios
[2] https://github.com/aerogear/aerogear-ios-http
[3] https://github.com/aerogear/aerogear-ios-oauth2
11 years
iOS meeting
by Corinne Krych
Hello Swifter and iOS lovers,
Here is the proposed agenda of our next meeting which will take place Tuesday 16 September at 2pm (CEST - UTC + 2hours)
soclap.com/p/aerogear_ios_meeting_11sept2014
Feel free to add topics to it and join us if you want to discuss with us next 2.0 iOS release.
++
Corinne
11 years
