1:03 p.m.
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" : {
...
}
}
8:29 p.m.
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/
<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/
<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
10:42 a.m.
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.
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
12:37 p.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
9:07 a.m.
Hi
answers inline,
On Nov 7, 2014, at 2:03 PM, 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)
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
-
Christos
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
10:41 a.m.
+1 Christos,
approach c) would add new screen (or rather modal) to the UI, but it would
be most straightforward for users (and live coding demos!)
On Mon, Nov 10, 2014 at 9:07 AM, Christos Vasilakis <cvasilak(a)gmail.com>
wrote:
Hi
answers inline,
On Nov 7, 2014, at 2:03 PM, 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)
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
-
Christos
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
10:48 a.m.
+1 for option C but in the same time we should also have the "default" code
snippet (only for the current variant) flow available.
On Mon, Nov 10, 2014 at 10:41 AM, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
+1 Christos,
approach c) would add new screen (or rather modal) to the UI, but it would
be most straightforward for users (and live coding demos!)
On Mon, Nov 10, 2014 at 9:07 AM, Christos Vasilakis <cvasilak(a)gmail.com>
wrote:
> Hi
>
> answers inline,
>
> On Nov 7, 2014, at 2:03 PM, 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)
>
>
> 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
>
> -
> Christos
>
>
> 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
10:56 a.m.
Sounds good, I created https://issues.jboss.org/browse/AGPUSH-1096
On Mon, Nov 10, 2014 at 10:48 AM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
+1 for option C but in the same time we should also have the
"default"
code snippet (only for the current variant) flow available.
On Mon, Nov 10, 2014 at 10:41 AM, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
> +1 Christos,
>
> approach c) would add new screen (or rather modal) to the UI, but it
> would be most straightforward for users (and live coding demos!)
>
> On Mon, Nov 10, 2014 at 9:07 AM, Christos Vasilakis <cvasilak(a)gmail.com>
> wrote:
>
>> Hi
>>
>> answers inline,
>>
>> On Nov 7, 2014, at 2:03 PM, 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)
>>
>>
>> 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
>>
>> -
>> Christos
>>
>>
>> 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
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
3461
days inactive
3464
days old
7 comments
5 participants
participants (5)
-
Burr Sutter -
Christos Vasilakis -
Lukáš Fryč -
Matthias Wessendorf -
Sebastien Blanc