On Mar 11, 2010, at 8:52 PM, The Editor wrote: > You make a fair point that to understand a command you must understand > forms. But here's a couple reasons why we have the term: > > 1. I specifically wanted to avoid confusing them with markup > functions. So form commands is ok, but not form functions.
I don't see any possible confusion of markup and functions. Markup defines structure and look. Functions do processing, change things, return things... They neither do structure nor look. The output of functions is even formatted _with_ markup. How can you confuse them? > 2. The five items in the handbook are the five extensions of BoltWire. > BoltWire's architecture is essentially a lego box with five kinds of > lego's (another analogy). Commands are definitely one of the five. And > I need a name for commands.php--since functions.php is already taken. Lego? The hobbyhorse of engin... oops... farmers! > We could call it forms.php, but in my mind, html form stuff is a > subdivision of markups, not commands. The commands are conceptually > orders given to the zap forms processor, to be carried out on > submission. I think commands is great for that. Your point is very strong. I give way. forms.php is inferior to commands.php and form functions is bulky. Closed. > But like you said, I don't think at this point it would be worth > trying to make some change here. Commands have been a part of BoltWire > longer than BoltWire. In fact, it's really the heart of BoltWire. It > all started the first time I tried to get a functional savedata > command working in another wiki. Wow. how far we have come! Dan, you walk down the BoltWire memory lane pretty often lately. :D Those good ol' days... Markus > Cheers, > Dan > > > > On Wed, Mar 10, 2010 at 2:32 PM, Markus <[email protected]> wrote: >> I forgot the big "but". Well, it's huge and a personal, emotional, >> long standing issue of mine. >> >> I think "Commands" is the single most offender of all terms. Commands >> are part of the form processor. Its doc page reflects the problem: the >> first paragraph does not even tell you WHAT commands are. And it >> can't! Because to understand commands you must first understand forms. >> Commands are 2nd-level. Forms are top-level. >> >> I still have a hard time to tell myself that commands are just a >> special part of forms. It sounds so separate. As if it was something >> for its own while it's just that: a part of a form. Commands make me >> think of command line programs that are invoked by written commands at >> best and of military and authorities at worst. >> >> Calling forms with their name, "forms", would be awesome. Calling >> commands in them "form functions" would be crystal clear: >> >> function = do something >> >> form function = do something within a form >> >> command = please not >> >> Now, I feel better. Thanks for listening. > > -- > 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. > -- 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.
