The dumper/inserter will use the established table standard, so they go together. You say you haven't had any trouble working with 'tables' in the past. What tables? The one you use with Windhex? The one you use with Thingy? The one with Hexposure? The one with Translhextion? The one you use with your own custom utility? The one with Atlas? That's the kind of thing I'd like to see go away moving forward with utilities. We can have some compatibility between utilities, set an abstraction layer for tables (more interesting for utility creators), and rely on standard feature set. Oh well. Our community likes to stay in the stone ages. Why should this be any different? They like their stones.
So, we've declared nothing here is of use to you? Fantastic! Wait... How is this contributing to the thread again?
Boy, I'll come back in 10 years and try to push you guys forward again. Timing seems to be way off on this one.
I've used just about every hex editor there is for romhacking, including Thingy, Thing32, Goldfinger, Windhex, Hexposure, and I'm sure I could dig up some others. And I've used the same type of table for each one, and never had an issue. I've used them to dump romjuice scripts (though, I admit I make a separate table with the "\r" and "\n" stuff) and insert Atlas ones with no problem.
If anything, I think perhaps there should be a standard for the basic <End> and <Linebreak> control codes. Some sorta standard value so that you don't have to set up the table to dump them properly.
But I'm more interested in the dumper/inserter because I don't really like romjuice, Cartographer is still unfinished (and I couldn't get it to dump ActRaiser 2, for some reason), and Atlas has always given me trouble. I'd like something a little more streamlined and simple to work with. Oh, and a GUI. I don't like stones. =P