One of the cool new features of the JavaFX 2.2 developer preview release is a new Canvas node that allows you to do free drawing within an area on the JavaFX scene similar to the HTML 5 Canvas. You can download this release for Windows, Mac, and Linux from JavaFX Developer Preview.

Being adventurous, I decided to take the JavaFX Canvas for a spin around the block. In doing some searching for cool HTML 5 Canvas examples, I came across Dirk Weber's blog comparing performance of HTML5 Canvas, SVG and  Adobe Flash,An experiment: Canvas vs. SVG vs. Flash. This looked interesting for a Canvas beginner as I am, so I decided to copy his implementation and see how it runs in JavaFX.

This turned out to be pretty straight forward. Dirk's original JavaScript application for the HTML 5 Canvas contained a spirograph drawn at the top of the screen with 4 sliders beneath it for changing the number of rotations and particles  and the inner and outer radius for the spirograph. Also, at the top is a text display showing the frames-per-second after the image is drawn. By manipulating the slider properties, the spirograph is drawn differently and each time the performance is shown in frames per second. 

To do the same thing in JavaFX,  I first created a JavaFX Application class, with a Stage and Scene and placed the Canvas at the top of the scene with 4 sliders below it followed by a Label to report the frames per second as defined in Dirk's original JavaScript implementation. One change I made to Dirk's implementation was instead of using Arrays of doubles for points, I used the JavaFX Point2D class. 

My original goal was just to become familiar with the JavaFX Canvas object, but as I played around I noticed something about the performance. When I ran Dirk's HTML 5 and Flash version I would get a consistent frame-per-second rate of 50-70 fps when I adjusted the sliders (Mac OS X 10.7.4, 2.6 GHz Intel Core 2 Duo, 4 GB ram). However, when I ran my JavaFX version, the first time after starting, it drew the spirograph in the low 40s fps. But I noticed that when I adjusted the sliders, the performance got better. First adjustment, low 80s fps; fifth adjustment, mid 120s; a few more and I was getting 1000 fps, and eventually Infinity fps. I didn't believe the Infinity reading, so I debugged to the code, only to find out that it took less than a millisecond to calculate and draw the spirograph.

I assume that this behavior reflects the Hotspot compiler kicking in after a few iterations of the Spirograph calculation. But, it sure is fast. 

The JavaFX source can be downloaded from here: 

SpiroGraph.java

SpiroCanvas.java

Views: 3916

Comment

You need to be a member of Codetown to add comments!

Join Codetown

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

From Camera to Cloud: Netflix’s Scalable Media Processing Pipeline

Netflix has detailed a cloud-based system for scaling camera file processing across global film and TV workflows. The pipeline handles ingest, validation, metadata extraction, and media transformation at scale using FilmLight API and distributed compute. It standardizes workflows across editorial, VFX, and color pipelines, improving consistency and reducing manual handling across productions.

By Leela Kumili

Presentation: Write-Ahead Intent Log: A Foundation for Efficient CDC at Scale

Vinay Chella and Akshat Goel discuss the challenges of running traditional CDC across heterogeneous databases during peak order traffic. They explain how Debezium hit limits under high load and share how they built Write-Ahead Intent Log (WAIL) - a custom architecture that utilizes a dumb producer proxy and a smart consumer pattern to cleanly separate the intent from the state payload.

By Vinay Chella, Akshat Goel

How Lightweight ADRs and Architectural Advice Forums Can Support Architectural Decisions

How we decide is at the core of architecture, and the architecture advice process is a way to decentralize architectural decisions. It needs to be supported by Architecture Decision Records because of the speed at which technology and systems move, and can be complemented by a weekly architecture advice forum.

By Ben Linders

Ky 2.0 Fetch API Wrapper with Revamped Hooks, Smarter Timeouts, and Built-In Schema Validation

Ky 2.0 is an open-source JavaScript HTTP client built on the Fetch API, featuring significant updates such as consolidated hook handling, enhanced timeout management, and improved URL processing. The release includes response validation through schema validation libraries and addresses migration from earlier versions. It aims to provide a lightweight alternative to axios.

By Daniel Curtis

VS Code 1.123 Adds Two-Hour Extension Update Delay to Limit Supply Chain Attacks

VS Code 1.123 adds a two-hour delay before auto-updating extensions to newly published versions, creating a revocation window against supply chain attacks. The delay does not apply to trusted publishers like Microsoft, GitHub, and OpenAI. Similar cooldown mechanisms have now spread across pip, RubyGems, npm, pnpm, Yarn, and Bun.

By Steef-Jan Wiggers

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service