[Sugar-devel] About web activities, webkit2 and backward compatibility
Question for the sugar-web-activities framework developers: * With the actual implementation, do we _really_ need webkit2? You can say, why? We already decided that! I know, but thinking in the following months: * If we continue going with webkit2, the only way to develop web activities, will be sugar-build. No real users can use that activities in a xo with sugar for at least 6 months more. * This means, there are little incentive for developers to create activities without users, or like in the case of Lionel, port custom (and working) web activities to the new framework. * If we use webkit, we can modify the way sugar-0.100 identify a web activity in the activity.info file, to make it backward compatible, and include the needed classes in the .xo, to use them if is executed in a old sugar. * We _need_ activities using the framework to make sure all is working ok, and check if we have all the needed pieces. I repeat, I know this was decided, but I think these are good enough arguments. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On 21 May 2013 20:31, Gonzalo Odiard wrote: > Question for the sugar-web-activities framework developers: > > * With the actual implementation, do we _really_ need webkit2? > Probably not. It should be easy to give it a try, the API didn't change that much. > * If we continue going with webkit2, the only way to develop web > activities, will be sugar-build. No real users can use that activities in a > xo with sugar for at least 6 months more. > You will also need to figure out how to provide the equivalent of the shell apisocket inside the activity. Same interface and partially different implementation might work. > I repeat, I know this was decided, but I think these are good enough > arguments. > Personally I'm going to focus on building something that it's even worth considering to backport. We are pretty far from that goal yet. I don't see anything wrong with someone writing a backward compatible activity which can run the sugar-html-* stuff though. I think we also said that when we made the decision. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 4:04 PM, Daniel Narvaez wrote: > On 21 May 2013 20:31, Gonzalo Odiard wrote: > >> Question for the sugar-web-activities framework developers: >> >> * With the actual implementation, do we _really_ need webkit2? >> > > Probably not. It should be easy to give it a try, the API didn't change > that much. > > >> * If we continue going with webkit2, the only way to develop web >> activities, will be sugar-build. No real users can use that activities in a >> xo with sugar for at least 6 months more. >> > > You will also need to figure out how to provide the equivalent of the > shell apisocket inside the activity. Same interface and partially different > implementation might work. > > Good point. > I repeat, I know this was decided, but I think these are good enough >> arguments. >> > > Personally I'm going to focus on building something that it's even worth > considering to backport. We are pretty far from that goal yet. I don't see > anything wrong with someone writing a backward compatible activity which > can run the sugar-html-* stuff though. I think we also said that when we > made the decision. > Great. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 12:31 PM, Gonzalo Odiard wrote: > Question for the sugar-web-activities framework developers: > > * With the actual implementation, do we _really_ need webkit2? > > You can say, why? We already decided that! > > I know, but thinking in the following months: > > * If we continue going with webkit2, the only way to develop web activities, > will be sugar-build. No real users can use that activities in a xo with > sugar for at least 6 months more. webkit2 is included in F18 and is in OLPC builds. Has anyone checked if it is good enough to run the latest webapp stuff? There may be no need to go back to webkit1 if you want to continue on this path. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
> webkit2 is included in F18 and is in OLPC builds. Has anyone checked > if it is good enough to run the latest webapp stuff? There may be no > need to go back to webkit1 if you want to continue on this path. > > I can'see webkit2 installed in 13.2.0, what is the package? [olpc@xo-1e-88-13 logs]$ rpm -qa | grep -i webkit webkitgtk3-1.10.2-3.fc18.armv7hl webkitgtk-1.10.2-3.fc18.armv7hl Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 1:44 PM, Gonzalo Odiard wrote: > >> webkit2 is included in F18 and is in OLPC builds. Has anyone checked >> if it is good enough to run the latest webapp stuff? There may be no >> need to go back to webkit1 if you want to continue on this path. >> > > I can'see webkit2 installed in 13.2.0, what is the package? webkitgtk3 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
> webkitgtk3 > I think that is webkit, no webkit2 Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 2:02 PM, Gonzalo Odiard wrote: > >> webkitgtk3 > > > I think that is webkit, no webkit2 How are you coming to that conclusion? I just checked the spec file, webkit2 compilation is enabled, and the lib appears installed as /usr/lib/libwebkit2gtk-3.0.so.18.0.5 It is not as new as the version in F19 of course, but as far as I know nobody has investigated as to whether that really matters. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
I was confused by the rpm number, my mistake. [olpc@xo-1e-88-13 logs]$ rpm -ql webkitgtk3 | grep typelib /usr/lib/girepository-1.0/JSCore-3.0.typelib /usr/lib/girepository-1.0/WebKit-3.0.typelib /usr/lib/girepository-1.0/WebKit2-3.0.typelib Looks like the two libraries are packaged in the same rpm. On Tue, May 21, 2013 at 5:06 PM, Daniel Drake wrote: > On Tue, May 21, 2013 at 2:02 PM, Gonzalo Odiard > wrote: > > > >> webkitgtk3 > > > > > > I think that is webkit, no webkit2 > > How are you coming to that conclusion? > I just checked the spec file, webkit2 compilation is enabled, and the > lib appears installed as /usr/lib/libwebkit2gtk-3.0.so.18.0.5 > > It is not as new as the version in F19 of course, but as far as I know > nobody has investigated as to whether that really matters. > > Daniel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tuesday, May 21, 2013 05:09:38 PM Gonzalo Odiard wrote: > > I was confused by the rpm number, my mistake. > > > [olpc@xo-1e-88-13 logs]$ rpm -ql webkitgtk3 | grep typelib > /usr/lib/girepository-1.0/JSCore-3.0.typelib > /usr/lib/girepository-1.0/WebKit-3.0.typelib > /usr/lib/girepository-1.0/WebKit2-3.0.typelib > Does sugar-build really need to clone and build Webkit2? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On 21 May 2013 23:43, Daniel Francis wrote: > On Tuesday, May 21, 2013 05:09:38 PM Gonzalo Odiard wrote: > > > > I was confused by the rpm number, my mistake. > > > > > > [olpc@xo-1e-88-13 logs]$ rpm -ql webkitgtk3 | grep typelib > > /usr/lib/girepository-1.0/JSCore-3.0.typelib > > /usr/lib/girepository-1.0/WebKit-3.0.typelib > > /usr/lib/girepository-1.0/WebKit2-3.0.typelib > > > > Does sugar-build really need to clone and build Webkit2? > I think for development we really want the stable 2.0 API. I'd rather not have to worry about API changes. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
> I think for development we really want the stable 2.0 API. I'd rather not have to worry about API changes. What webkit2 features are we using? Websockets works ok on webkit. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Wednesday, 22 May 2013, Gonzalo Odiard wrote: > > I think for development we really want the stable 2.0 API. I'd rather > not have to worry about API changes. > > What webkit2 features are we using? Websockets works ok on webkit. > I was not talking about webkit1 but about the webkit2 version in Fedora. There has been a lot of API changes in webkit2 between the Fedora version and the latest which we are shipping in sugar-build. From a quick look to release announcements it seems like the Fedora 18 webkit2 might be missing even some basic stuff like get_uri... If we went with webkit1 that would not be a problem. But I still think we should go with webkit2 for the stuff we are adding to toolkit and use webkit1 for the backward compatible activity. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
Tried to run a current web activity in current olpc build, 13.2.0 os6. I copied sugar-toolkit-gtk3/src/sugar3/activity/htmlactivity.py inside the activity, and changed activity.info accordingly. The activity fails in line: self._web_view.show() https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/htmlactivity.py#L52 with a segmentation fault: Terminated by signal 11, pid 1436 data (None, ', mode 'w' at 0xd67a18>, 'bc05e2b23867858d4df2bb97d5088312e4dffa1e') 2013/5/22 Daniel Narvaez : > On Wednesday, 22 May 2013, Gonzalo Odiard wrote: >> >> > I think for development we really want the stable 2.0 API. I'd rather >> > not have to worry about API changes. >> >> What webkit2 features are we using? Websockets works ok on webkit. > > > I was not talking about webkit1 but about the webkit2 version in Fedora. > There has been a lot of API changes in webkit2 between the Fedora version > and the latest which we are shipping in sugar-build. From a quick look to > release announcements it seems like the Fedora 18 webkit2 might be missing > even some basic stuff like get_uri... > > If we went with webkit1 that would not be a problem. But I still think we > should go with webkit2 for the stuff we are adding to toolkit and use > webkit1 for the backward compatible activity. > > > -- > Daniel Narvaez > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
2013/5/22 Manuel Quiñones :
> Tried to run a current web activity in current olpc build, 13.2.0 os6.
>
> I copied sugar-toolkit-gtk3/src/sugar3/activity/htmlactivity.py inside
> the activity, and changed activity.info accordingly. The activity
> fails in line:
>
> self._web_view.show()
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity/htmlactivity.py#L52
>
> with a segmentation fault:
>
> Terminated by signal 11, pid 1436 data (None, ',
> mode 'w' at 0xd67a18>, 'bc05e2b23867858d4df2bb97d5088312e4dffa1e')
Tested as separate script, this gives segfault too:
from gi.repository import Gtk
from gi.repository import WebKit2
class HTMLActivity(Gtk.Window):
def __init__(self):
Gtk.Window.__init__(self)
self._web_view = WebKit2.WebView()
self.add(self._web_view)
self._web_view.show()
html_activity = HTMLActivity()
html_activity.connect("delete-event", Gtk.main_quit)
html_activity.show()
Gtk.main()
> 2013/5/22 Daniel Narvaez :
>> On Wednesday, 22 May 2013, Gonzalo Odiard wrote:
>>>
>>> > I think for development we really want the stable 2.0 API. I'd rather
>>> > not have to worry about API changes.
>>>
>>> What webkit2 features are we using? Websockets works ok on webkit.
>>
>>
>> I was not talking about webkit1 but about the webkit2 version in Fedora.
>> There has been a lot of API changes in webkit2 between the Fedora version
>> and the latest which we are shipping in sugar-build. From a quick look to
>> release announcements it seems like the Fedora 18 webkit2 might be missing
>> even some basic stuff like get_uri...
>>
>> If we went with webkit1 that would not be a problem. But I still think we
>> should go with webkit2 for the stuff we are adding to toolkit and use
>> webkit1 for the backward compatible activity.
>>
>>
>> --
>> Daniel Narvaez
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> .. manuq ..
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
