Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Community:SummerOfCode13: Difference between revisions
Correct individual URLs for felipe projects.
(Add links to Felipe's blog post) |
(Correct individual URLs for felipe projects.) |
||
| Line 35: | Line 35: | ||
tightly controlled, irreversible-without-password setting, but rather a feature that will make it harder to accidentally break or deteriorate the Firefox experience. | tightly controlled, irreversible-without-password setting, but rather a feature that will make it harder to accidentally break or deteriorate the Firefox experience. | ||
This project will be implemented using the Add-on SDK. [http://felipe.wordpress.com/2013/04/22/ | This project will be implemented using the Add-on SDK. [http://felipe.wordpress.com/2013/04/22/silverfox-gsoc/ More info about this project]. | ||
| Good JS skills and ability to work with large codebases. Previous add-on experience is a big plus. | | Good JS skills and ability to work with large codebases. Previous add-on experience is a big plus. | ||
| [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared] | | [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared] | ||
| Line 43: | Line 43: | ||
| about:memory has been a very useful tool for us developers to better understand memory consumption in Firefox and help diagnose and fix problems (See the [https://wiki.mozilla.org/Performance/MemShrink MemShrink project]). We would like to make about:memory also useful for web developers and users by providing better data visualization and analysis that will help them understand the footprint of their websites and improve accordingly. You should be able to come up with useful and creative ways to visualize that data and implement those visualization using JS. | | about:memory has been a very useful tool for us developers to better understand memory consumption in Firefox and help diagnose and fix problems (See the [https://wiki.mozilla.org/Performance/MemShrink MemShrink project]). We would like to make about:memory also useful for web developers and users by providing better data visualization and analysis that will help them understand the footprint of their websites and improve accordingly. You should be able to come up with useful and creative ways to visualize that data and implement those visualization using JS. | ||
We would still keep the original about:memory but relabel it as something like "Stats for nerds". It is important to keep the original/light-weight version since a visual-heavy implementation of about:memory will use non-trivial amounts of memory. [http://felipe.wordpress.com/2013/04/22/ | We would still keep the original about:memory but relabel it as something like "Stats for nerds". It is important to keep the original/light-weight version since a visual-heavy implementation of about:memory will use non-trivial amounts of memory. [http://felipe.wordpress.com/2013/04/22/aboutmemory-gsoc/ More info about this project]. | ||
| Good JS skills and knowledge/passion for data vizualization. Past work with data visualization is a big plus. | | Good JS skills and knowledge/passion for data vizualization. Past work with data visualization is a big plus. | ||
| [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared] | | [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared] | ||
| Line 50: | Line 50: | ||
| Fullscreen Mode | | Fullscreen Mode | ||
| One upcoming Firefox feature is a fullscreen mode that should provide an immersive experience. This mode will provide a streamlined interface as can be seen in this [http://people.mozilla.com/~shorlander/ux-presentation/01-Firefox-Australis-%28Windows%29-%28Fullscreen%29.jpg preliminary mockup]. Features such as a clock and other OS indicators (new APIs have been implemented for these from the WebAPI project) might also be part of the project. | | One upcoming Firefox feature is a fullscreen mode that should provide an immersive experience. This mode will provide a streamlined interface as can be seen in this [http://people.mozilla.com/~shorlander/ux-presentation/01-Firefox-Australis-%28Windows%29-%28Fullscreen%29.jpg preliminary mockup]. Features such as a clock and other OS indicators (new APIs have been implemented for these from the WebAPI project) might also be part of the project. | ||
The implementation of this feature will mostly involve three languages: XUL, CSS and JS. [http://felipe.wordpress.com/2013/04/22/ | The implementation of this feature will mostly involve three languages: XUL, CSS and JS. [http://felipe.wordpress.com/2013/04/22/fullscreen-gsoc/ More info about this project]. | ||
| Great CSS skills are important, and knowledge of XUL/flexbox is a plus. Good JS skills. Past theme development experience would be great. | | Great CSS skills are important, and knowledge of XUL/flexbox is a plus. Good JS skills. Past theme development experience would be great. | ||
| [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared] | | [mailto:gsoc@felipc.com Felipe], [mailto:jwein+gsoc@mozilla.com Jared] | ||
| Line 71: | Line 71: | ||
| Autosuggest Search Engines | | Autosuggest Search Engines | ||
| Many websites have search fields that are used many times over, but these websites do not present themselves as search-capable in order to offer itself to be added as a search engine in the browser. [https://bugzilla.mozilla.org/show_bug.cgi?id=335448 Firefox should detect repeated search field usage] and offer that as an option to the user. At a minimum, it should be able to detect it and add an entry with "Add [website]" in the searchbar dropdown (similar to how OpenSearch works). After the detection part is working well, a refined UX for the feature can be discussed and prototyped (but that shouldn't be the focus of the project). | | Many websites have search fields that are used many times over, but these websites do not present themselves as search-capable in order to offer itself to be added as a search engine in the browser. [https://bugzilla.mozilla.org/show_bug.cgi?id=335448 Firefox should detect repeated search field usage] and offer that as an option to the user. At a minimum, it should be able to detect it and add an entry with "Add [website]" in the searchbar dropdown (similar to how OpenSearch works). After the detection part is working well, a refined UX for the feature can be discussed and prototyped (but that shouldn't be the focus of the project). | ||
The student should be able to propose methods on how the detection algorithm should work and how to make improvements on it over the course of the project. [http://felipe.wordpress.com/2013/04/22/ | The student should be able to propose methods on how the detection algorithm should work and how to make improvements on it over the course of the project. [http://felipe.wordpress.com/2013/04/22/autosuggest-gsoc/ More info about this project]. | ||
| Great JS skills and understanding of DOM, HTML form fields, and algorithms (db and data structures that will be used to store and search the input field history to detect patterns of search usage) | | Great JS skills and understanding of DOM, HTML form fields, and algorithms (db and data structures that will be used to store and search the input field history to detect patterns of search usage) | ||
| [mailto:gsoc@felipc.com Felipe] | | [mailto:gsoc@felipc.com Felipe] | ||