Timeline for Generic rule parser for RPG board game rules - how to do it?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 27, 2012 at 17:01 | vote | accept | floriank | ||
| Oct 24, 2012 at 1:16 | comment | added | floriank | It would be easier to save the generated form data serialized and run the parser on that in the language the app is using instead of using another language. But with lua I could - in theory - set vars to lua, eval that script with my set vars and type cast the result, it might be safe this way. | |
| Oct 23, 2012 at 21:04 | comment | added | TMN | @burzum: What about having your interface generate the lua scripts? | |
| Oct 23, 2012 at 17:26 | comment | added | floriank | After reading this I think I could simply eval lua scripts for that. The downside here would be that a user has to be capable of writing lua scripts. My personal goal is to write an interface that can be used without programming knowledge, like the rule builder in magento (ecommerce app). Because I want people to be able to add their own rules. I'm not implementing anything commercial, just a tool to let me and my friends enter the rules of RPG system we play on an irregular base and getting back to the rules and to apply them is a pain after some time... | |
| Oct 22, 2012 at 17:58 | comment | added | Jimmy Hoffa | I guess I should say it is the right approach to this sort of problem, but that's predicated on the person doing the implementation being someone with sufficient skill. For learning, DSL's are great for juniors, but for actual releasable product I would never want to see anyone below senior level writing a DSL, and for a junior a DSL solveable problem should be solved in a different way. | |
| Oct 22, 2012 at 17:03 | comment | added | Jon Purdy | @JimmyHoffa: Fair enough. It’s just in my nature to reach for language-based solutions, especially for games. I probably underestimate the difficulty of making something small and functional because I’ve done it many times. Still, it seems like an appropriate recommendation in this case. | |
| Oct 22, 2012 at 16:39 | comment | added | Jimmy Hoffa | Not a bad approach but I'm consistently skeptical of DSL's, they're a lot of work to get right (especially if you're talking about a true DSL with custom syntax and all, as opposed to just some fluent API which people have started calling "DSL"s), so you better be sure you're going to use the heck out of it, if you are then it's worth it. Often times I think people want to attempt a DSL where they're only going to use it for a small rules engine. Here's my rule of thumb: If the DSL implementation + usage is less code than no DSL, go for it, I don't think that would be so in this case. | |
| Oct 22, 2012 at 16:28 | history | answered | Jon Purdy | CC BY-SA 3.0 |