Script in Metaplace?
Come to Cafe Eleutheria at 4:00 PM PDT on Wednesday 21st for a discussion of namespaces, naming standards, name recording, and other ways to avoid current and future problems with name collisions!
We've started seeing collisions in the chat command namespace, and while I don't want to speak for any other scripters, I notice I've started occasionally seeing collisions in the property-name and trigger-name namespaces too.
This is obviously a problem, and not just for scripters, because as large as Metaplace is these days, we can't testevery module against every other module, and that means the first the average Metaplace user is going to find out about the problem is when they install two unrelated, differently-authored modules, and all of a sudden their world is broken in some weird way they've no idea how to debug.
So, here's my notion. Rather than make the Metaplace folks come up with a technical solution after the fact - which is going to be damn tricky anyway, since some modules need to interact - I'm suggesting that we, the scripting community, get together and come up with some naming standards for voluntary compliance for our modules' private properties and triggers, such that we can be sure of not stepping on each others' code, and plans to record the public properties, triggers, chat commands, etc. we're using on the Wiki, as per the page Obo has started for chat commands, again, so we can be sure to avoid duplication or accidentally stepping on a trigger other modules are using.
In the meantime, please post your thoughts and ideas on this topic to the forums, at http://www.metaplace.com/forums/posts/view/3569969 .
