[Sugar-devel] Adding compatibility in webactivity to webkit1

[Daniel Narvaez]

I'm unconvinced that it will be a short term workaround. It will be hard to
get rid of.

We are implicitly adding support for webkit 1.8 (API 1) to sugar-web. We
might have to write sugar-web code which is webkit1 specific. People will
write activities which runs on 1.8. They will use non
forward-compatible APIs. They will cut and paste python wrappers to run on
webkit1. For a long time webkit <= 1.8 will be the main platform really,
given the deployments situation.

I think this is an important decision. Even if it's not our intention we
will either send the message that we would like people to start using the
web toolkit on deployed software or that it's still a cutting edge
technology, targeted to developers and very recent software. The are
advantages and disadvantages of both approaches, the point is more that we
should be aware of the choice we are making.

On Wednesday, 27 November 2013, Gonzalo Odiard wrote:

> I am not opposed to alternative implementations,
> if we can "keep it simple".
>
> This is a workaround for a problem, in the end, we want remove it,
> when is not needed anymore.
>
> Gonzalo
>
>
> On Wed, Nov 27, 2013 at 2:22 PM, Rogelio Mita <
> rogeliomita at activitycentral.com <javascript:_e({}, 'cvml',
> 'rogeliomita at activitycentral.com');>> wrote:
>
>> Nice!, I quickly looked at the patch and I urged try to encapsulate the
>> all logic of webkit2 and the webkit1 in separate modules, using a luck of
>> strategy pattern or do something polymorphic, but I notice that it is a
>> decision not yet taken (as Daniel says), I doubt whether to spend time on
>> this for that reason, you will say, however when this decision is finally
>> decided, I would like to make note of this style refactor to have clean
>> webactivity module, which is relatively new and keep small, you think?
>>
>> Regards!
>>
>>
>> 2013/11/27 Gonzalo Odiard <gonzalo at laptop.org <javascript:_e({}, 'cvml',
>> 'gonzalo at laptop.org');>>
>>
>>>
>>> On Wed, Nov 27, 2013 at 1:04 PM, Daniel Narvaez <dwnarvaez at gmail.com<javascript:_e({}, 'cvml', 'dwnarvaez at gmail.com');>
>>> > wrote:
>>>
>>>> I think it's good to have this upstream because otherwise changes to
>>>> sugar-web will easily break webkit1 support.
>>>>
>>>> I'm not completely convinced we should support webkit1 yet. I'm worried
>>>> it will be pretty painful to maintain. It should be possible to port
>>>> webkitgtk 2.2 to Fedora 18...
>>>>
>>>>
>>> Maybe, but have many other dependencies to update.
>>>
>>> Another alternative is find what is crashing in webkit2 and solve it,
>>> but is out of my knowledge.
>>>
>>> Gonzalo
>>>
>>>
>>> _______________________________________________
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org <javascript:_e({}, 'cvml',
>>> 'Sugar-devel at lists.sugarlabs.org');>
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>
>>
>> --
>> Roger
>>
>> Activity Central <http://activitycentral.com/>
>>
>
>

-- 
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20131128/de2db8a9/attachment.html>