Community:SummerOfCode11:Brainstorming: Difference between revisions

no edit summary
No edit summary
Line 43: Line 43:
| <br>  
| <br>  
| <br>
| <br>
|-
| Port Mozilla C/C++ codebase to java
|
The aim of this project is to port parts of Firefox C/C++ codebase to java to create java version of Firefox eventually. Wrapping platform-specific code with Netscape Portable Runtime makes possible to use effective code translation.
Project will create iterative and incremental process. Every cycle starts with working version of java Firefox (splitted up into legacy and ported parts). Cycle consist of following development tasks:
1. Choosing legacy module/sources to port.
2. Running source translator on it.
3. Fixing (porting) broken code. Beside fixing runtime for translated code (special library to reduce and simplify code modifications of translated sources) is updating.
4. Analysis new porting patterns and cases for translation using new runtime features.
5. Modify translator according discovered patterns so it will produce more applicable code.
6. Recover two java Firefox parts integrity if any problems. Update build scripts.
More detailed information you can read [https://docs.google.com/document/pub?id=1R71HRpSyDTlXlaNm3WPURal0GIqq5-X6e5mpntVoP08 here].
'''Refs:'''
[1] http://simile.mit.edu/wiki/Java_Firefox_Extension
[2] https://developer.mozilla.org/en/java_in_firefox_extensions
[3] http://www.mozilla.org/rhino/
[4] http://java.net/projects/squawk/
[5] http://tech.novosoft-us.com/product_c2j.jsp
[6] http://www.tangiblesoftwaresolutions.com/Product_Details/CPlusPlus_to_Java_Converter_Details.html
| Makarov Dmitry  (student) <br/>  <br/> MENTOR WANTED!
|
|
|}
|}


Line 98: Line 136:
| <br>
| <br>
| <br>
| <br>
|-
| Resource tracker for extensions
|
Create CPU-time and memory resource tracker for add-ons. Result must be looking similar to Google Chrome Shift-Esc task manager. That is feature showing consumed resources per add-on. By contrast Chromium that use extension process separation and show process characteristics this project implementation will use js-profiling abilities of Firefox.
More detailed information you can read [https://docs.google.com/document/pub?id=18Lw7UtzZog9m1taCds5nlEFycNpkIgGA0AsbGMq45u8 here].
'''Refs:'''
[1] http://www.mozilla.org/projects/venkman/
[2] https://jetpack.mozillalabs.com/
[3] https://wiki.mozilla.org/Electrolysis
[4] https://addons.mozilla.org/en-US/firefox/addon/firebug/
[5] http://www.softwareishard.com/blog/firebug/tracing-console-for-firebug/
[6] https://addons.mozilla.org/en-US/firefox/addon/xul-profiler-by-yoono/
[7] https://addons.mozilla.org/en-US/firefox/addon/memory-profiler/
[8] https://addons.mozilla.org/en-US/firefox/addon/leak-monitor/
[9] https://engtech.wordpress.com/2007/11/13/howto-greasemonkey-profiler-firebug/
[10] http://seleniumhq.org/projects/ide/
[11] http://www.mozilla.org/performance/jsprofiler.html
| Makarov Dmitry  (student) <br/>  <br/> MENTOR WANTED!
|
|
|}
|}


2

edits