Reply to thread

Message: <blockquote data-quote="Firzair" data-source="post: 2139943" data-attributes="member: 1334">Yeah that's about what I figured a universally useable chargen need to be.What's a bit of a problem with this approach is all the XML-coding to be done (I don't like XML).But seeing what you've done there I think perhaps I should learn C++... seems good at building javascript-enabled objects.The distinction between data and code is good, as long as the code doesn't define the data. My first approach in my program was to code the whole rulesets in the objects data. So I got to have the rules for gaining new feats in the rules for the character level-data. While this could be easily changed using the object administration GUI it's not easy to just change this rule by a modification rule. So I will just put the rules that define data directly into the data. What I want to know is what size of a footprint (memory size) your program would need. Does it parse all the XML files and do all objects always exist in memory? Those XML-files can get realy big, how fast is XML-parsing? While I see the XML as a somewhat unified export format I wonder if it's useable for an application... GreetingsFirzair</blockquote>