If you can't come up with even part of a name for it after you wrote most of it, then I can't come up with a name for it based on a vague or at least imprecise description.Valid criticism. :-)
I wrote it for another purpose then I think people might use it for. It's a solution looking for a problem.
I added a part of a definition of a object at the top.
Is that enough to understand?
Update:
If I put it like this:
I wrote above "think of a backend to an XML editor with an API so you can implement a data model" A backend to a smart XML editor, might be a good definition.
And it is hard to describe! I played the game 15+ years ago and it took a while to understand how it could be modeled without all the exceptions in the the rules making it really ugly code.
I am proud, it was a hard problem that imho resulted in quite a neat package of functionality.
There must be similar things, but I've never seen them. I am trying to describe something new. (-: And my verbal talents suck. :-)
In reply to Re^2: What should I name my module?
by BerntB
in thread What should I name my module?
by BerntB
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |