On Tue, Oct 6, 2009 at 6:02 AM, Hans <[email protected]> wrote: > > 2009/10/5 The Editor <[email protected]>: >> >> What is happening here Hans, is that "source" is a recognized command >> in BoltWire. Kind of a reserved name in BoltWire--that works >> specially. > > Just my luck then! > But it seems crazy to allow 'special' words act as commands when you > create a data field with that name. It is just a name fora data > variable and should not act crazy, I think. > There should be no special exceptions.
How is BoltWire supposed to know you are not calling the command, and intend to use it as a data variable instead? It is the same with any other command: login, create, target, etc. They all have special behaviors. > Generally name space is important, and BW is a bit poor on that score, > for instance in using page names like 'top', 'header' etc. as top > level names, restricting a user in their name choice. Agreed. Namespace is important, and BW has generally tended to go with simpler syntax at the expense of namespace. Same with markups. A trade-off. My assumption is that people writing forms should be familiar with recognized commands. But given there are so many, that may be problematic. I'm open to some kind of flag to indicate commands--perhaps [command source value...] as opposed to [session source value...] But commands are often put in regular input fields like text or box so this would be onerous in those situations to have to do field replacements for everything. And once again, it would wreak havoc on probably every existing form out there. As for zones, we've discussed it a bit before. But again, it's a tradeoff. I suspect it is generally easier for a user to know where to put things: forum.header vs zone.forum.header. Though to be honest, it was just inherited from PmWiki, where forum.header has special meaning. Not zone.forum.header. My biggest resistance is that changing it now would be equally disruptive to existing sites. If I were to redo things, I might go with zone.top and zone.forum.top, etc. It's an easy enough change to do. In fact, I think you can customize this behavior by using the myBOLTgetlink hook. Define the function exactly as BOLTgetlink, except add a line to the start that says something like if ($start != 'code') $start = 'zone'; or perhaps better if($start == '') $start = 'zone'; (not tested) That automatically puts a zone in the front of all your zones. Not tested, but should work. We could even perhaps make this a site config option in the core. You are the second person at least to suggest this. > What other special command names are there apart from 'source'? > Why is 'source' a special command? It is not special in any way, just one of the normal commands BoltWire recognizes. See the list here: http://www.boltwire.com/index.php?p=docs.handbook.commands Then you have to add any commands added by plugins. Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
