Line 1: |
Line 1: |
− | <noinclude>{{TOCright}} | + | <noinclude> |
| [[Category:Feature Page Incomplete]] | | [[Category:Feature Page Incomplete]] |
− | [[Category:Feature|WebKit]] | + | [[Category:FeatureLanded|WebKit]] |
| <!-- You can add categories to tie features back to real deployments/schools requesting them, for example | | <!-- You can add categories to tie features back to real deployments/schools requesting them, for example |
| [[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> | | [[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> |
Line 11: |
Line 11: |
| == Owner == | | == Owner == |
| * Planned/proposed by [[User:DanielDrake|Daniel Drake]] | | * Planned/proposed by [[User:DanielDrake|Daniel Drake]] |
− | * Implemented by: ? (volunteer here!) | + | * Implemented by: [[User:Erikos|Simon Schampijer]] and [[User:Manuq|Manuel Quiñones]] |
| | | |
| == Current status == | | == Current status == |
− | * Targeted release: (SUGAR_VERSION) | + | * Targeted release: 0.96 |
− | * Last updated: (DATE) | + | * Last updated: 31.01.12 |
− | * Percentage of completion: XX% | + | * Percentage of completion: 80% |
| | | |
| == Detailed Description == | | == Detailed Description == |
Line 22: |
Line 22: |
| Browse and related components currently embed Mozilla XUL/Gecko as their backend, however, Mozilla embedding has typically been neglected and buggy, causing a maintenance headache for us. It is now [https://groups.google.com/forum/#!topic/mozilla.dev.embedding/c_NMcO-N8wo/discussion actively discouraged] by Mozilla developers, who are focusing all their efforts on Firefox. From the perspective of a fairly regular open-source project, Mozilla's direction is also [http://lists.sugarlabs.org/archive/sugar-devel/2011-June/031865.html questionable on other points]. | | Browse and related components currently embed Mozilla XUL/Gecko as their backend, however, Mozilla embedding has typically been neglected and buggy, causing a maintenance headache for us. It is now [https://groups.google.com/forum/#!topic/mozilla.dev.embedding/c_NMcO-N8wo/discussion actively discouraged] by Mozilla developers, who are focusing all their efforts on Firefox. From the perspective of a fairly regular open-source project, Mozilla's direction is also [http://lists.sugarlabs.org/archive/sugar-devel/2011-June/031865.html questionable on other points]. |
| | | |
− | WebKit is a promising alternative, which is (by nature) an embeddable web engine. It is used in Apple Safari and Google Chrome and various other projects. | + | WebKit is a promising alternative, which is (by nature) an embeddable web engine. It is used in Apple Safari, Google Chrome, Epiphany (GNOME browser) and various other projects. |
| | | |
| === Existing prototype: Surf === | | === Existing prototype: Surf === |
Line 74: |
Line 74: |
| On the other hand, the loss of Sugar's web browser is current: it screwed up a lot during late 2010 (xulrunner-1.9 / Fedora 14 timeframe), is now limping along again, has completely broken again (as of mid-2011, xulrunner-2.0 and Fedora 15 timeframe) and is no doubt up for a bumpy ride ahead. The solution can be designed and implemented now. Let's not mix a relatively straightforward, clearly defined and sorely needed task with one that is exploratory and uncertain. | | On the other hand, the loss of Sugar's web browser is current: it screwed up a lot during late 2010 (xulrunner-1.9 / Fedora 14 timeframe), is now limping along again, has completely broken again (as of mid-2011, xulrunner-2.0 and Fedora 15 timeframe) and is no doubt up for a bumpy ride ahead. The solution can be designed and implemented now. Let's not mix a relatively straightforward, clearly defined and sorely needed task with one that is exploratory and uncertain. |
| | | |
− | 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, 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. | + | 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 == | | == Benefit to Sugar == |