18 resultados para Patrick Chamoiseau
em University of Southampton, United Kingdom
Resumo:
This is one of a series of short case studies describing how academic tutors at the University of Southampton have made use of learning technologies to support their students.
Resumo:
This is one of a series of short case studies describing how academic tutors at the University of Southampton have made use of learning technologies to support their students.
Resumo:
This is a presentation I put together to get students thinking about their digital university experience. The resulting discussions will be used to inform a survey sent out to all students to find out what parts of the digital university experience are important to them.
Resumo:
A Seminar about the advantages of using open source licenses as a complimentary strategy to the academic publish process.
Resumo:
In the example code you can see that when the remove(Object o) method is called the Integer is not cast to an int and the matching is done using the object's .equals() method rather than using ==
Resumo:
Edshare for INFO2009 coursework 2 - Team 'DROP TABLE groups;
Resumo:
Our website is a resource that describes equality and shows examples of bad Web accessibility. The website is hosted at: http://users.ecs.soton.ac.uk/wjvh1g10/index.html
Resumo:
An introduction to Vim and why I use it. This resource is the precursor to a technical walk through and code along using vim. During the talk I handed round a cheat sheet for vim which can be found at http://www.tuxfiles.org/linuxhelp/vimcheat.html You can find full documentation and a lot more indepth examples in the vim documentation: http://vimdoc.sourceforge.net/htmldoc/help.html
Resumo:
This is a sample visualization of contributions to eprints.soton.ac.uk. The visualization was created from data from the OAI endpoint using gource. The data is divided by dc:subject classification. The idea was taken from Martin Hawksey's blog post http://mashe.hawksey.info/2011/12/google-refining-jorum-ukoer/
Resumo:
I delivered this presentation at the CITE seminar on 5th of February 2013
Resumo:
This is a selection of University of Southampton Logos in both vector (svg) and raster (png) formats. These are suitable for use on the web or in small documents and posters. You can open the SVG files using inkscape (http://inkscape.org/download/?lang=en) and edit them directly. The University logo should not be modified and attention should be paid to the branding guidelines found here: http://www.edshare.soton.ac.uk/10481 You must always leave a space the width of an capital O in Southampton on all 4 edges of the logo. The negative space makes it appear more prominently on the page.
Resumo:
This is a set of slides and a tutorial exercise which we used to teach people the basics of RDF and how they can manipulate data in this format to make quite powerful web pages very simply. It is not intended as full introduction to RDF and it's subtleties the aim is to teach the very bare minimum to be able to do something quickly. It empowers programmers to go away and play with linked data.
Resumo:
These are a range of logos created in the same way as Mr Patrick McSweeny http://www.edshare.soton.ac.uk/11157. The logo has been extracted from PDF documents and is smoother and accurate to the original logo design. Many thanks to to McSweeny for publishing the logo, in SVG originally, I struggled to find it anywhere else. Files are in Inkscape SVG, PDF and PNG. From Mr Patrick McSweeney: This is a selection of University of Southampton Logos in both vector (svg) and raster (png) formats. These are suitable for use on the web or in small documents and posters. You can open the SVG files using inkscape (http://inkscape.org/download/?lang=en) and edit them directly. The University logo should not be modified and attention should be paid to the branding guidelines found here: http://www.edshare.soton.ac.uk/10481 You must always leave a space the width of an capital O in Southampton on all 4 edges of the logo. The negative space makes it appear more prominently on the page.