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: 3911

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

Leapwork Research Shows Why AI in Testing Still Depends on Reliability, Not Just Innovation

Leapwork recently released new research showing that while confidence in AI-driven software testing is growing rapidly, accuracy, stability, and ongoing manual effort remain decisive factors in how far teams are willing to trust automation.

By Craig Risi

OpenAI Publishes Codex App Server Architecture for Unifying AI Agent Surfaces

OpenAI has recently published a detailed architecture description of the Codex App Server, a bidirectional protocol that decouples the Codex coding agent's core logic from its various client surfaces. The App Server now powers every Codex experience, including the CLI, the VS Code extension, and the web app, through a single, stable API.

By Eran Stiller

Does AI Make the Agile Manifesto Obsolete?

Capgemini's Steve Jones argues AI agents building apps in hours have killed the Agile Manifesto, as its human-centric principles don't fit agentic SDLCs. While Forrester reports 95% still find Agile relevant, Kent Beck proposes "augmented coding" and AWS suggests "Intent Design" over sprint planning. The debate: Is Agile dead, or evolving for AI collaboration?

By Steef-Jan Wiggers

Article: Proactive Autoscaling for Edge Applications in Kubernetes

Kubernetes often reacts too late when traffic suddenly increases at the edge. A proactive scaling approach that considers response time, spare CPU capacity, and container startup delays can add or remove instances more smoothly, prevent sudden spikes, and keep performance stable on systems with limited resources.

By Rajeev Kallayil Ravi

Chrome 144 Ships Temporal API: Advancing JavaScript Date/Time Standardisation

Chrome 144 introduces the groundbreaking Temporal API, revolutionizing date and time management in JavaScript. As a modern alternative to the criticized Date object, Temporal resolves parsing ambiguities, time zone complexities, and mutable arithmetic. With distinct types and built-in support, it empowers developers to handle dates seamlessly, though adoption varies across browsers.

By Daniel Curtis

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service