Me too.avatarbr wrote:I need this![]()
That's the reason why i'm working on this. But it works now different since i gave you the last peek. It takes the validation stuff from the documentation now. You have to declare a human readable syntax-patterns for each command and each variation of it, which is translated into regex patterns to validate and extract data from a command. As long this isn't done, the tool is useless, because every missing or wrong syntax-value is detected as error.
This may sound inconvenient, but it enables the possibility to change validation behavior on runtime, without a compiler.
avatarbr wrote:I was thinking in create a very simple TeaseAI Guide to help people who want to create simple scripts or just colaborate with some vocabulary/response files. Like just something explaining what is a Module and what need to have there, how to put a vocabulary file, etc.
If i could get my hands on something like that, i would implement it in the documentation. I'll add the Help corner to the documentation too, but it's a little to unstructured and wordy. I haven't read it till the end myself... I always stop reading when i get bored.
I'm more the kinda guy who wants a quick overview and when i need further information's about something, i want this information and not all information's, without any possibility to filter. Probably you'll laugh, considering the fact i've rewritten thousands of lines in the base code, but it scared the crap outta me... All this compact information... I read one chapter and forget about the last, while understanding only half of it, at the time i read it.
And maybe this is the reason why there is no content...
I'm open to suggestions.malaru wrote: Maybe it would be nice to have some kind of overview... but I honestly don't know how to get that in a way, that makes it convenient to use.
Things i could imagine:
- a subforum, where develpers are mods. -> this way we could update content of such posts/threads without asking mods. And it's a bit akward to do ask for something like that, when the post creator is unavailable. Everyone creating such posts or threads has to keep in mind, that it's unspoken open for editing.
- a Github Wiki -> Havent used it, but i think it's the technically easiest solution.
The first solution leaves relationship between tease-AI and milovana untouched (or tightens it even more, since information is as up-to-date as possible) while the 2nd one weakens it heavily.
That's the reason, why my personal favorite is the first solution. But for this the admins have to agree with it.



