Analysis
Classic analysis: change the chart without re-running it
The analysis CodeXR started with, and still where most sessions begin: one building per file, sized and coloured by the metrics you choose. What 1.2.0 changed is that you no longer have to re-run it to see it another way.
- Swap the chart type from the Field Mapping panel mid-session, without relaunching the analysis.
- The chart types that used to present incorrectly now render properly, and big projects stay readable by showing the top files per metric.
How to read it
The classic analysis measures every file in the folder or project you pointed at, then puts one mark per file on the table. Two things decide what you end up looking at: the chart, which sets the geometry, and the field mapping, which decides what that geometry means.
It opens on Babia Boats, the chart that produces the city. Area is the number of functions in the file, height is its total line count, and colour is its cyclomatic complexity. So a wide, tall, hot block is a long file with many functions and complicated code, and you can see it from across the room without reading a single number.
It is live. Save a file in the editor and that file is re-analysed and the scene updates by itself, so the city keeps up with what you are doing rather than showing a snapshot you have to regenerate.
What the default mapping shows
- Area: the number of functions in the file
- Height: its total line count
- Colour: its cyclomatic complexity
On large projects: the table shows the top files per metric rather than every file, so the scene stays readable instead of becoming a wall.
Eight charts, one table
The chart sets the geometry; the mapping sets the meaning. You swap either one live from the Field Mapping panel, from inside the scene, without losing the analysis.
- Babia Boats
- The default, and the one that reads as a city: a block per file laid out on the table. Maps area, height and colour.
- Bar Chart
- One bar per file along a single axis. Maps an axis and height.
- Barsmap Chart
- Bars across two axes, so a second field groups them into rows. Maps two axes and height.
- Cyls Chart
- Cylinders rather than bars, which adds radius as a third channel.
- Cylsmap Chart
- Cylinders across two axes with radius, the densest of the linear charts.
- Bubbles Chart
- Spheres placed on two axes, with height and radius. The one for spotting outliers.
- Pie Chart
- How one metric divides across the files. Maps a key and a size.
- Donut Chart
- The same proportions as the pie, centre left open.
What the numbers mean
These are the extension’s own definitions: the same glossary the in-room guide shows, generated from the real analysis contracts.
- Total and code lines
- Every line in the file, and the subset that is actual code rather than comments or blanks.
- Comment ratio
- Comment lines divided by total lines.
- Function count
- How many functions were detected in the file.
- Complexity (CCN)
- Cyclomatic complexity: the number of independent decision paths through a function.
- Complexity bands
- A CCN above 10 counts as high, and above 25 as critical.
- Max complexity
- The highest CCN among the functions in the file.
- Parameters
- The arguments in a function signature, reported as an average and a maximum.
- Nesting depth
- How deeply loops and branches are stacked inside a function.
The scene
One building per file, on the table you walk around.
The controller
Field Mapping picks the chart, then the metric behind area, height and colour.
Inside VS Code
The same analysis as a 2D panel, without leaving the editor.
The in-room guide
What you are looking at, explained without taking the headset off.
The other three analyses
The same pedestal serves all four, and the controller switches between them without losing the state of any.
That is one of the four analyses. They all come from the same extension, and the same install.
Install it and run it