• re-implement "Data Inspector" in HexView #4
• Entropy detection #1
• histogram (1, 2, 4 byte blocks)
• simple range annotation
• create FormatInfo fields from context menu
• faster implementation of RangeList (intervaltree?)

Currently SmartSelection matches can be selected from the context menu of the selection:

It would be useful to allow selecting matches by directly clicking on them, e.g. ctrl-click on a match.

• rename ObjectWindow to DataSourceWindow?
  • or DataWindow? or some even better name?
  • or atleast in the UI to "Data Window"?
• rename Selection Heuristics to SmartSelection?

siehe binwalk

parse binary only to get reassemble_into and store_into lists, without producing range-annotated hexdump

• ENTER for run
• treeview durch textbox o.ä. ersetzen

General

• ??? how to handle parse_with, reassemble_into, store_into
• convert expressions to C
• ...numeric
• ...array/member (helper functions)

Generate readers - similar to parse methods, but with static calls instead of loops over self.children

• read bytes and fixed from tvb (see also issue #10)
• generate struct reader (generate sequential code to parse children one by one)
• generate repeat reader (parse child in loop)
• generate variant reader (generate sequential code to try variants until one succeeds)

FixedFieldFI currently specifies types with the python struct.pack type syntax.

changing this to wireshark's field types ("L" --> FI_UINT32 etc) would make generating wireshark dissectors easier and more predictable

also, the ws field types are kind of more powerful (more string types) and have useful predefined types (ip, mac address)

• "save as" for new files should start in project directory - currently it starts in "/" or some last-used location
• all file extensions should be allowed - currently (at least on macOS) a ".txt" suffix is forced

wenn man in Data source options den typ wechselt, verschwindet der inhalt der typspezifischen felder in der ansicht, ist aber intern noch gespeichert

sondern öffnet ein zweites Mal

• less whitespace (optional?)
• remember columns [(title, content, order, size)]
• payload view (hex, ascii, ...?)
• diff view
• highlighting
• filtering
• find
• ...

Info-toolbar? Save-button?

add a field type (or a param / expression syntax for VarByteFieldFI) to allow easy specification of padding fields (pad to length, pad to multiple of N)

display selected bytes as various int/uint types

Hi!

The length highlighting in the hex view is super neat, but when selecting the length field of a long-ish packet that does not fit on the screen completely, the highlighting disappears when scrolling down to find the end, even though the length field stays selected.

(tested on the pypi release)

allow user to parse only a selected range of a ByteBuffer with the grammar, not the whole ByteBuffer

Data inspector kindof allows this already

maybe just implement a data inspector which can use a grammar from the project instead of from the separate file?

or some other way to say "all bytes until \0" or "all bytes until \r\n" or "all ascii chars until first non-ascii" etc