February 25, 2005
"Walter" <newshound@digitalmars.com> wrote in message news:cvo18q$1ftr$1@digitaldaemon.com...
>
> "Matthew" <admin@stlsoft.dot.dot.dot.dot.org> wrote in message news:cvnude$1cub$1@digitaldaemon.com...
>> Erm, you do realise nvx is a command line tool?
>
> Yes.
>
>> Seriously confused
>
> Sorry. I just went off on a tangent. Most of the post has nothing to
> do with
> nvx!

Gotcha

I liked the Kleenex concept. I'm going to use that somewhere/somehow. :-)


February 25, 2005
> But I still can't remember which is on or off, "O" or "|". I suppose it's fair, though, because now everyone is equally confused.

It's funny you mention that. Yesterday I got a new monitor and so last night I set it up and I had plugged stuff in and I stumbled around and turned everything on and ... nothing happened.  The room was pretty dark so I flipped a few switches again and tried again. no dice. So I thought shoot I have to start paying more attention. I opened up the (one page) manual and it said pretty much "the only thing you absolutely need make sure you do is turn on the monitor before you turn on the computer otherwise everything could be hosed". I thought I had done that but who knows so I got a flash light and looked around in the back and found the on/off switch (that I had originally toggled a few times by feel). It had that stupid O and | and I had no idea what was what. I didn't touch it and went and found another switch the the O and | that I knew was off to learn what setting is what. I went back to the monitor, turned it off, unplugged everything. Plugged it all back in and turned it all on in the right order and then finally realized there was an invisible little button on the front that I hadn't seen in the dark that looked like

  ---
 /   \
 | | |
 \ | /
   |

That I guess means "on/off". So I pressed that and it turned on and everything was working fine. sheesh.


February 25, 2005
In article <cvo1pn$1gee$1@digitaldaemon.com>, Paul Bonser says...
>I don't know about you, but I'm using Linux, and I use the command line every day. So what if it takes me a while to figure out how to write a script to wait for one process to die before starting another (some grepping of the output of ps and some sleeping), it's fun dagnabit! And plus, I doubt there are many GUI tools to do that...
>
>Also, I think it's probably none of our business the Loin training Walter's been doing...unless you mean lion training, it's not really appropriate for this list :P
>
>-- 
>
>-PIB
>
>--
>"C++ also supports the notion of *friends*: cooperative classes that are permitted to see each other's private parts." - Grady Booch

Paul: Darn, I hate it when I transpose letters! Thanks so much for the
correction, cause I did mean “Lion.” I’m surprise Walter didn’t nail me for that
one. <g>

-------------------------------------------------------------------
"Dare to reach for the Stars...Dare to Dream, Build, and Achieve!"
February 26, 2005
>I know people swear by their favorite GUI IDEs. I know they believe they are more productive with them, just as I believe I am more productive with the command line tools. Who knows, perhaps we're both right.
>

Most tools need both a command-line for power users and a GUI for quick and dirty stuff.

I try to use both.


February 28, 2005
Marco wrote:
>>I know people swear by their favorite GUI IDEs. I know they believe they are
>>more productive with them, just as I believe I am more productive with the
>>command line tools. Who knows, perhaps we're both right.
>>
> 
> 
> Most tools need both a command-line for power users and a GUI for quick and
> dirty stuff.  
> 
> I try to use both.
> 
> 

Exactly why I think all GUIs should have a console built in :)

-- 
-PIB

--
"C++ also supports the notion of *friends*: cooperative classes that
are permitted to see each other's private parts." - Grady Booch
February 28, 2005
"Ben Hinkle" <bhinkle@mathworks.com> wrote:

[...]
> then finally realized there was an invisible little button on the front that I hadn't seen in the dark
[...]

"Every time you try to operate on of these weird black controls that are labelled in black on a black background, a little black light lights up black to let you know you've done it."

(Douglas Adams, The Restaurant At The End Of The Universe)

-manfred
February 28, 2005
In article <cvmsiv$bel$1@digitaldaemon.com>, Walter says...
>
[...]
>
>But I still can't remember which is on or off, "O" or "|". I suppose it's fair, though, because now everyone is equally confused.

So you agree it should be "false " and "true"? :-)

Ciao


February 28, 2005
Roberto Mariottini wrote:

>>But I still can't remember which is on or off, "O" or "|". I suppose it's
>>fair, though, because now everyone is equally confused.
> 
> So you agree it should be "false " and "true"? :-)

Yeah, I always turn false the TV before going to bed...
And now I must remember to go turn the coffee pot true.
:-P

I still think that bit { off, on }, bool { false, true }
makes more sense? But as long as I can still make-believe
that they are separate, the current D "bool" alias is OK.

--anders

PS.
Other famous engineering-nerd-meets-the-real-world clashes I have:
- Windows operating systems > Start Menu > *Shut Down* menu item
- Macintosh operating systems > Disk icon > Trashcan to *unmount*
- Sony Ericsson phone > "No" button > press and hold to turn *on*

Here's a nice gallery : http://www.baddesigns.com/examples.html
February 28, 2005
"Roberto Mariottini" <Roberto_member@pathlink.com> wrote in message news:cvul5o$250v$1@digitaldaemon.com...
> In article <cvmsiv$bel$1@digitaldaemon.com>, Walter says...
> >
> [...]
> >
> >But I still can't remember which is on or off, "O" or "|". I suppose it's fair, though, because now everyone is equally confused.
>
> So you agree it should be "false " and "true"? :-)

LOL. I checked, and "O" means "on" and "|" means "off". So if you think of it as looking like zero or one, it's backwards. What moron ever came up with that?


February 28, 2005
"Anders F Björklund" <afb@algonet.se> wrote in message news:cvumcu$2658$1@digitaldaemon.com...
> PS.
> Other famous engineering-nerd-meets-the-real-world clashes I have:
> - Windows operating systems > Start Menu > *Shut Down* menu item
> - Macintosh operating systems > Disk icon > Trashcan to *unmount*
> - Sony Ericsson phone > "No" button > press and hold to turn *on*
>
> Here's a nice gallery : http://www.baddesigns.com/examples.html

On my phone, the "hang up" button is what turns the phone on. ???

Airplanes have always had struggles with this sort of thing. There's a case where a military aircraft was coming in for a landing, and an emergency arose where it needed to abort the landing, go to full power, and go around. The pilot yelled "takeoff power!". The engineer obligingly cut power to the engines. The airplane crashed.

As a result of that, the proper phrase for full power was changed to "meeto power".

The cockpit designer for the 757 told me once that all the controls seem obvious in a cockpit. But, he said, everything that is now "obvious" was paid for with a crash and somebody's blood. Obvious designs really aren't obvious except in hindsight. Check out the book "The Design of Everyday Things" which every engineer should read.