Skip to content

serene-ding/svg-essentials-examples

 
 

Repository files navigation

SVG Essentials Examples

This repository contains interactive examples and other files created for SVG Essentials, 2nd Edition by J. David Eisenberg and Amelia Bellamy-Royds (O'Reilly, 2014). The repository also includes the examples used in a related post on the O'Reilly Radar blog.

Cover image of SVG Essentials

If you're reading the online version of the book, you'll see these examples embedded in your browser (they are hosted as Github pages). If you're reading the print book or PDF/ePUB/Kindle formats, these are the examples given as links.

Many examples display the code as well as the final SVG, and the code can usually be live edited; type within the code blocks that have a green border, or use the drop-down lists to switch between options, then select “Refresh” to see the results, or “Reset” to undo.

To save on typing long URLs, here's an index of all the interactive examples:

If you've stumbled upon this page and don't yet have your copy of SVG Essentials, be aware that the above outline only includes the interactive examples; there are some topics which were easier to describe with good old-fashioned code snippets and figures.


The examples are covered by the standard example permissions policy for O'Reilly books, reproduced below for your convenience:

Using Code Examples

Our books are here to help you get your job done. In general, you may use the code in our books in your programs and documentation. You do not need to contact us for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from our books does not require permission. Answering a question by citing our books and quoting example code does not require permission. On the other hand, selling or distributing a CD-ROM of examples from O'Reilly books does require permission. Incorporating a significant amount of example code from our books into your product's documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN.

If you think your use of code examples falls outside fair use or the permission given here, feel free to contact us at [email protected].

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • HTML 79.0%
  • XSLT 7.2%
  • Java 4.3%
  • Perl 3.9%
  • JavaScript 2.6%
  • OCaml 2.4%
  • Other 0.6%