[aerogear-dev] UnifiedPush js client

Luke Holmquist lholmqui at redhat.com
Tue Sep 1 09:22:23 EDT 2015


On Mon, Aug 31, 2015 at 12:01 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> sure, let's do it - makes it obvious something changed
>
> Yea,  before i do the bump, i'll have to see what else we want/need to
remove.  I know notifier we deprecated.  I'll start a separate ML thread
for all this 3.0 talk and what the future might look like for the JS Lib



> On Mon, Aug 31, 2015 at 5:29 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> The new Repo is now here https://github.com/aerogear/aerogear-js-push !!
>>
>> I'll create some JIRA's to update the Readme, update aerogear.org,
>> remove the code from the main repo, etc...
>>
>>
>> Question.  Will this require a major version bump once i remove the code?
>>  i'm thinking yes
>>
>> On Mon, Aug 31, 2015 at 5:11 AM, Corinne Krych <corinnekrych at gmail.com>
>> wrote:
>>
>>> +1
>>> This way, we're getting closer to native libs approach with separate libs
>>>
>>> On 31 August 2015 at 10:55, Lukáš Fryč <lukas at fryc.eu> wrote:
>>>
>>>> You are right Luke, this start to make more and more sense :-)
>>>>
>>>> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>> so i decided to take a gander at the push client lib in the
>>>>> aerogear.js project.   Currently if someone would like to use it,  they
>>>>> have a couple options.
>>>>>
>>>>> 1. download the whole lib,
>>>>> 2. download a custom build from the website
>>>>> 3. download a custom build from bower
>>>>> 4. create a custom build from source
>>>>>
>>>>> In the past i think i was against breaking out pieces of the JS lib
>>>>> into separate repo's since we could just use the AeroGearComponents repo i
>>>>> created for custom builds.  But i think with the state of the JS lib(not
>>>>> sure where it's going), it might make sense to, at least with the push
>>>>> lib(perhaps the simplePush polyfill also) to break those out into separate
>>>>> repo's similar to the other client projects.
>>>>>
>>>>> I think the starting vision of the project has changed, so perhaps
>>>>> this change is good.(this should probably be a whole separate thread)
>>>>>
>>>>> Now that Chrome and Safari have push in the browser, FF is getting it
>>>>> also very soon,  it's possible this part of the library will be used more
>>>>>
>>>>>
>>>>> thoughts?
>>>>>
>>>>> -Luke
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150901/064171fc/attachment-0001.html 


More information about the aerogear-dev mailing list