Category talk:Oblivion XML
I'm trying hard while writing this page to stick to what I know - which isn't much. This isn't supposed to be a tutorial on xml syntax anyway, but if anyone more knowledgeable should step in with a new introduction, I won't argue.
-- JRoush 20:19, 20 May 2009 (EDT)
- Unfortunately, I doubt anyone here knows more than you do on the subject. There are a few people who have been messing with this stuff, but I haven't seen any of em around here in a while.
- Dragoon Wraith TALK 17:40, 21 May 2009 (EDT)
- Thanks.JRoush 21:25, 22 May 2009 (EDT)
- I think I can help. I've been dealing with Oblivion's XML (both just the XML files and the OBSE XML functions) quite a bit lately. But I gotta warn you, I really suck at documenting. So, what kind of things do you need to know? Kyoma 02:59, 23 May 2009 (EDT)
About "include", where would that go? Under operators?Kyoma 06:05, 23 May 2009 (EDT)
- Thanks very much for your help, Kyoma. I wasn't sure where to put include - I was just going to drop it in the Menu Elements page with a special note. If you have a plan, don't hesitate. JRoush 12:15, 23 May 2009 (EDT)
Say would it be a good idea to change the Trait term to Attribute? With all the possible confusing on how Oblivion uses the trait keyword differently. Kyoma 06:20, 10 March 2011 (EST)
- Yes, I've been meaning to do that for some time. I haven't made any inroads on the xml stuff in quite a while, kyoma, so if you want to change any of these pages go right ahead. JRoush 15:16, 10 March 2011 (EST)
- Okiedokie! kyoma 13:40, 12 March 2011 (EST)
Nonsanity: EXCELLENT documentation! And I guess I should know since I designed "Oblivion XML", wrote the code for it, and made most of the base XML files. These are the docs I always wanted to do, but didn't. :) I was going to suggest using Trait instead of Attribute, since in XML "attributes" are like the "name", "src", and "trait" used here. But if Trait is confusing, go with what you like.
I DO want to point out that most of the examples with operator tags don't start with a <copy> but instead use the existing value of the... Attribute... as the initial value. I would not recommend this, as examples OR as normal practice. The problem is that there is no control over when the attribute will be recalculated. Originally, the initial value for every numeric tag was 0, but there were one or two special, controlled cases where re-using the old value made sense and was safe. (I think one example was using an OnlyIf operator on the previous value to help determine the new value.) But for the most part, operator chains should always start with a Copy or one of the few other tags that are self-contained, like Rand.
I just stumbled on this write up. I may not be back here to read responses unless poked. I welcome emails, though remember it's been years since I made all this... Nonsanity 15:14, 19 May 2011 (EDT)
- Hi! Interesting to see th creator of this, well, unique system. :) And, a bit late though, my thoughts:
- With regards to Trait vs Attribute, I think I mixed the two up in my post (not in my idea). Initially these docs referred to "name", "src" and "trait" as Traits and things like "user0", "x", "filename" were referred to as Property Objects. But alot of other documentation used "Traits" for the latter, leading to alot of confusion. Hence my suggestion to change "name, "src" and "trait" to Attribute since, as you said, is what they would be in normal XML syntax. From here on out I (in other docs) will refer to "user0", "x", "filename", etc. as Traits and to "name", "src" and "trait" as Attributes.
- On the subject of Operators, I'm busy writing some docs for how the engine handles and updates operators, in which I'll add a section on when not to use "copy". And other behaviour or cave-ats.kyoma 05:34, 10 February 2012 (EST)