CSCWiki - User contributions [en]

Library Project

2013-10-22T21:55:13Z

Jladan: /* Guidelines for Library Funding */

== Existing Solution ==
There is a menu entry in [[ceo]] for the library. Do not use this for library stuff.

In Fall 2013, a new database and library interface is being implemented to make it easier to maintain the library and check out books. The book checkout system will likely be added to [[ceo]]

== Objectives ==
Our club library is pretty impressive, for 1980. We should seriously consider changing this to the present. Content decisions seem to generally be made by strongly opinionated individuals whereas we should be focused on providing resources for anyone on campus who is interested in computer science.
* Bring in a proper library management system.
** This is being written. If interested in contributing, contact jladan.
* Update and improve library content.
* Set up some method of keeping the library current in the future.
* Re-evaluate the purpose of our library.

== Books Wishlist ==
Split to [[Books Wishlist]]

== Guidelines for Library Funding ==
In the past, our budgets have failed to focus much attention to the library,
even though our textbooks keeping getting older and less relevant, and courses
and frontiers in Computer Science evolve. It is a shame that we don't have a book
on multi-core programming, or artificial intelligence! The following guideline
provides a detailed strategy for budgeting for books in the future :

'''This guideline is likely high, because most undergrad courses are moving towards printed course notes rather than textbooks.'''

*Did you know that every year approximately 20% of the courses in [http://www.cs.uwaterloo.ca/ SCS] change their books & edition?
This equates to something like $1000 of new material per year. As a result :
**We need to raise at least $1,000 annually to keep up with the material used to cover courses in SCS
**We will need to raise most of it during the Fall & Winter terms since :
***First offerings of courses occur in the Fall/Winter term each year and that is when the new textbooks arrive
***Historically we get higher memberships and people on campus so more funding
*Did you know that CS is a constantly changing field?
**New fields within CS are discovered every year
**New technologies and paradigms (e.g. multi-core programming) occur every 5 to 10 years?
**New knowledge is discovered in the field that replaces our older (less accurate) knowledge?
We therefore need to allocate roughly $1,500 per year to have a library that accurately reflects the current
and state of the art of computer science. To say that our library is not state of the art in CS is an extreme
under-statement. This funding could be equally spread out to $500 per term from mathsoc.

Currently our library is very much outdated and does not have textbooks that reflect the courses that CS students are
currently taking. From my estimate we need approximately $5,000 to have an up to date CS library. Therefore for the immediate strategy we need to get at least $1,500 per term from Mathsoc/MEF to allow our library a chance at staying current with the department's offerings. Therefore we should try to budget in $2,000 for Fall,Winter and Spring to get our library updated to the CS courses as well as to cover some of the frontiers and state of the art in computing that will serve our library into the future.

A great deal of discussion has been spent talking about our library equipment and possible hardware (barcode upgrades for instance). However I don't think it would be responsible for us to look at these areas and especially to budget these improvements in if we don't have a vastly updated library.

== Fixing the Library ==
A statement :
The only way to get the library fixed is through terms of growing and pruning.
As mentioned above, we need to grow our library to reflect the courses offered in SCS,
as well as to cover the current and state of the art in CS.

At the same time it is important that we prune down our library to contain relevant and
updated material. There is no point in having a cluttered library that makes it hard to
find reference material because we must hold on to books that are 20/30+ years old. We
don't need to have books on APL/360 programming, and having these old unnecessarry books
will pollute our library with irrelevance and outdatedness.

The only way the library can be fixed is to find the solutions to the direct problems in our
library. That is rather than worrying about the irrelevant technical details of the library system,
we need to take a look at our inventory (that is our books) and see what needs growing and pruning.
We can build the technical layers once we have built the paper layers (that is the physical books have
been purchased or have been planned to be purchased). It will take courage and will to follow
this procedure since we will have to let go of things that need letting go.
== Proposed Library Update Plan ==
One of the problems in keeping any library relevant is to ensure that reference material
is up to date and current with the area of study in question. This is especially true in
the area of computer science and technology where ideas change fast. The following are some
suggested considerations which could aid in keeping our library up to date now and into the
future.
* Safari Bookshelf Subscription
Safari Bookshelf is a online web service that allows you to read any O'Reilly book for a
subscription fee (usually around $40/month). This service will give the CSC an excellent
online library resource, where members can login and view all of the latest O'Reilly books
including those yet to be published. Access control would be a concern which would need
to be addressed in using such a system, however the concept of having an electronic resource
of continually up to date reference material is tempting.
* What are the new technologies and ideas in computer science?
This is the question that we should be asking ourselves at least at the beginning of the term
to determine what new books need to be purchased to fill the reference gap that builds going from
term to term. We should have a firm commitment of purchasing at least 10 reference books per term
to ensure that we are getting the breadth and depth requirements of having a successful CS library,
especially when it is common for dozens of new CS books to be released every term.
* What are the official CS course textbooks?
The CSC should have an up to date library of all of the required textbooks for all of the CS courses
offered at the University. This will allow our members to quickly access their course reference materials
should they ever leave their books at home, or need to look at the book desperately for an assignment that
is coming due soon. The CSC be a source of reference for CS students who need the references that drive
many of their CS courses.
* What books are getting old?
** How relevant is the book's content today?
** Has the book gone to a new edition?
** Have their been fundamental changes in the topic which are not reflected in the current book?
** How popular is the book? (This can be determined by how many times it has been checked out from the library system)
** Does the material fill a large gap in our reference material?
== Library Accessories ==
There has also been some talk for suggested accessories or tools for our library system. The
following is the current list of such accessories and reasons behind getting such accessories.
* Magstripe Member Cards
Each CSC member could have a magstripe member card which would allow them to check-in and checkout
books by swiping their card at a swiper and then scanning the book in question. This could speed
up the check-in/check-out times since they do not need to enter information into the system, but
rather scan their cards. The magstripe cards could later be extended with CEO to allow term renewal
via card swipe, as well as other value added features.
* Wireless barcode scanner.
The wireless barcode scanner will allow us to go up to the books and scan them in, rather than
having to move the books over to the barcode scanner to have them scanned. This will allow for
a degree of more freedom when scanning in books (especially when we receive the stack of new
books)
* RFID tags
When we receive new books, RFID tags encoded with book information is attached to each book.
Whenever, someone checks-in/checks out books, all you need to do is wave the book in front of a scanner
without having to locate the barcode, which could speed up the process of checking in and out books

[[Category:Library]]
[[Category:Projects]]

Library Project

2013-10-22T21:46:52Z

Jladan: /* Objectives */

== Existing Solution ==
There is a menu entry in [[ceo]] for the library. Do not use this for library stuff.

In Fall 2013, a new database and library interface is being implemented to make it easier to maintain the library and check out books. The book checkout system will likely be added to [[ceo]]

== Objectives ==
Our club library is pretty impressive, for 1980. We should seriously consider changing this to the present. Content decisions seem to generally be made by strongly opinionated individuals whereas we should be focused on providing resources for anyone on campus who is interested in computer science.
* Bring in a proper library management system.
** This is being written. If interested in contributing, contact jladan.
* Update and improve library content.
* Set up some method of keeping the library current in the future.
* Re-evaluate the purpose of our library.

== Books Wishlist ==
Split to [[Books Wishlist]]

== Guidelines for Library Funding ==
In the past, our budgets have failed to focus much attention to the library,
even though our textbooks keeping getting older and less relevant, and courses
and frontiers in Computer Science evolve. It is a shame that we don't have a book
on multi-core programming, or artificial intelligence! The following guideline
provides a detailed strategy for budgeting for books in the future :

*Did you know that every year approximately 20% of the courses in [http://www.cs.uwaterloo.ca/ SCS] change their books & edition?
This equates to something like $1000 of new material per year. As a result :
**We need to raise at least $1,000 annually to keep up with the material used to cover courses in SCS
**We will need to raise most of it during the Fall & Winter terms since :
***First offerings of courses occur in the Fall/Winter term each year and that is when the new textbooks arrive
***Historically we get higher memberships and people on campus so more funding
*Did you know that CS is a constantly changing field?
**New fields within CS are discovered every year
**New technologies and paradigms (e.g. multi-core programming) occur every 5 to 10 years?
**New knowledge is discovered in the field that replaces our older (less accurate) knowledge?
We therefore need to allocate roughly $1,500 per year to have a library that accurately reflects the current
and state of the art of computer science. To say that our library is not state of the art in CS is an extreme
under-statement. This funding could be equally spread out to $500 per term from mathsoc.

Currently our library is very much outdated and does not have textbooks that reflect the courses that CS students are
currently taking. From my estimate we need approximately $5,000 to have an up to date CS library. Therefore for the immediate strategy we need to get at least $1,500 per term from Mathsoc/MEF to allow our library a chance at staying current with the department's offerings. Therefore we should try to budget in $2,000 for Fall,Winter and Spring to get our library updated to the CS courses as well as to cover some of the frontiers and state of the art in computing that will serve our library into the future.

A great deal of discussion has been spent talking about our library equipment and possible hardware (barcode upgrades for instance). However I don't think it would be irresponsible for us to look at these areas and especially to budget these improvements in if we don't have a vastly updated library.
== Fixing the Library ==
A statement :
The only way to get the library fixed is through terms of growing and pruning.
As mentioned above, we need to grow our library to reflect the courses offered in SCS,
as well as to cover the current and state of the art in CS.

At the same time it is important that we prune down our library to contain relevant and
updated material. There is no point in having a cluttered library that makes it hard to
find reference material because we must hold on to books that are 20/30+ years old. We
don't need to have books on APL/360 programming, and having these old unnecessarry books
will pollute our library with irrelevance and outdatedness.

The only way the library can be fixed is to find the solutions to the direct problems in our
library. That is rather than worrying about the irrelevant technical details of the library system,
we need to take a look at our inventory (that is our books) and see what needs growing and pruning.
We can build the technical layers once we have built the paper layers (that is the physical books have
been purchased or have been planned to be purchased). It will take courage and will to follow
this procedure since we will have to let go of things that need letting go.
== Proposed Library Update Plan ==
One of the problems in keeping any library relevant is to ensure that reference material
is up to date and current with the area of study in question. This is especially true in
the area of computer science and technology where ideas change fast. The following are some
suggested considerations which could aid in keeping our library up to date now and into the
future.
* Safari Bookshelf Subscription
Safari Bookshelf is a online web service that allows you to read any O'Reilly book for a
subscription fee (usually around $40/month). This service will give the CSC an excellent
online library resource, where members can login and view all of the latest O'Reilly books
including those yet to be published. Access control would be a concern which would need
to be addressed in using such a system, however the concept of having an electronic resource
of continually up to date reference material is tempting.
* What are the new technologies and ideas in computer science?
This is the question that we should be asking ourselves at least at the beginning of the term
to determine what new books need to be purchased to fill the reference gap that builds going from
term to term. We should have a firm commitment of purchasing at least 10 reference books per term
to ensure that we are getting the breadth and depth requirements of having a successful CS library,
especially when it is common for dozens of new CS books to be released every term.
* What are the official CS course textbooks?
The CSC should have an up to date library of all of the required textbooks for all of the CS courses
offered at the University. This will allow our members to quickly access their course reference materials
should they ever leave their books at home, or need to look at the book desperately for an assignment that
is coming due soon. The CSC be a source of reference for CS students who need the references that drive
many of their CS courses.
* What books are getting old?
** How relevant is the book's content today?
** Has the book gone to a new edition?
** Have their been fundamental changes in the topic which are not reflected in the current book?
** How popular is the book? (This can be determined by how many times it has been checked out from the library system)
** Does the material fill a large gap in our reference material?
== Library Accessories ==
There has also been some talk for suggested accessories or tools for our library system. The
following is the current list of such accessories and reasons behind getting such accessories.
* Magstripe Member Cards
Each CSC member could have a magstripe member card which would allow them to check-in and checkout
books by swiping their card at a swiper and then scanning the book in question. This could speed
up the check-in/check-out times since they do not need to enter information into the system, but
rather scan their cards. The magstripe cards could later be extended with CEO to allow term renewal
via card swipe, as well as other value added features.
* Wireless barcode scanner.
The wireless barcode scanner will allow us to go up to the books and scan them in, rather than
having to move the books over to the barcode scanner to have them scanned. This will allow for
a degree of more freedom when scanning in books (especially when we receive the stack of new
books)
* RFID tags
When we receive new books, RFID tags encoded with book information is attached to each book.
Whenever, someone checks-in/checks out books, all you need to do is wave the book in front of a scanner
without having to locate the barcode, which could speed up the process of checking in and out books

[[Category:Library]]
[[Category:Projects]]

Library Project

2013-10-22T21:44:07Z

Jladan: /* Existing Solution */

== Existing Solution ==
There is a menu entry in [[ceo]] for the library. Do not use this for library stuff.

In Fall 2013, a new database and library interface is being implemented to make it easier to maintain the library and check out books. The book checkout system will likely be added to [[ceo]]

== Objectives ==
Our club library is pretty impressive, for 1980. We should seriously consider changing this to 2007. Content decisions seem to generally be made by strongly opinionated individuals whereas we should be focused on providing resources for anyone on campus who is interested in computer science.
* Update and improve library content.
* Bring in a proper library management system.
** This may want to be written. If interested in contributing, contact the Systems Committee or Club Executive.
* Set up some method of keeping the library current in the future.
* Re-evaluate the purpose of our library.

== Books Wishlist ==
Split to [[Books Wishlist]]

== Guidelines for Library Funding ==
In the past, our budgets have failed to focus much attention to the library,
even though our textbooks keeping getting older and less relevant, and courses
and frontiers in Computer Science evolve. It is a shame that we don't have a book
on multi-core programming, or artificial intelligence! The following guideline
provides a detailed strategy for budgeting for books in the future :

*Did you know that every year approximately 20% of the courses in [http://www.cs.uwaterloo.ca/ SCS] change their books & edition?
This equates to something like $1000 of new material per year. As a result :
**We need to raise at least $1,000 annually to keep up with the material used to cover courses in SCS
**We will need to raise most of it during the Fall & Winter terms since :
***First offerings of courses occur in the Fall/Winter term each year and that is when the new textbooks arrive
***Historically we get higher memberships and people on campus so more funding
*Did you know that CS is a constantly changing field?
**New fields within CS are discovered every year
**New technologies and paradigms (e.g. multi-core programming) occur every 5 to 10 years?
**New knowledge is discovered in the field that replaces our older (less accurate) knowledge?
We therefore need to allocate roughly $1,500 per year to have a library that accurately reflects the current
and state of the art of computer science. To say that our library is not state of the art in CS is an extreme
under-statement. This funding could be equally spread out to $500 per term from mathsoc.

Currently our library is very much outdated and does not have textbooks that reflect the courses that CS students are
currently taking. From my estimate we need approximately $5,000 to have an up to date CS library. Therefore for the immediate strategy we need to get at least $1,500 per term from Mathsoc/MEF to allow our library a chance at staying current with the department's offerings. Therefore we should try to budget in $2,000 for Fall,Winter and Spring to get our library updated to the CS courses as well as to cover some of the frontiers and state of the art in computing that will serve our library into the future.

A great deal of discussion has been spent talking about our library equipment and possible hardware (barcode upgrades for instance). However I don't think it would be irresponsible for us to look at these areas and especially to budget these improvements in if we don't have a vastly updated library.
== Fixing the Library ==
A statement :
The only way to get the library fixed is through terms of growing and pruning.
As mentioned above, we need to grow our library to reflect the courses offered in SCS,
as well as to cover the current and state of the art in CS.

At the same time it is important that we prune down our library to contain relevant and
updated material. There is no point in having a cluttered library that makes it hard to
find reference material because we must hold on to books that are 20/30+ years old. We
don't need to have books on APL/360 programming, and having these old unnecessarry books
will pollute our library with irrelevance and outdatedness.

The only way the library can be fixed is to find the solutions to the direct problems in our
library. That is rather than worrying about the irrelevant technical details of the library system,
we need to take a look at our inventory (that is our books) and see what needs growing and pruning.
We can build the technical layers once we have built the paper layers (that is the physical books have
been purchased or have been planned to be purchased). It will take courage and will to follow
this procedure since we will have to let go of things that need letting go.
== Proposed Library Update Plan ==
One of the problems in keeping any library relevant is to ensure that reference material
is up to date and current with the area of study in question. This is especially true in
the area of computer science and technology where ideas change fast. The following are some
suggested considerations which could aid in keeping our library up to date now and into the
future.
* Safari Bookshelf Subscription
Safari Bookshelf is a online web service that allows you to read any O'Reilly book for a
subscription fee (usually around $40/month). This service will give the CSC an excellent
online library resource, where members can login and view all of the latest O'Reilly books
including those yet to be published. Access control would be a concern which would need
to be addressed in using such a system, however the concept of having an electronic resource
of continually up to date reference material is tempting.
* What are the new technologies and ideas in computer science?
This is the question that we should be asking ourselves at least at the beginning of the term
to determine what new books need to be purchased to fill the reference gap that builds going from
term to term. We should have a firm commitment of purchasing at least 10 reference books per term
to ensure that we are getting the breadth and depth requirements of having a successful CS library,
especially when it is common for dozens of new CS books to be released every term.
* What are the official CS course textbooks?
The CSC should have an up to date library of all of the required textbooks for all of the CS courses
offered at the University. This will allow our members to quickly access their course reference materials
should they ever leave their books at home, or need to look at the book desperately for an assignment that
is coming due soon. The CSC be a source of reference for CS students who need the references that drive
many of their CS courses.
* What books are getting old?
** How relevant is the book's content today?
** Has the book gone to a new edition?
** Have their been fundamental changes in the topic which are not reflected in the current book?
** How popular is the book? (This can be determined by how many times it has been checked out from the library system)
** Does the material fill a large gap in our reference material?
== Library Accessories ==
There has also been some talk for suggested accessories or tools for our library system. The
following is the current list of such accessories and reasons behind getting such accessories.
* Magstripe Member Cards
Each CSC member could have a magstripe member card which would allow them to check-in and checkout
books by swiping their card at a swiper and then scanning the book in question. This could speed
up the check-in/check-out times since they do not need to enter information into the system, but
rather scan their cards. The magstripe cards could later be extended with CEO to allow term renewal
via card swipe, as well as other value added features.
* Wireless barcode scanner.
The wireless barcode scanner will allow us to go up to the books and scan them in, rather than
having to move the books over to the barcode scanner to have them scanned. This will allow for
a degree of more freedom when scanning in books (especially when we receive the stack of new
books)
* RFID tags
When we receive new books, RFID tags encoded with book information is attached to each book.
Whenever, someone checks-in/checks out books, all you need to do is wave the book in front of a scanner
without having to locate the barcode, which could speed up the process of checking in and out books

[[Category:Library]]
[[Category:Projects]]

Books Wishlist

2013-10-22T21:38:11Z

Jladan: /* Foundations/Field Surveys */

This page consists of books we'd like to get to stock the [[library]]. It is divided into 3 sections. The first is books going on this term's MEF proposal, this should be done by whoever is writing the proposal. The second is a list of actual books with ISBN. The third is vague ideas of what kind of books we need. The goal is for this page to be emptied by way of moving things from section three up to section one and then off.

A bunch of these were bought. That needs to be updated.

Programming Windows by Charles Petzold used to be the definitive guide to Win32
http://www.amazon.ca/Programming-Windows%C2%AE-Charles-Petzold/dp/157231995X/ref=sr_1_1?ie=UTF8&s=books&qid=1269631483&sr=8-1

TCP/IP illustrated (All three volumes $180)
http://www.amazon.com/TCP-IP-Illustrated-Vol-Protocols/dp/0201633469
= MEF Proposal =
MEF Proposal books should include a quote and a sentence or two of justification.

= Actual Books =
Actual books should have a precise title and ISBN for edition desired.

*Coders at work
*Thinking as Computation
** http://mitpress.mit.edu/books/thinking-computation

== j2simpso's suggestions should be sorted ==
*Dreaming in Code
** ISBN 978-1400082469
*Founter's at Work: Stories of Startup's early Days
** ISBN 978-1590597149
*Metaprogramminging GPUs with SH
** ISBN 978-1568812298
*High Performance Computing
** ISBN 978-1566923126
*Critical Testing Processes: Plan, Prepare, Perform, Perfect
** ISBN 978-0201748680
* GREP pocket reference
** ISBN 978-0596153601
* Programming Embedded Systems
** ISBN 978-0596009830
* High Availability and Disaster REcovery
** ISBN 978-3540244608
* An Introduction to Mathematical Cryptography
** ISBN 978-0387779930
* Real Time Systems Design and Analysis
** ISBN 978-0471228554
* The Black Swan: The Impact of the Highly Improbable
** ISBN 978-1400063512

== Non-technical ==
* Mythical Man Month (20th Anniversary ed)
** ISBN 0-201-83595-9
* Natural Harvest - A Collection of Semen-Based Recipes
** ISBN 1-4743-1461-5
* Logicomix: An Epic Search for Truth
** ISBN 978-0747597209

== UI & HCI ==
*Sketching User Experiences
** ISBN 978-0-12-374037-3
*The Design of Everyday Things
** ISBN 978-0465067107
*The Laws of Simplicty
** ISBN 978-0262134729

== Course Textbooks ==
* CSfoo: '''rebind''' CLRS
* CS116: Downey, Python for Software Design: How to Think Like a Computer Scientist
** ISBN 978-0521725965
* CS136: King, C programming
** ISBN 978-0393979503
* CS240: GOODRICH & TAMASSIA:ALGORITHM DESIGN
** ISBN 978-0471383659
* CS246: SAVITCH:ABSOLUTE C++ 4TH ED
** ISBN 978-0136083818
* CS246: MEYERS:EFFECTIVE C++
** ISBN 978-0321334879
* CS365: Sipser, ''Introduction to the Theory of Computation'' SECOND EDITION
** ISBN 0-534-95097-3
* CS462 SHALLIT:SECOND COURSE IN FORMAL LANGUAGES & AUTOMATA THEOR
** ISBN 9780521865722

== Foundations/Field Surveys ==
* Knuth, The Art of Computer Programming (Copies that aren't signed)
** Volume 1, Fascicle 1: MMIX -- A RISC Computer for the New Millennium
*** ISBN 978-0201853926
** Volume 4, Fascicle 0: Introduction to Combinatorial Algorithms and Boolean Functions
*** ISBN 978-0321534965
** Volume 4, Fascicle 1: Bitwise Tricks & Techniques; Binary Decision Diagrams
*** ISBN 978-0321580504
** Volume 4, Fascicle 2: Generating All Tuples and Permutations
*** ISBN 978-0201853933
** Volume 4, Fascicle 3: Generating All Combinations and Partitions
*** ISBN 978-0201853940
** Volume 4, Fascicle 4: Generating All Trees--History of Combinatorial Generation
*** ISBN 978-0321335708
* Wirth, Algorithms + Data Structures = Programs
** ISBN 978-0130224187
* Dijkstra, A Discipline of Programming
** ISBN 978-0132158718
* Abelson, Structure and Interpretation of Computer Programs
** ISBN 978-0070004849
* Basic Category Theory for Computer Scientists
** ISBN 978-0262660716

== Strict Theory ==
* Recommended by John Watrous: http://www.amazon.com/Computational-Complexity-Approach-Sanjeev-Arora/dp/0521424267/ref=sr_1_1?ie=UTF8&s=books&qid=1276314046&sr=1-1
* [http://www.amazon.com/Computational-Complexity-Christos-H-Papadimitriou/dp/0201530821/ Papadimitriou, ''Computational Complexity''] or newer equivalent
** ISBN 0201530821
* [http://www.amazon.com/Computability-Theory-Chapman-Hall-Mathematics/dp/1584882379 Cooper, ''Computability Theory''] or similar (Cooper is buggy)
** ISBN 1-58-488237-9
* [http://www.amazon.com/Introduction-Kolmogorov-Complexity-Applications-Computer/dp/0387339981/ Li and Vitanyi ''Kolmogorov Complexity and its Applications]
** ISBN 978-0387339986
* [http://www.amazon.com/Cambridge-Tracts-Theoretical-Computer-Science/dp/0521802008 Blackburn, de Rijke, Venema, ''Modal Logic'']
** ISBN 978-0521802000
* Kozen, ''Theory of Computation''
** ISBN 978-1846282973

== Programming Languages ==

* Theory of
** Friedman & Wand, Essentials of Programming Languages, 3rd Edition
*** ISBN 978-0262062794
** Pierce, Types and Programming Languages
*** ISBN 978-0262162098
* C++
** Bjarne Stroustrup, A Tour of C++
*** ISBN 978-0321958310
** Andrei Alexandrescu, Modern C++ Design: Generic Programming and Design Patterns Applied
*** ISBN 978-0201704310
* Scheme
** Friedman, The Little Schemer - 4th Edition
*** ISBN 978-0262560993
** Friedman, The Seasoned Schemer
*** ISBN 978-0262561006
** Friedman, The Reasoned Schemer
*** ISBN 978-0262562140
** Dybvig, The Scheme Programming Language, 3rd Edition
*** ISBN 978-0262541480
* ML
** Reppy, Concurrent Programming in ML
*** ISBN 978-0521714723
** Paulson, ML For The Working Programmer
*** ISBN 978-0521565431
* Haskell
** Hutton, Programming in Haskell
*** ISBN 978-0521692694
** Hudak, The Haskell School of Expression
*** ISBN 978-0521644082

== Data Structures ==
* Okasaki, Purely Functional Data Structures
** ISBN 978-0521663502

== Typography ==
* Bringhurst, The Elements of Typographic Style
** ISBN 978-0881792065
* Knuth, Computers & Typesetting, Volumes A-E Boxed Set
** ISBN 978-0201734164

= Vague Ideas =
These can be anything from a title missing an edition choice to a topic name to a binding style/colour.

== Theory ==
* Approximation Algorithms
* Randomized Algorithms
* Computer and Intractability (Grey & Johnson)
* Human Computer Interaction (HCI)
* Project Management
** Software Requirements
** Software Design & Architecture
** Software Testing
* Concurrency/Multithreading
* Security (Firewalls)
* Introduction to the Theory of Computation
* Numerical Analysis
* Numerical Methods? (Stoer & Bulirsch)
** This is probably not the actual title. We want a book on numerical methods by Stoer & Bulirsch
* Computer Systems: A Programmer's Perspective (Bryant & O'Hallaron)
* Quantum Computing book (from QIP)
** We have the course text, do we need more on the topic? IQC Recommendation?

== Programming Languages ==
* Python
* Haskell .NET
* Ruby
* C#
* Visual Basic .NET
* OCaml
* F#
* Basic
* Groovy
* Javascript
* C/C++
* Assembly .NET
* Databases [SQL]
* Coq .NET

== Technology Books ==
* Ubuntu
* Unix/Linux Beginner Books
* OpenGL/DirectX
* GTK
* Unix Network Programming

[[Category:Library]]

Books Wishlist

2013-10-22T21:27:08Z

Jladan:

This page consists of books we'd like to get to stock the [[library]]. It is divided into 3 sections. The first is books going on this term's MEF proposal, this should be done by whoever is writing the proposal. The second is a list of actual books with ISBN. The third is vague ideas of what kind of books we need. The goal is for this page to be emptied by way of moving things from section three up to section one and then off.

A bunch of these were bought. That needs to be updated.

Programming Windows by Charles Petzold used to be the definitive guide to Win32
http://www.amazon.ca/Programming-Windows%C2%AE-Charles-Petzold/dp/157231995X/ref=sr_1_1?ie=UTF8&s=books&qid=1269631483&sr=8-1

TCP/IP illustrated (All three volumes $180)
http://www.amazon.com/TCP-IP-Illustrated-Vol-Protocols/dp/0201633469
= MEF Proposal =
MEF Proposal books should include a quote and a sentence or two of justification.

= Actual Books =
Actual books should have a precise title and ISBN for edition desired.

*Coders at work
*Thinking as Computation
** http://mitpress.mit.edu/books/thinking-computation

== j2simpso's suggestions should be sorted ==
*Dreaming in Code
** ISBN 978-1400082469
*Founter's at Work: Stories of Startup's early Days
** ISBN 978-1590597149
*Metaprogramminging GPUs with SH
** ISBN 978-1568812298
*High Performance Computing
** ISBN 978-1566923126
*Critical Testing Processes: Plan, Prepare, Perform, Perfect
** ISBN 978-0201748680
* GREP pocket reference
** ISBN 978-0596153601
* Programming Embedded Systems
** ISBN 978-0596009830
* High Availability and Disaster REcovery
** ISBN 978-3540244608
* An Introduction to Mathematical Cryptography
** ISBN 978-0387779930
* Real Time Systems Design and Analysis
** ISBN 978-0471228554
* The Black Swan: The Impact of the Highly Improbable
** ISBN 978-1400063512

== Non-technical ==
* Mythical Man Month (20th Anniversary ed)
** ISBN 0-201-83595-9
* Natural Harvest - A Collection of Semen-Based Recipes
** ISBN 1-4743-1461-5
* Logicomix: An Epic Search for Truth
** ISBN 978-0747597209

== UI & HCI ==
*Sketching User Experiences
** ISBN 978-0-12-374037-3
*The Design of Everyday Things
** ISBN 978-0465067107
*The Laws of Simplicty
** ISBN 978-0262134729

== Course Textbooks ==
* CSfoo: '''rebind''' CLRS
* CS116: Downey, Python for Software Design: How to Think Like a Computer Scientist
** ISBN 978-0521725965
* CS136: King, C programming
** ISBN 978-0393979503
* CS240: GOODRICH & TAMASSIA:ALGORITHM DESIGN
** ISBN 978-0471383659
* CS246: SAVITCH:ABSOLUTE C++ 4TH ED
** ISBN 978-0136083818
* CS246: MEYERS:EFFECTIVE C++
** ISBN 978-0321334879
* CS365: Sipser, ''Introduction to the Theory of Computation'' SECOND EDITION
** ISBN 0-534-95097-3
* CS462 SHALLIT:SECOND COURSE IN FORMAL LANGUAGES & AUTOMATA THEOR
** ISBN 9780521865722

== Foundations/Field Surveys ==
* Knuth, The Art of Computer Programming
** Volume 1, Fascicle 1: MMIX -- A RISC Computer for the New Millennium
*** ISBN 978-0201853926
** Volume 4, Fascicle 0: Introduction to Combinatorial Algorithms and Boolean Functions
*** ISBN 978-0321534965
** Volume 4, Fascicle 1: Bitwise Tricks & Techniques; Binary Decision Diagrams
*** ISBN 978-0321580504
** Volume 4, Fascicle 2: Generating All Tuples and Permutations
*** ISBN 978-0201853933
** Volume 4, Fascicle 3: Generating All Combinations and Partitions
*** ISBN 978-0201853940
** Volume 4, Fascicle 4: Generating All Trees--History of Combinatorial Generation
*** ISBN 978-0321335708
* Wirth, Algorithms + Data Structures = Programs
** ISBN 978-0130224187
* Dijkstra, A Discipline of Programming
** ISBN 978-0132158718
* Abelson, Structure and Interpretation of Computer Programs
** ISBN 978-0070004849
* Basic Category Theory for Computer Scientists
** ISBN 978-0262660716

== Strict Theory ==
* Recommended by John Watrous: http://www.amazon.com/Computational-Complexity-Approach-Sanjeev-Arora/dp/0521424267/ref=sr_1_1?ie=UTF8&s=books&qid=1276314046&sr=1-1
* [http://www.amazon.com/Computational-Complexity-Christos-H-Papadimitriou/dp/0201530821/ Papadimitriou, ''Computational Complexity''] or newer equivalent
** ISBN 0201530821
* [http://www.amazon.com/Computability-Theory-Chapman-Hall-Mathematics/dp/1584882379 Cooper, ''Computability Theory''] or similar (Cooper is buggy)
** ISBN 1-58-488237-9
* [http://www.amazon.com/Introduction-Kolmogorov-Complexity-Applications-Computer/dp/0387339981/ Li and Vitanyi ''Kolmogorov Complexity and its Applications]
** ISBN 978-0387339986
* [http://www.amazon.com/Cambridge-Tracts-Theoretical-Computer-Science/dp/0521802008 Blackburn, de Rijke, Venema, ''Modal Logic'']
** ISBN 978-0521802000
* Kozen, ''Theory of Computation''
** ISBN 978-1846282973

== Programming Languages ==

* Theory of
** Friedman & Wand, Essentials of Programming Languages, 3rd Edition
*** ISBN 978-0262062794
** Pierce, Types and Programming Languages
*** ISBN 978-0262162098
* C++
** Bjarne Stroustrup, A Tour of C++
*** ISBN 978-0321958310
** Andrei Alexandrescu, Modern C++ Design: Generic Programming and Design Patterns Applied
*** ISBN 978-0201704310
* Scheme
** Friedman, The Little Schemer - 4th Edition
*** ISBN 978-0262560993
** Friedman, The Seasoned Schemer
*** ISBN 978-0262561006
** Friedman, The Reasoned Schemer
*** ISBN 978-0262562140
** Dybvig, The Scheme Programming Language, 3rd Edition
*** ISBN 978-0262541480
* ML
** Reppy, Concurrent Programming in ML
*** ISBN 978-0521714723
** Paulson, ML For The Working Programmer
*** ISBN 978-0521565431
* Haskell
** Hutton, Programming in Haskell
*** ISBN 978-0521692694
** Hudak, The Haskell School of Expression
*** ISBN 978-0521644082

== Data Structures ==
* Okasaki, Purely Functional Data Structures
** ISBN 978-0521663502

== Typography ==
* Bringhurst, The Elements of Typographic Style
** ISBN 978-0881792065
* Knuth, Computers & Typesetting, Volumes A-E Boxed Set
** ISBN 978-0201734164

= Vague Ideas =
These can be anything from a title missing an edition choice to a topic name to a binding style/colour.

== Theory ==
* Approximation Algorithms
* Randomized Algorithms
* Computer and Intractability (Grey & Johnson)
* Human Computer Interaction (HCI)
* Project Management
** Software Requirements
** Software Design & Architecture
** Software Testing
* Concurrency/Multithreading
* Security (Firewalls)
* Introduction to the Theory of Computation
* Numerical Analysis
* Numerical Methods? (Stoer & Bulirsch)
** This is probably not the actual title. We want a book on numerical methods by Stoer & Bulirsch
* Computer Systems: A Programmer's Perspective (Bryant & O'Hallaron)
* Quantum Computing book (from QIP)
** We have the course text, do we need more on the topic? IQC Recommendation?

== Programming Languages ==
* Python
* Haskell .NET
* Ruby
* C#
* Visual Basic .NET
* OCaml
* F#
* Basic
* Groovy
* Javascript
* C/C++
* Assembly .NET
* Databases [SQL]
* Coq .NET

== Technology Books ==
* Ubuntu
* Unix/Linux Beginner Books
* OpenGL/DirectX
* GTK
* Unix Network Programming

[[Category:Library]]

Historical:Webcams

2013-05-30T02:46:27Z

Jladan:

A [http://csclub.uwaterloo.ca/office/webcam live webcam feed] of the office is available online.

== Operation ==

We use [http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome Motion] to serve this webcam feed. It uses video4linux to read from the webcam, and pushes frames to the client (who maintains an HTTP connection). Frames are pushed when a certain amount of motion has detected, or a set maximum amount of time has passed since the last frame. One of these runs on each of our webcam hosts ([[Machine_List#maltodextrin|maltodextrin]] and [[Machine_List#bit-shifter|bit-shifter]]). Motion includes a builtin tiny HTTP server (running on port 8081 in our case) which serves a sequence of JPEG images to the browser. An ordinary <tt><img></tt> tag is embedded in the web page, and browsers will update the image when they receive a new one over the HTTP connection.

The Motion documentation is fairly self-explanatory, but here are the options we use for the webcam server part:

webcam_port 8081
webcam_quality 30
webcam_motion on
webcam_maxrate 5
webcam_localhost off
webcam_limit 1000

== Webcam Counter ==

Also known as the "implicit consent sign". The sign is connected via serial to bit-shifter. Associated scripts which update the counter are found in /opt/camcount/ on bit-shifter.

If the counter isn't working, /opt/camcount/daemon likely needs to be restarted.

== Hardware ==

=== Logitech QuickCam Messenger ===
* USB IDs: 046d:08da
* Kernel module: gspca (gspca-source)
* Max resolution: 640x480

=== Logitech QuickCam Zoom ===
* USB IDs: 046d:08b3
* Kernel module: pwc
* Max resolution: 640x480

=== Logitech QuickCam Web ===
* USB IDs: 046d:0850
* Kernel module: quickcam (qc-usb-source package)
* Max resolution: 480x360

=== Logitech QuickCam Chat ===
* USB IDs: 046d:092c
* Kernel module: gspca (gspca-source)
* Max resolution: 480x360

[[Category:Hardware]]