Features/WebKit: Difference between revisions

Line 75:

The implementation proposed here is actually a simplification of the platform, as hulahop will be removed. Using WebKit instead of Mozilla in Browse is expected to result in a simplification of the codebase. If web technologies do catch on in other parts of Sugar, I predict that Browse will still retain its identity and requirements, due to considerations of cookies, SSL certificates, etc, which will not apply outside of web browser context. Finally, prerequisites aside, I expect the task of moving Browse from Mozilla to WebKit to be quite easy, and would generate experience and knowledge that would help towards the potential "HTML activities" direction.

==== New prototypes ====

Here is a demo of how pygi and webkit1 can be used to create a simple web browser in a python app: http://dev.laptop.org/~dsd/20110625/wkdemo.py

== Benefit to Sugar ==

@@ Line 75: / Line 75: @@
 The implementation proposed here is actually a simplification of the platform, as hulahop will be removed. Using WebKit instead of Mozilla in Browse is expected to result in a simplification of the codebase. If web technologies do catch on in other parts of Sugar, I predict that Browse will still retain its identity and requirements, due to considerations of cookies, SSL certificates, etc, which will not apply outside of web browser context. Finally, prerequisites aside, I expect the task of moving Browse from Mozilla to WebKit to be quite easy, and would generate experience and knowledge that would help towards the potential "HTML activities" direction.
+==== New prototypes ====
+Here is a demo of how pygi and webkit1 can be used to create a simple web browser in a python app: http://dev.laptop.org/~dsd/20110625/wkdemo.py
 == Benefit to Sugar ==