158
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − + Line 24:
Line 24: − Webified+ + + + + + + + +
Summer of Code/2010/Abstract Browser (view source)
Revision as of 19:51, 25 March 2010
, 19:51, 25 March 2010no edit summary
lucian
lucian
* '''What is your IRC nickname?'''
* '''What is your IRC nickname?'''
lucian. backups are lucian1900 and sindbad1900
lucian
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
English and Romanian, either is fine.
English and Romanian, either is fine.
* '''What is the name of your project?'''
* '''What is the name of your project?'''
AbstractBrowser
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''
Several people have expressed concern about xulrunner/hulahop and Browse maintainability. Also, there is a perception that webkit is faster and uses less memory than gecko. Various benchmarks do seem to show webkit to be superior, but results are inconclusive. Also, the Surf activity is significantly faster than Browse on XOs.
It would be good if Browse could switch between browser engines, if not at runtime at least with little effort. This would require an abstraction layer on top of hulahop/pywebkitgtk that Browse could target. This would open the road for other engines as well (like chromium).
Thus, this project has two parts:
1) Design and implement a browser engine abstraction layer in Python with two backends: hulahop/xulrunner and pywebkitgtk/webkit.
2) Port Browse to this new abstraction layer, complete with [[Webified|SSB support]].
* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''
* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''