diff options
Diffstat (limited to 'developers/gsoc/2008ideas.html')
| -rw-r--r-- | developers/gsoc/2008ideas.html | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/developers/gsoc/2008ideas.html b/developers/gsoc/2008ideas.html index c7c0a9a..d888bb6 100644 --- a/developers/gsoc/2008ideas.html +++ b/developers/gsoc/2008ideas.html @@ -37,8 +37,8 @@ <div class="navsection"> <ul class="sitelinks"> -<li><a href="http://wiki.netsurf-browser.org/">Development wiki</a></li> -<li><a href="http://source.netsurf-browser.org/">Git repository viewer</a></li> +<li><a href="//wiki.netsurf-browser.org/">Development wiki</a></li> +<li><a href="//source.netsurf-browser.org/">Git repository viewer</a></li> <li><a href="http://ci.netsurf-browser.org/">Continuous Integration</a></li> <li><a href="http://bugs.netsurf-browser.org/">Bug report system</a></li> <li><a href="http://ci.netsurf-browser.org/jenkins/view/Categorized/job/docs-netsurf/doxygen/">Code documentation</a></li> @@ -63,9 +63,9 @@ <ul> <li>Join our IRC channel <code>#netsurf</code> on <a href="http://freenode.net/">Freenode</a> and introduce yourself. Also, subscribe to the <a href="http://www.netsurf-browser.org/lists/netsurf-dev">developer mailing list</a>.</li> <li>Have access to a computer with supported OS (RISC OS, Linux, FreeBSD, etc) or an OS relevant for the project you want to apply for (Windows, Mac OS).</li> -<li>Get up to speed with <a href="http://wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>.</li> +<li>Get up to speed with <a href="//wiki.netsurf-browser.org/Documentation/GettingCoding">Git</a>, as we use this for source control, and get the NetSurf <a href="http://www.netsurf-browser.org/documentation/develop#SourceControl">source code</a>.</li> <li><a href="http://www.netsurf-browser.org/documentation/develop#Compiling">Build NetSurf</a> and enjoy using it. (Ask if you need help.)</li> -<li>Get familiarised with the source code – read the <a href="http://git.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li> +<li>Get familiarised with the source code – read the <a href="//git.netsurf-browser.org/netsurf.git/tree/docs">code documentation</a>.</li> </ul> <dd> <dt>When applying for a project<dt> @@ -79,7 +79,7 @@ <dd> <ul> <li>Most of NetSurf team communication happens via #netsurf IRC during evenings and nights (<a href="http://en.wikipedia.org/wiki/Central_European_Time">CET</a>). We expect you to join in on a regular basis for help, discussions and project updates. Note that you're not restricted to speaking to your assigned mentor; the whole development team are willing to help wherever they can.</li> -<li>When improving NetSurf's layout engine, be able to create <a href="http://source.netsurf-browser.org/trunk/netsurftest/">test cases</a> and verify that existing test cases don't get broken.</li> +<li>When improving NetSurf's layout engine, be able to create <a href="//source.netsurf-browser.org/trunk/netsurftest/">test cases</a> and verify that existing test cases don't get broken.</li> <li>Keep NetSurf's <a href="http://www.netsurf-browser.org/about/#ProjectGoals">project goals</a> in mind, especially the first point.</li> </ul> </dd> @@ -105,33 +105,33 @@ <li>Focus upon and fix the limitations in the current CSS engine</li> <li>Develop an entirely new CSS engine to replace the existing one</li> </ul> -<p>There is an outline description of a <a href="http://git.netsurf-browser.org/netsurf.git/tree/docs/ideas/css-engine.txt">new CSS engine</a>, which may be of interest to those who want to take the second approach to this project. This description is fairly complete from an external API perspective. The implementation details of a new engine are completely negotiable – we have some idea of what's needed, but the student's input will be highly valued.</p> +<p>There is an outline description of a <a href="//git.netsurf-browser.org/netsurf.git/tree/docs/ideas/css-engine.txt">new CSS engine</a>, which may be of interest to those who want to take the second approach to this project. This description is fairly complete from an external API perspective. The implementation details of a new engine are completely negotiable – we have some idea of what's needed, but the student's input will be highly valued.</p> <p>Regardless of which approach is taken, we would expect that testing of the code is performed on a regular basis to ensure that things are still working as expected. New testcases should be written to exercise existing bugs and test out new functionality.</p> </div> <p><strong>Skills required:</strong> C, CSS, parsing</p> <p><strong>Difficulty:</strong> Medium</p> -<p><strong>Existing code:</strong> <a href="http://git.netsurf-browser.org/netsurf.git/tree/content/handlers/css">CSS parser and modules</a></p> +<p><strong>Existing code:</strong> <a href="//git.netsurf-browser.org/netsurf.git/tree/content/handlers/css">CSS parser and modules</a></p> <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21/">CSS 2.1 specification</a> <a href="http://www.w3.org/TR/DOM-Level-2-Style/">DOM Level 2 Style specification</a></p> <h2>Native Windows or Mac OS X ports</h2> <p>NetSurf currently has user-interface layers for the RISC OS Window Manager and for GTK (on Linux, FreeBSD, etc.). The GTK interface works on Windows or Mac OS X, but a native interface for these systems would give a better experience.</p> <p><strong>Skills required:</strong> C, Windows UI development or Mac OS X UI development</p> <p><strong>Difficulty:</strong> Medium</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/gui.h?view=markup">Declarations of functions that each interface must implement</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/gui.h?view=markup">Declarations of functions that each interface must implement</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a></p> <p><strong>References:</strong></p> <h2>Keyboard navigation</h2> <p>The browser currently requires a mouse to use. Keyboard shortcuts would move between and activate links, inputs, etc. The document structure is stored in a tree, and algorithms for walking through the tree to find the next link or input would need to be developed. A further improvement would be to take layout position into account and implement moving in 2D.</p> <p><strong>Skills required:</strong> C, HTML, CSS, usability</p> <p><strong>Difficulty:</strong> Easy</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/textinput.c?view=markup">Key press handling</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.h?view=markup">Box tree structures</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/textinput.c?view=markup">Key press handling</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render/box.h?view=markup">Box tree structures</a></p> <p><strong>References:</strong></p> <h2>Printing improvements</h2> <p>Printing is currently only available on RISC OS, and the output is difficult for the user to predict. Work could include implementing printing for GTK, print preview, intelligent paging or reformatting, support for print stylesheets, and user control over what parts of the page are printed. This might include writing a portable base and platform-specific layer.</p> <p><strong>Skills required:</strong> C, CSS, GTK, possibly Cairo, possibly Postscript</p> <p><strong>Difficulty:</strong> Hard</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/print.c?view=markup">RISC OS printing implementation</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/riscos/print.c?view=markup">RISC OS printing implementation</a></p> <p><strong>References:</strong></p> <h2>PDF plotter</h2> @@ -146,7 +146,7 @@ </div> <p><strong>Skills required:</strong> C, graphics, PDF</p> <p><strong>Difficulty:</strong> Medium</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">Plotter interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/plotters.c?view=markup">RISC OS plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/gtk_plotters.c?view=markup">GTK plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/save_draw.c?view=markup">DrawFile plotter</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/plotters.h?view=markup">Plotter interface</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/plotters.c?view=markup">RISC OS plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/gtk_plotters.c?view=markup">GTK plotter</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/save_draw.c?view=markup">DrawFile plotter</a></p> <p><strong>References:</strong></p> <p><strong>Mentor:</strong> John Tytgat</p> @@ -169,7 +169,7 @@ <p>NetSurf currently has no support for CSS dynamic pseudo classes (e.g. :hover). The work would involve adding support for these classes to the CSS parser and selection engine and modifying the layout engine to handle dynamic style changes.</p> <p><strong>Skills required:</strong> C, HTML, CSS</p> <p><strong>Difficulty:</strong> Hard</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/css">CSS parser</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render">HTML handler and layout engine</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/css">CSS parser</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/render">HTML handler and layout engine</a></p> <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21">CSS 2.1 specification</a></p> @@ -177,7 +177,7 @@ <p>NetSurf's RISC OS user interface is rich and powerful. It supports many features such as editable toolbars, dialogue box handling and menu generation. If the interface code was abstracted into a separate library, other RISC OS applications could benefit from the availability of a sophisticated, tried and tested and style guide compliant GUI toolkit.</p> <p><strong>Skills required:</strong> C, RISC OS WIMP, OSLib</p> <p><strong>Difficulty:</strong> Medium – Hard</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/riscos/">RISC OS specific code</a></p> <p><strong>References:</strong> <a href="http://ro-oslib.sourceforge.net/">OSLib</a></p> <h2>Extracting the core into a library</h2> @@ -190,7 +190,7 @@ <p>Ideally, the back-end part of the browser would be abstracted to a stand-alone library, which a front-end could provide a table of entry points to. This allows for more than one program to use NetSurf's abilities efficiently, as well as giving us a chance to rationalise and tidy up the current rather ad-hoc API.</p> <p><strong>Skills required:</strong> C</p> <p><strong>Difficulty:</strong> Medium – Hard</p> -<p><strong>Existing code:</strong> See "Native Windows or Mac OS X ports" and "PDF plotter". <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/options.c?view=markup">Options code in back-end</a></p> +<p><strong>Existing code:</strong> See "Native Windows or Mac OS X ports" and "PDF plotter". <a href="//source.netsurf-browser.org/trunk/netsurf/desktop/options.c?view=markup">Options code in back-end</a></p> <p><strong>References:</strong></p> <h2>Improved inline element handling</h2> @@ -203,7 +203,7 @@ </ul> <p><strong>Skills required:</strong> C, HTML, CSS</p> <p><strong>Difficulty:</strong> Hard</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/render/layout.c?view=markup">Layout code</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/render/layout.c?view=markup">Layout code</a></p> <p><strong>References:</strong> <a href="http://www.w3.org/TR/CSS21/">CSS 2.1 specification</a></p> <h2>Improved GTK front end; tabs, downloads, etc</h2> @@ -216,7 +216,7 @@ </ul> <p><strong>Skills required:</strong> C, GTK</p> <p><strong>Difficulty:</strong> Medium</p> -<p><strong>Existing code:</strong> <a href="http://source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/">Core code for text selection, export, etc</a></p> +<p><strong>Existing code:</strong> <a href="//source.netsurf-browser.org/trunk/netsurf/gtk/">GTK specific code</a>, <a href="http://source.netsurf-browser.org/trunk/netsurf/desktop/">Core code for text selection, export, etc</a></p> <p><strong>References:</strong></p> <div class="footer"> |