76mm -> RE: TOAWxml Editor (6/22/2021 8:15:35 PM)
|
quote:
ORIGINAL: rhinobones Instead of using the “single” page xml format, would it be possible to load the flat file into an Excel like spreadsheet? Built in sorting and searches would solve the problems you’re having with the current format and mass changes would be easier. I'll take a look at this, but have several concerns: 1) If I only do the "flat" searches, I won't really have any problems with the current format, I think it would be relatively easy to display a flat list of a single layer in the hierarchy--I just don't think that it would be very useful; I could also easily add sorting. You can see how a "spreadsheet" style flat XML document would look like if you check out my "Equipment DB Viewer" (also in this subforum). It basically looks like a spreadsheet and acts like one to a certain extent (has sorting, but no replace function). I'm not really eager to try importing hierarchical XML (eg, Force, Formations, Units, Equipment) into a spreadsheets, which are inherently flat. I know that Excel allows for "nested" rows, but AFAIK those don't create truly hierarchical data and are purely a graphic thing. 2) I don't think that adding a replace feature (to allow for mass changes) would be much more difficult than a search feature, so I could probably add that as well. But if you want to make mass changes right now, it is super-easy to do so with XML files in Notepad++. quote:
ORIGINAL: rhinobones After editing you would probably need a macro to return the file to a suitable upload configuration. Frankly the main reason I'm hesitant to mess around with spreadsheets is that while I think it might be pretty easy to spit out a spreadsheet which was about 80% correct, dealing with all of the issues to get it to 100% could be a nightmare. Importing the data back into XML would probably be even worse--currently all data entry via TOAWxml undergoes error validation before being added to the XML file (so you can't add text where you need a number, can't add a number which is incorrect, etc.). Just importing everything from Excel to XML would bypass all of that validation, meaning that the resulting XML could be a huge, unworkable mess, especially since errors could be introduced both while exporting from, and importing to, XML. I'm not sure, but suspect that dealing with this would involve extensive, very tedious coding, which frankly, I am loath to do. I think you've mentioned spreadsheets a couple of times...what specifically are you wanting to do? I might be able to think of something equivalent but might work better with XML.
|
|
|
|