EDB organizer

**Pat89** · January 03, 2011, 02:41 PM

Hi all,

Personally I hate it if the syntax of a file is not as it should be, so I made a simple tool which fixes this for the EDB:

Before:
Attachment 131074

After:
Attachment 131075

Its use is rather simple:

Select the EDB you want to fix.
The tool will create a backup called "export_descr_buildings_BACKUP.txt".
The tool will fix the selected EDB in a couple of seconds.

DOWNLOAD v1.0

**Aradan** · January 03, 2011, 04:19 PM

Is there something that it does different compared to the 'prettified' version of the EDB HoH's EDB validator can generate? I don't mean to rain on your parade, mind you, just curious.

**Pat89** · January 03, 2011, 04:39 PM

I guess not

(didn't know it could do that

)

**HouseOfHam** · January 04, 2011, 03:49 PM

The 'Generate prettified EDB' button in the EDB validator was something I added mostly for my own convenience and as a debugging tool, to make sure everything got parsed correctly. Because of that, there are some limitations to what it generates. Namely, it strips out all comments and plugins definitions. So, if keeping those is important to you, you'd want to use Pat's tool instead.

Plus, the 'Generate prettified EDB' is only available if EDB doesn't contain any errors to start with. If you're starting with a really messy EDB with a lot of errors, you wouldn't be able to access it.

**Aradan** · January 04, 2011, 04:19 PM

First point is valid, having all the comments removed would be annoying. As for the second point, well, if you have an error-ridden EDB, making it pretty is the least of your concerns.

Any chance you two gents could 'merge' and provide a prettification function in EDB Validator that will preserve all the comments (align them with the line directly below them)?

**Pat89** · January 04, 2011, 04:28 PM

Unfortunately they're in a different language... (HoH's tool is in Java, mine in AutoIt3)

But nothing prevents you from using this one prior to the validator or vice versa... The only EDB error this tool crashes on is if you have more closing "}" brackets than opening "{" brackets (telling you the line of the floating "}").