Started by milon, July 15, 2016, 02:55:38 PM
Quote from: milon on March 03, 2017, 05:23:45 AMSorry for the belated reply - I haven't had time to dig into the XML to see what you're referring to. If you're asking for specific documentation of what it does, that would defeat the purpose of it being an Auto Doc. If you're asking for more detailed analysis/use of compProperties, could you elaborate a bit on what you're looking for?
Quote from: milon on March 17, 2017, 03:02:45 PMAh, okay. Thanks for passing that along. I haven't been on Discord yet, and probably won't get into that, tbh. I'm willing to add more parsing/tracking, but I need a little clarity yet. (Sorry if I'm being thick-skulled here; I'm just still not getting it.)Here's what I understand: According to the A16 XML, there's only 3 different attributes that show up in Core as Class="???Properties_..." and they are ALWAYS applied to a <comps><li ... > tag. They are:CompProperties_...HediffCompProperties_...StorytellerCompProperties_...(Note: There is no BuildingProperties or StuffProperties in the A16 XML. If you're referring to something that isn't public knowledge, please PM me rather than posting it publicly.) The point of this isn't manual documentation, but I don't think that's what you're after. These attributes are all grouped under comps<li> and they shouldn't be that hard to find. Their names give really good clues as to what they do. So what exactly are you asking me to track? Again, I'm willing to make it happen, I'm just not sure what I'm being asked for.
Quote from: milon on March 22, 2017, 01:39:27 PMOkay, I made a test build of the above. It now parses separately any "special" tag (currently just <li> and <defName>) with an attribute containing 'Properties_' . That seems to catch all of the various CompProperties without grabbing anything else.Here's the test build (not updated on the main page): https://www.dropbox.com/s/q896td291evktld/CoreXML%20A16%20Test.html?dl=0Let me know if that's what you're looking for, and if it's useful. I don't want to get lost in the feature-creep end of things either. Oh, and how's the overall formatting & usability? Anyone have ideas how to improve the layout? Having two pseudo-columns via Float in a >1MB HTML file isn't exactly ideal, but it's the best I can think of to allow independent vertical scrolling.
Quote from: milon on November 20, 2017, 07:09:22 PMUpdated to A18. I haven't *touched* A18 yet, beyond downloading and running the Auto-Doc on it. I'm still "on vacation" because IRL is insane in milon-land. Please PM me if there's any weirdness or anything else I should be alerted to.Enjoy!
Quote from: milon on November 20, 2017, 07:09:22 PMEnjoy!
Quote from: milon on November 20, 2017, 07:09:22 PMUpdated to A18.