Skip to main content

Scaling and Text

An obvious question about the CDK rendering code is : "Why not scale text with AffineTransform?" So, of course this is possible, and works quite nicely - but there is a cost.

One of the goals of the rendering code is to start from models of any scale, and render them as consistently sized diagrams on screen. By 'scale' here I simply mean the average distance between points. So the CDK layout code might use a distance of (say) 1 between two carbon atoms, but a file with a structure made in some other chemical editor might have an average atom-atom distance of 100. These are unitless values, by the way.

Now, what we could have done was transform the coordinates in the model to a consistent scale, then rendered these transformed coordinates. What we chose to do, however, was to calculate a single transform for the model and draw with this. If you use this transform to scale the graphics object before drawing you get this for a model scale of 10:

and this for a model scale of 100 (in other words a 'bond length' of 100):

the images are at slightly different zooms, but the point is clear I think. The choice is between scaling fonts independently, and altering the model directly.


chem-bla-ics said…
Why is the font size smaller in the second example? It seems it is not scaled?
gilleain said…
This was the whole point! :)

The font size is smaller because the scale is smaller. The world distance between A-B is more in the second one, so a smaller scale is needed to put it on screen.

Say the A-B distance is 10 or 100, then the scale necessary to draw a line on screen of 300px is either 30 or 3, respectively. The font size is scaled by the same amount.
Ralf Stephan said…
Well, you point to one thing in this post. There are many other factors and fundamental limitations to include:

1. how is the font specified, binary or vector? Binary fonts cannot be scaled without loss of quality
2. does the user have preferences? some like big atom symbols some not. Either way, they should have a choice
3. can the description of the molecule be converted to a vector description? this is a must nowadays, also the conversion must be identical to what's onscreen. It's so annoying to have the SVG output of a nice formula change the font used and fine-positioning lost

what follows is that normal bitmapped fonts cannot be used. also, as you say, no absolute measure of font size will suffice because what should be constant within the molecule is the ratio font size/bond length. there is no way to accomplish this except with a vector font and an independent measure like height of A divided by the distance of C-C in ethane. If this metric is set to a reasonable value, this value can be changed then by the user.

what do you say?

Ralf Stephan
(written with JCP in mind)
gilleain said…
From a user point of view, it's definitely an important goal to be able to specify exactly the font size, and to have that exported properly.

The difficulty - as always - is implementing it! Since I made this post, I've learned a few things about drawing fonts in chemical reactions, and it is possible to have nicely scaled fonts - but I did end up using AffineTransforms in combination with FontMetrics, and various other tricks.

One important point that was brought up by Egon was the need for scaling the font as a proportion (like 50%, 120%, etc) rather than some magic number. I agree that should be part of a high-level API, but in my experience it is usually necessary to say "12pt" or other exact measures.

Basically, I will have to take another look at the font management in the CDK. It looks like you've been doing some great work reviving the project (I'm following on github) so perhaps this is a good time to push through all the CDK-graphics changes.


Popular posts from this blog

Common Vertex Matrices of Graphs

There is an interesting set of papers out this year by Milan Randic et al (sorry about the accents - blogger seems to have a problem with accented 'c'...). I've looked at his work before here.

[1] Common vertex matrix: A novel characterization of molecular graphs by counting
[2] On the centrality of vertices of molecular graphs

and one still in publication to do with fullerenes. The central idea here (ho ho) is a graph descriptor a bit like path lengths called 'centrality'. Briefly, it is the count of neighbourhood intersections between pairs of vertices. Roughly this is illustrated here:

For the selected pair of vertices, the common vertices are those at the same distance from each - one at a distance of two and one at a distance of three. The matrix element for this pair will be the sum - 2 - and this is repeated for all pairs in the graph. Naturally, this is symmetric:

At the right of the matrix is the row sum (∑) which can be ordered to provide a graph invarian…

Generating Dungeons With BSP Trees or Sliceable Rectangles

So, I admit that the original reason for looking at sliceable rectangles was because of this gaming stackoverflow question about generating dungeon maps. The approach described there uses something called a binary split partition tree (BSP Tree) that's usually used in the context of 3D - notably in the rendering engine of the game Doom. Here is a BSP tree, as an example:

In the image, we have a sliced rectangle on the left, with the final rectangles labelled with letters (A-E) and the slices with numbers (1-4). The corresponding tree is on the right, with the slices as internal nodes labelled with 'h' for horizontal and 'v' for vertical. Naturally, only the leaves correspond to rectangles, and each internal node has two children - it's a binary tree.

So what is the connection between such trees and the sliceable dual graphs? Well, the rectangles are related in exactly the expected way:

Here, the same BSP tree is on the left (without some labels), and the slicea…

Signatures with user-defined edge colors

A bug in the CDK implementation of my signature library turned out to be due to the fact that the bond colors were hard coded to just recognise the labels {"-", "=", "#" }. The relevant code section even had an XXX above it!

Poor show, but it's finally fixed now. So that means I can handle user-defined edge colors/labels - consider the complete graph (K5) below:

So the red/blue colors here are simply those of a chessboard imposed on top of the adjacency matrix - shown here on the right. You might expect there to be at least two vertex signature classes here : {0, 2, 4} and {1, 3} where the first class has vertices with two blue and two red edges, and the second has three blue and two red.

Indeed, here's what happens for K4 to K7:

Clearly even-numbered complete graphs have just one vertex class, while odd-numbered ones have two (at least?). There is a similar situation for complete bipartite graphs:

Although I haven't explored any more of these…