Sketch is a Common Lisp environment for the creation of electronic art, visual design, game prototyping, game making, computer graphics, exploration of human-computer interaction and more. It is inspired by Processing Language and shares some of the API.
Since April 2016, Sketch is available in Quicklisp, Common Lisp’s de facto package manager. This makes getting and running Sketch as easy as
(ql:quickload :sketch)
To make Sketch run correctly, though, a few requirements must be met.
Sketch should be compatible with all major Common Lisp implementations and all major operating systems - more specifically, all CL implementations and operating systems that cl-sdl2 runs on. Incompatibility with any of those is considered a bug.
Sketch is known to work with:
- CCL 1.11 on Mac OS X El Capitan
- CCL SVN 1.12.dev.r16617 on Arch Linux
- CCL 1.11 on Windows 10 64bit
- SBCL on Debian Unstable
- SBCL 1.2.16 on Arch Linux
- SBCL 1.3.1 on Linux Mint 17
- SBCL 1.3.6 on Windows 10 64bit
Sketch is known to not work with:
- SBCL 1.2.15 on Mac OS X
Sketch can’t handle input and the window’s titlebar is black. These kinds of issues are a known problem with Mac OS X, because it needs its GUI threads to be main, and CCL is the only lisp that accounts for that out of the box. There are ways to counter this, but until a solution finds its way into this repository, SBCL on Mac OS X will stay on this list. In the meantime, use CCL.
If you test Sketch on other systems, please send a pull request to include your results.
SDL2 is currently Sketch’s only backend. It is a C library which you will need to download manually from libsdl webpage. Select the release compatible with your operating system, or compile from the source code.
For loading image and font files, Sketch relies on SDL2 Image and SDL2 TTF, respectively, both part of the SDL project.
Some users have reported that libffi needed to be installed to make Sketch work.
Sketch requires graphics hardware and drivers with support for GL version 3.3.
Sketch works on both CCL and SBCL, but installing all prerequisites might not be as straightforward as it is on the other platforms.
Download SDL2, SDL2_IMAGE and SDL2_TTF dlls from libsdl webpage and copy them somewhere Windows can find them - \Windows\System32
will work. When copying SDL2_TTF, make sure to copy all of the dlls provided in the archive, and not just the TTF one.
Now you will need to get a libffi dll. One of the ways of doing this is compiling from the source, but for a quick and easy solution, you can just find a trusted source and use their version. For example, if you are using Emacs on Windows, you can find libffi-6.dll
in emacs\bin
. Copy it to the same directory you copied sdl2 dlls to earlier.
To bootstrap cffi-libffi, you are going to need a C compiler, more specifically the one from the GNU Compiler Collection. Also, libffi headers and pkg-config are needed. Luckily, you can get all these things (and more) with MSYS2. Go to https://msys2.github.io and follow the instructions for installing the 64bit version.
From its console, install gcc, libffi headers and pkg-config by running pacman -S gcc libffi libffi-devel pkg-config
.
From the Control Panel, open System properties, go to the Advanced tab, and click “Environment Variables…” - or click the Start button, start typing “environment” and select “Edit the system environment variables”.
Double click “Path” from the list of System variables and make sure that both your lisp implementation’s path (something like C:\Program Files\Steel Bank Common Lisp\1.3.6\
) and MSYS path (probably C:\msys64\usr\bin
) are listed. If not, click “New” and add them now.
If you needed to change anything here, restart the computer now.
If you are using SLIME, you won’t be able to load or run Sketch if you start SWANK from emacs (by running M-x slime
). Instead, you should open the Command Prompt (the regular one, not MSYS), start your lisp and eval (ql:quickload :swank)
(swank:create-server)
. From Emacs, type M-x slime-connect
, and finally, press enter twice (for localhost and port 4005).
If you did everything correctly, you should be able to (ql:quickload :sketch)
and move on to the tutorial.
Please make sure to also get the following libraries to your local-projects
directory. This is not necessary otherwise.
To get a feel for what Sketch can do, and also to make sure that everything has been installed correctly, you can look at the examples. The code below will run all four currently provided examples at once. Note that on older machines running four sketches at once might result in a small degradation in performance, so you might want to run sketches separately.
CL-USER> (ql:quickload :sketch-examples)
CL-USER> (make-instance 'sketch-examples:hello-world)
CL-USER> (make-instance 'sketch-examples:sinewave)
CL-USER> (make-instance 'sketch-examples:brownian)
CL-USER> (make-instance 'sketch-examples:life) ; Click to toggle cells,
; any key to toggle iteration
In all the following examples, we’re going to assume that Sketch is loaded with (ql:quickload :sketch)
, and that we’re in package :TUTORIAL
, which is set to use :SKETCH
.
CL-USER> (ql:quickload :sketch)
CL-USER> (defpackage :tutorial (:use :cl :sketch))
CL-USER> (in-package :tutorial)
TUTORIAL> ;; ready
NOTE: This tutorial is using the revised DEFSKETCH
macro, introduced in May 2016. Until this release hits Quicklisp, you’ll have to install Sketch manually to your local-projects
directory, along with https://github.com/lispgames/cl-sdl2 and
https://github.com/lispgames/sdl2kit. More about this here.
Defining sketches is done with the DEFSKETCH
macro, that wraps DEFCLASS
. Using DEFCLASS
is still possible, but DEFSKETCH
makes everything so much easier, and in these examples, we’re going to pretend that’s the only way.
(defsketch tutorial ())
(make-instance 'tutorial)
If all goes well, this should give you an unremarkable gray window.
Let’s draw something!
(defsketch tutorial ()
(rect 100 100 200 200))
(defsketch tutorial ()
(dotimes (i 10)
(rect (* i 40) (* i 40) 40 40)))
(defsketch tutorial ()
(dotimes (i 10)
(rect 0 (* i 40) (* (+ i 1) 40) 40)))
(defsketch tutorial ()
(dotimes (i 10)
(rect 0 (* i 40) (* (+ i 1) 40) 40))
(circle 300 100 50))
(defsketch tutorial ()
(line 0 0 400 400)
(line 400 0 0 400))
(defsketch tutorial ()
(polyline 100 100 200 150 300 100
200 200 100 100))
(defsketch tutorial ()
(polygon 100 100 200 150 300 100 200 200))
(defsketch tutorial ()
(dotimes (i 4)
(ngon (+ i 3) (+ 50 (* i 100)) 200 20 20 (* i 20))))
(defsketch tutorial ()
(bezier 0 400 100 100 300 100 400 400))
Grayscale imagery is nice, but let’s add color and make our sketch more vibrant. Assuming that you’re using Emacs + SLIME, or a similarly capable environment, you can just re-evaluate with the following code:
(defsketch tutorial ()
(background +yellow+))
The window becomes yellow. There are a couple of things to note. Drawing code doesn’t need to go into a special function or method, or be binded to a sketch explicitly. DEFSKETCH
is defined as (defsketch sketch-name bindings &body body)
: that body is your drawing code. We will get to BINDINGS
later. The other thing is that Sketch comes with its own color library.
There are constants for commonly used colors: +RED+
, +GREEN+
, +BLUE+
, +YELLOW+
, +MAGENTA+
, +CYAN+
, +ORANGE+
+WHITE+
, and +BLACK+
.
If you want to be more specific about the colors you want, you are welcome to use (rgb red green blue &optional (alpha 1.0))
, (hsb hue saturation brightness &optional (alpha 1.0))
or (gray amount &optional (alpha 1.0))
. The arguments to these functions are values from 0 to 1. You can use these functions in the same way you just used +YELLOW+
. Hopefully the function names and their arguments are self-explanatory, but if not, you can learn about the RGB color model here and about HSB (also called HSV) here. (gray amount &optional (alpha 1.0))
is really just a convenient alias for (rgb amount amount amount &optional (alpha 1.0))
, and can be used for brevity when a shade of gray needs to be defined.
This might be a good place to note that function names in Sketch use the American English spellings, like “gray” and “color”. It’s just a choice that needed to be made, in pursue of uniformity and good style.
(defsketch tutorial ()
(background (rgb 1 1 0.5)))
This will give you a lighter yellow.
All functions have an additional, ALPHA
parameter. It determines the amount of transparency that the color should have.
Sometimes it’s easier to think about color values in non-normalized ranges. That’s why Sketch offers RGB-255
, HSB-360
, and GRAY-255
.
This is how these functions map to their normalized variants.
(rgb-255 r g b a) | (rgb (/ r 255) (/ g 255) (/ b 255) (/ a 255)) |
(hsb-360 h s b a) | (hsb (/ h 360) (/ s 100) (/ b 100) (/ a 255)) |
(gray-255 g a) | (gray (/ g 255) (/ a 255)) |
HSB-360
is using different ranges, because hue is represented in degrees (0-360), and saturation and brightness are represented as percentages (0-100).
If you are used to working with colors in hex, like in CSS, you can use (hex-to-color string)
, where STRING
is the color in one of the following formats: “4bc”, “#4bc”, “4bcdef”, and “#4bcdef”.
If you don’t care about fiddling with the exact values, but still need different colors, you can use one of the following functions.
Lerping is a fancy way of saying linear interpolation. This function takes the starting color and the ending color, and returns the color between them, which is an AMOUNT
away from the starting color. When AMOUNT
equals zero, the returned color equals the starting color, and when AMOUNT
equals one, the ending color is returned. Amounts between zero and one give colors that are “in-between”. These colors are calculated according to the specified MODE
, which is :HSB
by default, meaning that the resulting color’s hue is between the starting and ending hue, as is the case with its saturation and brightness.
(defsketch lerp-test ((title "lerp-color") (width 400) (height 100))
(dotimes (i 4)
(with-pen (make-pen :fill (lerp-color +red+ +yellow+ (/ i 4)))
(rect (* i 100) 0 100 100))))
Returns a random color. You probably don’t want to use this, because much of the returned colors are either too dark, or too light. You do get to choose the ALPHA
value, though.
(defparameter *colors* (loop for i below 16 collect (random-color)))
(defsketch random-color-test ((title "random-color") (width 400) (height 100))
(dotimes (x 8)
(dotimes (y 2)
(with-pen (make-pen :fill (elt *colors* (+ x (* y 8))))
(rect (* x 50) (* y 50) 50 50)))))
This is probably the function you’re looking for, if you just want to create a non-repeating set of colors quickly. It maps all numbers to “interesting” (not too dark, not too light) colors. You can use this for coloring procedurally generated objects, when prototyping and just trying to make things look different quickly, when making palettes, looking for “the right” color, and many other things.
(defsketch hash-color-test ((title "hash-color") (width 400) (height 100))
(dotimes (i 128)
(with-pen (make-pen :fill (hash-color i))
(rect (* i (/ 400 128)) 0 (/ 400 128) 100))))
Sometimes you have a color, and would like to transform it in some way. That’s what color filters are for.
TODO
TODO
TODO
TODO
TODO
TODO
TODO
TODO
TODO
TODO
I’m trying to compile my defsketch definition, but it keeps telling me that :TITLE (or :WIDTH, :HEIGHT, etc.) is not of the expected type LIST. Why is this happening?
You’re probably trying to use the old way of defining sketches - (defsketch name window-parameters slot-bindings &body body)
. DEFSKETCH
has been changed to (defsketch name bindings &body body)
. It’s still possible to define the title and other window parameters, though.
Example:
(defsketch foo (:title "Foo" :width 400)
((a 3))
(rect 100 100 200 200))
;;; Becomes
(defsketch foo
((title "Foo")
(width 400)
(a 3))
(rect 100 100 200 200))
For more, read about “Bindings” in the tutorial above.
For everything else, read the code or ask vydd at #lispgames.
Go make something pretty!
Copyright (c) 2015, 2016 Danilo Vidovic (vydd)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.