JsonTools v5.5. is live!

Mark Olson

I’d also like to throw out some more ideas that I’ve been mulling over, and hopefully get people’s thoughts on what features I should work on next.

Improve JSON from files and APIs form, add ability to replace JSON in files with RemesPath queries
Add ability to parse ini or TOML files
Improve JSON schema support, including adding ability to find multiple schema violations in a file
Add pretty-printing option that preserves comments
Any other ideas!

Mark Olson

Next release will have support for comment-preserving pretty-printing and compressing!

Mark Olson

Release 5.8 is live, with support for INI files, including reformatting them querying/viewing/editing them with the tree view.

Thoughts?

Vitalii Dovgan

@Mark-Olson
Interesting functionality, thank you!
Maybe it’s just me - but 4 toolbar buttons look too much to me. Let’s imagine we have 10 plugins with 4 toolbar buttons added by each of them - as the result, the toolbar will explode! :) So I’d propose to make the toolbar buttons configurable - e.g. by introducing the corresponding check-boxes in the settings - to allow user to decide which buttons should be visible and which not. (Surely, Notepad++ will need to be restarted to apply the selected number of buttons).

Mark Olson

@Vitalii-Dovgan
Good idea! Starting in the next release of JsonTools, you can customize which icons are shown and the order they appear in.

Because I don’t want to have a separate setting for each icon, what I’ve done is added a setting that uses a string where each char can represent an icon, and the position of the char in the string represents its left-to-right position on the toolbar.

Currently the character-icon mappings (case-insensitive) are ('t' = tree view, 'c' = compress, 'p' = pretty-print, 'o' = path to current position)

So a for this setting would mean no icons (b/c no char is mapped to an icon), tcpo means (tree, compress, pretty-print, path) in that order, and ct means (compress, tree) in that order.

Mark Olson

So I thought to myself, “JsonTools has a perfectly good tree viewer. Why shouldn’t I be able to use it for non-JSON files?”

I haven’t released v6.0 yet, but it’s a big one.

This in the documentation, but I should emphasize that JsonTools uses .NET regular expressions, not the Boost library that Notepad++ uses.

Mark Olson

JsonTools v6.1.1 is out, and the next version of the plugin list should list it.
It includes fixes for several bugs, performance improvements for the error form, improvements to regular expressions, and even Python-style F-strings!

Mark Olson

JsonTools v7 is out. It’s not on the plugin list, because I’m hoping for some guinea pigs to check it out first.

Rather than list all the new features, see how many you can spot in the image below!

Mark Olson

JsonTools v7.1.0 is live! Hopefully it will be in the version of the Plugin List that ships with Notepad++ 8.5.5. You should definitely upgrade to this version, especially if you have Notepad++ 8.6.3 or newer.

MarkusBodensee

@Mark-Olson said in JsonTools v5.5. is live!:

JsonTools v7.1.0 is live! Hopefully it will be in the version of the Plugin List that ships with Notepad++ 8.5.5. You should definitely upgrade to this version, especially if you have Notepad++ 8.6.3 or newer.

I think you mean the Plugin List that ships with Notepad++ 8.6.5

Mark Olson

JsonTools v8.0 is now live, and the most notable change is that it can now be translated to other languages.

I would be particularly interested in getting feedback from other C# plugin developers, particularly @Bas-de-Reuver, on the API I devised for translating forms using JSON with comments files and a somewhat hacky algorithm for translating WinForm controls while avoiding collisions. I am currently planning to add this code (or possibly a variant that uses XML instead of JSON with comments) to my NppCSharpPluginPack plugin template.

Mark Olson

JsonTools v8.2 is now downloadable via the Plugins Admin for Notepad++ 8.7.2. This version includes a variety of enhancements and bugfixes, but the main reason I wanted to post this here is that it attempts to fix a problem introduced in JsonTools v8.1, wherein decimal numbers had unnecessarily long representations (for example, 11.11 was reformatted as 11.109999999999999), and I’ve gotten a report that this issue is still not fixed in JsonTools v8.2, even though it is fixed on both of the two machines that I tested it on.

So here’s my request: please upvote this comment if and only if you notice that JsonTools v8.2 reformats 11.11 as 11.109999999999999. Don’t upvote this comment for any other reason; that way, I’ll know that this is still an issue if I get upvotes.

Mark Olson

I’ve just commited the unreleased JsonTools v8.2.0.3 that hopefully fixes the issue described in my previous comment. Did my commit fix it? I have no idea, 🤷!

Same deal as in my previous comment: please upvote this comment if and only if you notice that JsonTools v8.2.0.3 reformats 11.11 as 11.109999999999999. Don’t upvote this comment for any other reason; that way, I’ll know that this is still an issue if I get upvotes.