My own Radix viewer (JavaScript version). First version only w/ viewing functionality..
Note
When I talk about the radix, I mean the numeric base (decimal, binary/dual, ..).
- [2025-04-02] Update: better
util.js; and now also w/ new parameter--summary; - [2025-03-24] Update: new utils
sum. ... and a bit more, AFAIR. - [2025-03-24] Newest update: the
dumpnow also supports--countand--count-sort.
- Introduction
- Example Screenshots
- Download
- Utilities
- Comments/F.A.Q.
- Links
- Contact
- Copyright and License
It became necessary since I wanted to inspect the changing data of my Norbert.
It's more than a Hex viewer.. it's rather a Radix viewer; which will become a Radix Editor in some time. I'm working on it just a little bit right now, since it's not the most important project for my purposes. But it became necessary, so I invented it.
Tip
JFYI: Radix is my word for a numeric base. The decimal system with base 10, hexadecimal with 16, or binary with 2. So this project aim's to let you see input/file data in a specificly converted view.
I found out such a code like it's also the hexyl is really easy. Don't
know exactly how hard this will get when I will extend it (got a big TODO for this one). But it was a cake of piece
until now (even without looking at the hexyl source code).
The default 'runtime' parameters are not listed here. They got inserted by the startup shell scripts.
Look at the param.json:
--refresh(Integer/Boolean)--radix(Radix)--path(File)--ansi(Boolean)--head(Boolean/Integer/String)--tail(Boolean/Integer/String)--start(Integer)--stop(Integer)--replace(Radix/Boolean)--heat(Integer)--color(String/null)--filter(Boolean)--modulo(Radix/Boolean)--follow(Boolean)--high(String/Integer)--without(String/Integer)--only(String/Integer)--count(String/Integer/Boolean)--count-sort(String)
And here with the param.util.json:
--radix(Radix)--sort(Boolean/null)--offset(Integer)--size(Integer)--locale(Boolean)--ansi(Boolean)--pairs(Boolean)--sep(String)--list(Boolean)--spaces(Integer)--empty(Boolean)--high(String/Integer)--without(String/Integer)--only(String/Integer)--printable(Boolean)--silent(Boolean)--summary(Boolean)
The Boolean values are either without any value assignment, which sometimes causes problems when the
command line continues with non-key-parameters, then these would be assigned to the keys. Or they can
be written out (which is my recommendation) as follows: [ yes, no, on, off ];
There are (very less) parse functions to interprete your parameters.
Mostly it's the color string parser, which interpretes RGB input colors (separated by , or ; (optionally)).
And for the --without or --only you can also define more than one byte, separated via ,, and even byte
ranges via -. The (optional) last + separator to define the step. The last (also optional) parameter is
the input value radix/base, which will be used to interprete your input numbers; it's separated by a regular
slash /.
So e.g., when you want to show only even/odd numbers, e.g. try --without/--only '0-255+2'. Another example
can be --high '0-ff+f/16' (so mask all bytes between the hexadecimal values 0 to ff, with a step of
the hexadecimal f (so all 15 bytes).
The colors can be defined via three bytes separated by comma ,; more colors separated via ; as whole,
or more comma ,. It doesn't really matter, but please do not combine both in one parameter.
If defined empty (or with yes/no/on/off), size will automatically be adapted to your console's height.
It can also be an integer for the target line count; or a string with a '%' suffix, so you can define a percentage of your console's height.
Tip
With the newest version I also added the check for many null \0. Any empty line would so be summed up,
to see only one line with the info how much lines and bytes (with size) were ignored.
Update: looking for same bytes, not only the null.
This is a newer preview screenshot. Updated design, styles/colors, parameters, and more.
Here's a newer dump/utility, one to count any bytes in a file (for possible parameters see the
param.util.json, and the config.util.json
maybe).
Note
If you've other ideas for possible dump utilities, please mail me.
Tip
Now there's also the rot13 and the sum utility available. I really needed it here! ^_^
And this is showing the --replace feature.
at least
Warning
The following screenshots are a bit older, so neither the command line parameters are updated there, nor the colors/design. JFYI.
And this is a newer one, with less extensions and a newly configured configuration,
mostly with better colorization, plus the feature to not insist on a simple replacement character for
non-printable or ANSI characters, but to draw a radix converted view on it - whereas I'd like to use
the 2 to let the user see if the byte is even or odd. ;-)
My latest feature: I wanted to analyse some abstract complexity in my A.I. header data by looking at it in binary,
by doing a modulo operation. To directly see the structure or any abnormality or similarity or smth. like it, the
last thing was to colorize the bits (other bases also possible..). That's the result (and I really figured my
problem out) (and btw, superseded by the --heat, below):
Extended the latest feature to see kinda heatmap; this way I really saw how much my values are distributed over the header data.
You can download it by browsing the ./src/. It's a Node.js sub project.
js/: the 'real' code; one startup scriptmain.js(fordump.sh), thedump.js,util.jsand thehelper.js;json/: two configuration files (config*.json) and two schemes for the possible argv parameters (param*.json);sh/: startup (bash) shell scripts; in general I'm massively using such helper scripts (enivironment preparations);
I think in the future I'll also provide an easy setup/install script. But not for now. We'll see..
Tip
At the moment I prefer to use the newest dump.printable.sh (which
is actually just a wrapper around the dump.count utility) with my preferred settings (TODO?).
Additionally, my configuration .json file will have a better structure. It all was quick-and-easy setup for me,
but the more config parameters will come, the more structure they need .. and gonna have.
Note
I'm using my .json configuration with the help of my
config.js.
Note
I'm also using my own JSON.js project in here.
This is why you can see the comments in my config.json.
Important
This project relies on my own JavaScript infrastructure.
So you can only see the code of this sub project. It doesn't really run stand-alone.
If you'd like to use it, you could bring in your own polyfill. .. in case you don't
want to wait until I'm going to run my
init-sub-proj.sh.
I also needed some helping utilities for my purposes, so I started here.
Use the dump.util.sh for an overview, and also to directly call the
utilities which are shown in this script. But there are also shell scripts for each
available one.
These are the only available utilties (atm):
They all require at least a file path parameter and can also make us of all the available parameters.
Tip
The rot13 utility expects a single integer value (without any key) for the value
to add/sub to any input byte. Without this parameter it automatically uses the
13 (see Rot13).
Note
All the utils all supports some general parameters/arguments. The most important
should be --only and --without. For the rest see the command line parameters.
I'm massively using tmux,
and this doesn't seem to support cursor load (\e[u) nor save (\e[s)! :-/
If you think this project could be beneficial to you, or if you're simply interested in trying it out, please send me a mail expressing your interest, or create an issue here on GitHub.
Once we have enough requests, I'll make the effort to get everything up and running for you all.
I mention this project here because I often used it before I came up with my own solution.
In the future, when I'm extending this code base, I think I'm going to see this foreign project as an example for me. Like more colors for different types of byte data, and more.
The Copyright is (c) Sebastian Kucharczyk, and it's licensed under the MIT (also known as 'X' or 'X11' license).
