Hello all.
In preparation for a game I'm making that has quite a large dialogue/visual novel portion to it, I've decided that I needed a way for non-programmers(writers, artist and authors) to manipulate screen elements and create scenes and dialogue without having to learn a high-level coding language like C++ or Java. This has led me to begin designing a scripting language to fit the needs of those authors and writers.
However, roaming around on the internet, I've heard of XML and how it is said to shorten the time spent making text parsers and custom scripting languages.I am interested in adapting XML for my project, but there is an important question that I have: Since my goal is to allow a non-programmer with no prior knowledge of programming or scripting languages to write his or her dialogue and scenes in a text file, would XML be too complicated or difficult for them to work with? How complicated would the syntax the author has to learn be?
If anyone with experience with using XML in C++ could answer these, it would be greatly appeciated. Thanks.
Is XML non-programmer friendly?
You shouldn't ever let non-technical people edit XML files manually, that's asking for trouble.
What you probably should do is use the fact that XML is such a well-defined and widely adopted standard to your advantage. There are tons of libraries which can easily read and write XML files, so it might be a good idea to invest a small amount time in writing tools for these people that give them an easy interface to work with, and which write out the content they make to XML files.
This gives you nice intermediate files which are still more or less readable and which can also be easily read back into your game.
What you probably should do is use the fact that XML is such a well-defined and widely adopted standard to your advantage. There are tons of libraries which can easily read and write XML files, so it might be a good idea to invest a small amount time in writing tools for these people that give them an easy interface to work with, and which write out the content they make to XML files.
This gives you nice intermediate files which are still more or less readable and which can also be easily read back into your game.
Author
Thank you, that was just the type of answer I was looking for. I'll give your suggestion a try, as XML was always on my radar.
The website you offered seems to be empty, though.
The website you offered seems to be empty, though.
The website you offered seems to be empty, though.
That link is a link to my homepage which I placed in my signature (website is offline atm), it wasn't part of my reply
Radikalizm is correct; if you use XML, you should try to ensure no one has to write it manually, including yourself. It isn't a very good fit for domain specific languages.
In this case, you want to expose a domain specific language to users, so you'll have to parse that language anyway. When you have the data in hand after parsing, why would you want to convert it to XML? That seems superfluous.
Some pros/cons/alternatives of XML to represent stuff:
http://www.codinghor...racket-tax.html
In this case, you want to expose a domain specific language to users, so you'll have to parse that language anyway. When you have the data in hand after parsing, why would you want to convert it to XML? That seems superfluous.
Some pros/cons/alternatives of XML to represent stuff:
http://www.codinghor...racket-tax.html
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement