Address tracker v5

Tested on Windows 11 Version 24H2 (OS Build 26100.2454) with:
- Google Chrome Version 131.0.6778.109 (Official Build) (64-bit)
- Firefox 133.0 (64-bit)
- Microsoft Edge Version 131.0.2903.86 (Official build) (64-bit)

I'm accepting this on the base of "it's an improvement over the already accepted version", but this tool needs some serious work to be really considerable "usable".
If it wasn't already accepted in the section, I would've rejected it because of some of the issues I'm going to outline in this comment, in the hope that they'll be fixed.

Issue 1:
- the tool's UI/UX is bad, the white text over pitch black background is jarring to the eyes and the wall of texts are not easy to understand.
Overall I would recommend a redesign/reorganization of the screen space to avoid the "wall of text" effect and to improve the text boxes and simplify the usage.
Speaking of the text boxes, they are *not* the best way to do what you want to do, especially requiring tabs and not working with spaces, the format is very unintuitive and hard to use.
A revamp of the UI/UX is therefore very recommended.
Issue 2:
- a very basic use case doesn't work because of the way you assign free ram, let me explain with an example:
in Assigned.html, if you put the following ASM resources:

and the following empty RAMs

I would personally expect for $7e0070 to be assigned to !asdf and $7e0060 to !asdf2.
Instead what happens due to the greedy first-fit algorithm used to assign the free ram is that !asdf gets assigned to $7e0060, and thus !asdf2 fails to assign because the remaining freeram is not big enough.
This is a pretty big issue because it prevents the tool from working in this basic use-case. A possible fix is to sort the resource freerams before assigning, to prevent this issue.

Just to warn anyone using range notation, make sure you replace the hyphen with a tilde (~) to denote an ending address instead of a hyphen due to negative address support. This tool can be used beyond SMW and the SNES for misc ROM hacking or pretty much anything related to memory storage.

HammerBrother, I think the current organization can be improved. I didn't reject it but I think new people will get more confused when visiting the tool initially, specially the ones not used with programming languages.

The organization can be better. If the documentation is only on "HowToUse.html", consider removing the other files like "README.md" and "Old_Stuff_JustInCase" and keep them on your GitHub only.

When doing a release, it's mostly recommended to come with a binary (Addresser2.html), a readme (HowToUse.html), additional/dependency files (SMW_UsedAddress.txt) and a change log. Additional and/or similar files may make people get confused. I think if you are afraid that people may not like the current layout of Addresser2.html, you should consider offering an alternate release via GitHub until you make the remaining improvements over the new layout. That way, the user experience will be better, in my opinion.

This is one of the most complex javascript I written so far, with the auto-freeram tool. It had 5 checks to make sure the lines in the text are correct, have valid number of bytes, as well as utilizing the array.splice feature when a suitable RAM is found and the freeram gets “chopped” off.

Another last minute updates:
07-04-2021
potentially long line that could stretch the table for most users: Show/Hide

Code

2021-07-04 Escape tag option and warn the user about improper HTML tag setup for description
	-I discovered a major issue and have fixed them regarding
	 HTML tags in the description:
	--Improper tag setup like ending the table tags without
	  starting them beforehand can break the outer table.
	--Added a setting that will escape HTML tags and the
	  escape character itself (the ampersand), when enabled,
	  will disable the HTML effects, which prevents breaking
	  the table.

07-09-2021
-Fixed the duplicate detecting things that should be the same as different if these scenarios play out:
--Entry with blank description but whether or not have a tab character after the size/end_address.
--Leading zeroes in address, and size/end address.

I really don't know if this is considered memory management, since this is intended to find free bytes of memory when installing ASM resources.

All modified changes are OK.

I've added version number to the submission name, but if you prefer it versioned in another manner, let me know.

No, it's an update.
If it shows "obsoletes" in the waiting section, then it means it's an update.

is this a duplicate submission ?

Fix an issue where if a tab is inserted and results the format being valid, the function to display the address won't update.

Example:

If I add a tab character between 1 and testing, results in this:

This is now correct, however, it will not update the information presented below.

Also, this is my very first tool.

Tested in Firefox, Chrome, Edge. It doesn't work in IE because of BigInt usage but don't consider that a problem. I updated the tool so you can enter TABs just by typing them into the box, otherwise accepted as-is

Working on a tutorial/ASM library?

I may fork this one and put this in a website for easy use.