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. Markus On Mar 10, 8:09 pm, Markus <[email protected]> wrote: > Glad you like it. > > Although I don't have difficulties with the nomenclature, I am aware > of the fact that analogies can make things either more difficult or > easier. > > I cannot remember how many times I explained to people that their > Desktop is just a folder that is displayed in a different way. If it > wasn't the Desktop but just a folder that is displayed in a different > way, everyone who understood what a folder is wouldn't be scared > anymore about that magic thing behind their windows. On the other hand > "folder" itself is an analogy but one which actually works. > > Back to BoltWire. Yes, a farm analogy is a bit far-streched for a web > development engine. I know it is cool to talk about farms and fields > though you might get hungry or sick of your city life. Having to > mentally transform the beautiful landscape, cows and colorful crops to > some file system folders while you must understand what the actual > analogy is... might or might not make it easier. > > I probably couldn't even tell you _without_ thinking what the > analogies are. I say "field" but in my head is just a folder. I say > "farm" but in my head is just a folder. Do I think of stamps? > Certainly not. Just past versions of my pages. And so on. > > I am not saying that the nomenclature makes it more difficult. Nobody > knows that. As we don't, there is a high advantage to keeping > everything as it is: we know the nomenclature, new users will learn it > probably as fast as without it and we have a zillion documents where > these terms are used. Also I had a good laugh when first reading that > someone was really that funny to use a farm analogy for a CMS...! :) > > Last but not least, it makes BoltWire special and eco-friendly. > > Moo, > Markus > > On Mar 10, 6:51 pm, riccardo <[email protected]> wrote: > > > > > On Wed, Mar 10, 2010 at 05:02:24AM -0800, Markus wrote: > > > I agree that more FAQs would be great. What do you think about this > > > quick, unfinished map: > > > >http://www.markusweimar.de/test/BoltWire.html > > > Oh, that is useful. I still find the the nomenclature non-obvious. As a > > developer of buildings, I must simply remember that fields are just sites... > > > But a helpful diagram. Thanks > > > richard -- 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.
