dadido3/d3hex

The first dataflow based Hex-Editor!

d3hex's Issues

Add disassembler node

Capstone seems to be perfect for this

Add zlib node

A node which can read zlib data and output the content for further usage. To make random access possible, we need to create some sort of index first:
http://lh3.github.io/2014/07/05/random-access-to-zlib-compressed-files/

I don't know if it's possible to write data in the middle of the stream. But appending data should be possible.

Add more data types to the Data Inspector node

• Date and timestamps
• Colors

Create help

HTML based help for D3hex and all its nodes

Implement Boyer-Moore search algorithm

Smarter write algorithm for the history node

All history operations are written one after another, even if they are overwritten by another operation later on. Simplifying the history list, or using a different algorithm should fix some speed problems. Right now shift operations shift all bytes. This can be a big slowdown factor if there are several of those operations on very big files.

Add signal generator node

Outputs signals (sine, sawwave, rectangular, ...) as array of different types (signed/unsigned int, float)

Improve data and number input fields

Create new gadget with option to choose between several input formats:
Formats:

• Hexadecimal: 1A B2 55 FF or 1ABCDEF
• Decimal: 26 178 85 255 or 28036591
• Octal: 32 262 205 377 or 152746757
• Binary: 0011010 10110010 10000101 11111111 or 1101010111100110111101111

Perhaps use prefixes to define the number system. Like $ or 0x for hexadecimal and % or 0b for binary numbers.

For numbers, accept SI prefixes (Also the binary IEC version: ki, Mi, Gi, Ti, ...) after the number.

Add Julia scripting node

Node, which can be completely defined by a script written in Julialang.
But this needs the user to have Julia installed on their PCs.

Store/Restore window states/positions

Correct the event-range for event-forwarding

Fix crash with circular connections

Support different code pages

Make it possible to sync cursor position, selection and viewport between nodes

Only redraw updated chunks on an update event in View2D

Finish data descriptors

Ideas:

• 1D, 2D, 3D Array or single element
  • Element type ((Un)signed Int, Float, String)
  • Byteorder
• Filetype
  • File extension
  • Mime, Some sort of identifier

Store history operations in the node configuration

But limit (Or atleast give a warning and ask the user) it to a specific amount, so it won't blow up the node configuration file if you have a several gigabyte large history.

Correct the range for segments

Add clipboard data source

Lets you read and write the clipboard data of your OS.

Add audio playback node

Playback any kind of data, array.
Example: Audio data retrieved from the audio converter node.

Add result list to the search in the Editor node

A list of the previous results, clickable for sure

Improve history node window

recreate history node window to show a list of undo operations with symbols and fancy stuff

Create window for the dummy node

Show current size and have a button to reset the node.

Add text editor node

Will work with tremendously huge texts, believe me. It will be great, it will be the best node you have ever seen, and we will make the mexicans pay for it. 100%

New set of icons

Use http://www.famfamfam.com/lab/icons/silk/ for most stuff. Recreate others in similar style

Create API to handle windows/gadgets from Julia

Preferably with PureBasics dialog library.

Create module for software settings

Hierarchical settings with standard values and stuff. With a GUI to modify settings nicely. Should also contain settings for each node type. Additionally this system can be used to provide a simple GUI for Julia scripts.

Make history node more efficient

Precalculate some sort of tree or list. Anything should be better than iterating through all changes, even though it works fast enough below 20000 history operations.

Forward segments in the binary operation node

Add network bridge node

A node which you can connect to another network bridge node over the network. This allows you to share an output over several instances of D3hex, even on different computers over the internet. (Given that the needed ports are forwarded and firewalls are not blocking anything)

Implement offset parameter into View1D

Add image format converter

Converts an image to an array of colors (To be displayed via View2D).
May work for encoding and decoding.

Object: Data-Source verifier

Checks if a Data-Source works correctly.

Add logging system, replace old error message window

Add logging system, improve how errors or warnings are shown.

Add serial port data source

Lets you read and write from/to a serial port. (Similar to the network terminal)

Add compare node

Lists differences between two inputs

Add split node

Node to split data into several outputs.
Should also give you the possibility to get subarrays out of arrays

Add option to generate cryptographically secure numbers in the Random node

As these will be non deterministic, the node will output a different random sequnce for each data request for the same offset.

Improve Hash Generator node

• Let the user input a list of hashes to be highlighted
• Give the user the ability to copy hashes

Add statistics, math nodes

Statistics:

• Entropy (Chunk based and over all)
• Mean, mode (Chunk based and over all)
• Max, Min (Chunk based and over all)
• Histogram (1D, 2D, 3D, shifted)

Signal processing:

• Crosscorrelation, Autocorrelation
• Discrete fourier transformation
• Convolution

Math:

• Basic math operations

View3D

Improve random number generator in the random node

It's has big flaws for now

Support more pixel formats in View2D

Examples:

• 1 bpp Black and white
• 2 bpp Gray
• 4 bpp Gray
• 16 bpp ARGB4444
• 16 bpp RGBA4444
• 16 bpp RGBA5551
• 32 bpp Gray
• Allow any other color palette via additional input

Rewrite the node editor

• Use vector drawing library
  • Draw links with splines or bezier curves
  • Simplify l,ook
  • Visualize data transfer as moving dots or something
• Fix the position cleanup algorithm
• Make it possible for nodes to draw onto the node objects
• Show nodes while dragging them into the workspace, even if it is just the outline
• Use something better than the tree list. It uses too much space. Create a new popup window with search bar and symbols for nodes.

Correct negative offsets in View2D

One line of the image is invisible when using negative offsets

Add audio format converter

Converts audio files to an array of numbers. May work for encoding and decoding

Add cheat engine like node

Node to search for numbers, strings or any other data. It will display occurrences and their offsets in a list. These entries can then be filtered with other/newer values, until only the desired entries are left.

Add physical and logical drives as data source

Physical: Gives raw access to a physical drive. You can view/edit the partition tables, the partitions and everything else.
Logical: Gives raw access to a signle partition.

Redo drawing of the View2D node

The single images/chunks should always be of the same size in the screenspace, and therefore contain more data the more you zoom out. Furthermore, the node should get data in fewer big request, and not a request per line.

Add verifier node

Node containing methods to verify other nodes. For example:

• Behaviour of a node if a data request exceeds its given size or goes below 0
• Write and verify written data
• Verify shift operations
• Performance measurement of read, write and shift operations