gcarreno / laz-json-viewer Goto Github PK

• Create a non visible panel to hide the TSynEdit
• DO NOT FORGET THE READ-ONLY!! ;-D
• Add an action to show/hide the panel
• Upon completion don't forget to credit Craig (@chapmanworld)

I'm using:

function IntToBin(
  Value: LongInt;
  Digits: Integer;
  Spaces: Integer
):string;

The function IntToBin() has an overload that takes an Int64:

function intToBin(
  Value: Int64;
  Digits: Integer
):string;

And I think I see my issue. I love me some rubber ducking, LOL!!

This means I need to see if I can have the spaces every 8 bits on the overload or I need to process that after calling it.

• Add path to record
• Include path in recursive call to build VST
• Correctly fill the NodePath with the appropriate value for it's type
• Display path on a label somewhere

Create an ljv.version.pas under src to house all the version data.

There are still more memory leak issues present. Switching from test1.json to test2.json increases memory usage by 0.1MB.

• Add a formatted version like 133,133,001, or 133'133'001 for Integers
• For floats add 2 decimal places: 100,00.23 or 100'000.23

At the moment when ever the parser throws an exception a, not so useful, message is shown.

• Add more information from the exception message itself.
• Investigate how to deal with the lack of text when it encounters a BOM
• Investigate how to use LConvEncoding unit

Add drag-and-drop file capability.

• Add ActionList
• Add action actFileExit with the usual Linux and Windows exit shortcuts
• Add form key up to detect ESC and exit

At the moment the parser goes BOOM when it encounters either a BOM or a non UTF8 file

• Add form's Top, Left, Height, Width and WindowState to a config file
• Ponder adding the Pos from the PairSplitter

• Find a way to get the full path of a file, not just the relative path
• Every time a file is dropped compare that full path with the existing file list array
• Only add file if is unique

• Create a function that returns the spaced representation of the binary

• Check if all has been done correctly
• Check if any unit is needed
• Check if case sensitivity is an issue
• Check if the excluded components have any interference
• Check if there is any issue with resource strings

When the tab JSON is active there is no need to have the Status bar text for the Path.
Need to show it again when the Tree tab is selected