It *might* not be possible to use the same approach on both. Though,
interestingly, this is much easier on webkit1 so one way or another it
should be possible to make it work.
We need to merge support for webkitgtk1 upstream if we want upstream
patches to be required to not break it.
On Wednesday, 27 November 2013, Gonzalo Odiard wrote:
> Please remember we will be using web activities with Webkit1 for a while.
> Just a note, to be sure we don't go for something Webkit2 only.
>
> Gonzalo
>
>
> On Wed, Nov 27, 2013 at 10:16 AM, Rogelio Mita <
> rogeliom...@activitycentral.com <javascript:_e({}, 'cvml',
> 'rogeliom...@activitycentral.com');>> wrote:
>
>>
>> 2013/11/27 Daniel Narvaez <dwnarv...@gmail.com <javascript:_e({},
>> 'cvml', 'dwnarv...@gmail.com');>>
>>
>>> My summary email is still valid but for completeness... I'm not sure
>>> it's possible even from inside webkit to implement a non-racy
>>> window-object-cleared signal.
>>
>>
>> sounds good, I'm sure that python WebKit2 has to provide some solution to
>> this without having to go down a level, if our plan does not work, surely
>> on the list of webkit are going to tell us the right way, when I can, I
>> will try to do the plan
>>
>> Regards!
>>
>>
>> --
>> Roger
>>
>> Activity Central <http://activitycentral.com/>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org <javascript:_e({}, 'cvml',
>> 'Sugar-devel@lists.sugarlabs.org');>
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
--
Daniel Narvaez
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
