You are not logged in. Login Now
 0-17   17-41   42-66   67-79       
 
Author Message
25 new of 79 responses total.
mary
response 17 of 79: Mark Unseen   Jan 27 11:04 UTC 1999

Re: #15  How big of project would it be to totally rewrite
newuser and get it into the Grex domain?
remmers
response 18 of 79: Mark Unseen   Jan 27 11:24 UTC 1999

Re resp:15 - My thought was that if there was a "password hint"
field in which a user could fill in unique information for
verification purposes, the address and phone number wouldn't
be as necessary.
steve
response 19 of 79: Mark Unseen   Jan 27 18:17 UTC 1999

   The source is available.  Its in AFS space, and with the mit bridge
between afs and the web I think anyone can get it.  The real issue is
what to do with newuser, not access to it.
mdw
response 20 of 79: Mark Unseen   Jan 28 03:52 UTC 1999

The problem with "stripping" newuser down is that's not really a good
idea.  When the "helpful" person is there, telling the new person
everything they have to do, they stop thinking, and they stop
remembering.  Instead, they type in everything they're told, and that's
that.  The problems start the *next* time they log in.  They don't know
how to erase input, because their mind was in neutral last time.  They
don't remember their interrupt key.  In fact, they can't even remember
what an interrupt key does, because they didn't have to think.
rtg
response 21 of 79: Mark Unseen   Jan 28 05:52 UTC 1999

I see your point.  That's why I refuse to sit at the keyboard when I'm
helping new people sign up.  I know it's a blank the first time they log
in without me sitting by them.
  However, the reason I was sitting by them in the first place is that
they were too intimidated by the computer to even attempt it by
themselves.  I'd like to see something that gets them in quickly, so that
they can see a quick benefit, and yet make the help and advanced features
available easily as they find need for them.
  Could newuser change tty modes on the fly?  Would it be possible to
identify the terminal type early, and then switch to a full-screen mode
for the input, and be able to hyperlink to the explanation/help text if
necessary?  Ideally, the newuser program would be bare-bones, and then
once the userid, password, and terminal type are determined, link to the
change program directly, so that the user gets some experience with the
utility they will eventually return to.
mic
response 22 of 79: Mark Unseen   Feb 4 03:10 UTC 1999

If you decide to overhaul newuser, I'd be happy to program it if you so wish.
remmers
response 23 of 79: Mark Unseen   Feb 8 14:58 UTC 1999

It's been a while since I've looked at newuser, but if memory serves, 
what's at issue here -- the questions newuser asks -- is controlled 
to a large extent by template files rather than being hard-coded. So I 
doubt that major overhaul of the code would be necessary.

There seems to be concensus that the "technical" questions that newuser 
asks -- setting special keys, terminal type, login shell, etc. -- 
should be simplified, with the user being given the choice of accepting 
standard defaults.

There's mixed opinion on the other stuff that newuser asks -- address, 
phone number, etc. I favor simplifying that significantly too, though 
apparently not everyone agrees.
pfv
response 24 of 79: Mark Unseen   Feb 8 18:20 UTC 1999

        As far a user parameters, why not try somthing akin to:

        Please Select one of the following Configurations:

        1) For Those familiar with DOS (simple list..);
        2) For Those familiar with Windows (simple list..);
        3) For Those familiar with Linux (simple list..);

        Your Selection (you can alter all this later):
rcurl
response 25 of 79: Mark Unseen   Feb 8 18:54 UTC 1999

Hmmmmff! (signed: Mac OS user)
pfv
response 26 of 79: Mark Unseen   Feb 8 19:12 UTC 1999

oops, excuse my lack of memory! ;-)
dang
response 27 of 79: Mark Unseen   Feb 8 20:45 UTC 1999

How about:
        1) Those familiar with DOS
        2) Those familiar with windowed OSs (Windows, MacOS, etc.)
        3) Those familiar with UNIX (Linux, FreeBSD, Solaris, etc.)

Does that make you happier, Rane?  For these purposes, there's no 
functional difference between Windows and MacOS. (How's that for an 
inflamitory statement? :)
remmers
response 28 of 79: Mark Unseen   Feb 8 21:21 UTC 1999

Dunno about these choices. We don't offer any interfaces that are 
either DOS-like or windows-like. And practically everybody is familiar 
with windowed OS's these days.
rcurl
response 29 of 79: Mark Unseen   Feb 8 21:38 UTC 1999

Isn't the fundamental distinction for #27 GUI and CLI? But I'm not sure
what the relevance of this is to Grex as it stands. Grex is essentially
a CLI, with moves away from that with menu and, definitely, with Backtalk.
pfv
response 30 of 79: Mark Unseen   Feb 9 05:53 UTC 1999

        Don't expect any of them to understand GUI *OR* CLI..

        I'd stick to dos-like, doze-like, mac-lick, & linux-like.

        BTW, jp2 was crowing about his latest shell - which uses ncurses.
        Such a thing might behoove a GUI-exclusive clientel.
mdw
response 31 of 79: Mark Unseen   Feb 9 12:13 UTC 1999

I remember *very* clearly when Dave Parks took out the logic in newuser
that made people type in their interrupt character.  It was not pretty.
It's quite amazing, really, that some of the world's most common
terminal programs do such screwy things with ^C - but they do.  Making
something simplier does not always make it easier to learn.
pfv
response 32 of 79: Mark Unseen   Feb 9 15:04 UTC 1999

        Yeppers...

        Even nxterm, aterm and eterm all seem to differ as to what they
        default to - at least on MY box..
dang
response 33 of 79: Mark Unseen   Feb 9 21:12 UTC 1999

Odd.  Every term program I've ever used on every OS I've ever used has 
used ^C and not done anything strange with it.
remmers
response 34 of 79: Mark Unseen   Feb 9 22:00 UTC 1999

Ever used NCSA Telnet on a Mac?
aruba
response 35 of 79: Mark Unseen   Feb 9 23:02 UTC 1999

Windows 3.1 Terminal uses ^C for copy.
devnull
response 36 of 79: Mark Unseen   Feb 9 23:16 UTC 1999

Can't you use q in more?  Where else do people need an interrupt key?

I think the situation with the losing mac telnet is that ^C will send
an interrupt signal via the telnet protocol, rather than sending ^C.
So I think it would interrupt just fine if we just used the default
interrupt key, but didn't try to read what the interrupt key should be set
to.  (That is, if newuser weren't prompting for it, ^C will probalby just
work the way you want it to.)

I suspect newuser asks for a line kill key.  It happens that I'm a fairly
experienced unix user, but I don't happen to remember what the line kill
key is set to.  The fact that newuser prompted me doesn't help.

Why can't we just punt on prompting the user for an interrupt character,
and find a way to make sure that new users will read documentation explaining
this?
pfv
response 37 of 79: Mark Unseen   Feb 10 05:57 UTC 1999

        I'd rather ask why the basic choices outlined above are
        somehow unacceptable..

        It covers the 4|5 major incoming systems, and it makes their
        solutions simple. That they should read a manpage is never an
        issue.. Any idiot should be aware of man-pages as the *nix
        alternative to "hlp" files.. Unfortunately, most man-pages
        were written by eithe illiterates, or - more politely:
        "programmers too busy to learn to write".

        Offer the choices, 1-5, and list the hilights of what keys it
        means.. If they are lost, the magic name *IS* listed, and if
        they are NOT - then they can resolve it AFTER THE FACT.

        In fact... choice #6 could be:

                "screw up your keys with customization, instead"
mdw
response 38 of 79: Mark Unseen   Feb 10 11:41 UTC 1999

The problem with that is that there aren't "5 different packages", there
are hundreds.  Some of the most ubiquitous ones are really lousy too.
Basically, there is no such thing as an "avarage" or "standard".  It's
easy to not be aware of this.  Once you've seen how bad "lousy" can get,
and find something that you can actually live with, chances are you'll
make sure that "good" thing is on everything you care about.  If you
started with someone else's good solution, you may have no idea how bad
it can get -- until you find out the hard way.  I know of several
households in the mid 80's here in Ann Arbor had that tons of Ambassador
terminals (60x80) sitting around.  I imagine the people who learned
about computing on those had an interesting time adjusting to 24x80
video terminals.

One of the reasons newuser asks people what kind of computer they use,
is to collect "useful" data on how people access (or might access) grex.
Unfortunately, the question doesn't really collect useful data anymore.
It would be useful to know what terminal program people were using, what
OS, etc.  The way it's worded, we get responses like:
        Pentium Intel inside
        Mainframes
        486
        Pc, Mac, Silicon, Commodore, etc.
        pc
        Pentium 200 MMX^M
        all kinds
        none
        no comment
        IBM P150
        Pentiums
        Pentium 233 w/MMX
        233 pentium
which I suppose goes to indicate all those intel ads on TV have done
something to people's perceptions.  Only one person used "ibm", and even
they didn't think that was a sufficient description.  Several people
seem to have thought "pentium" was sufficient.  Apparently, microsoft
has a real marketing problem, nobody in this random sample bothered to
mention windows.
pfv
response 39 of 79: Mark Unseen   Feb 10 17:13 UTC 1999

        Yeah, I see your point.. But it becomes then a question of how in
        the world to acquire the info from folks that are, at best,
        blithely unaware of what the question even is..

        ..Or, MicroSoft is so accepted and prevalant that they are all
        presuming that you KNOW they are using 'Doze.. OTOH, the question
        seemed to ask about their _computer_ - and that, as I think of it
        myself, is the hardware (although I'll certainly admit that the
        software is what makes it all glue together).

        Now, it's been a couple years since I first had interest in it,
        but... I seem to recall that telnet clients & hosts can perform
        bidirectional barter as to operations-parameters.. It's a
        longshot, (and I really cringe at the thought), but.. is it both
        possible and advisable to have the host query the hell outta'
        their client? I'd hate to rely on this, but.. If it occured BEFORE
        the keys-selection point, then the program might be able to make
        better guesses - and offer improved choices - which the operator
        could then select with some confidence.. Or, use the information
        acquired to make better choices/customization..

        I'm not sure this entire topic is worth the effort, but I do know
        that having to diddle-dick with stty and setenv TERM... can be
        harrowing - particularly if either side decides to "take a day
        off", and default to something bizzare (mnet's still-prevalent
        ^J is-a-return, for example...)
senna
response 40 of 79: Mark Unseen   Feb 11 11:55 UTC 1999

I usually use your standard telnet programs and don't do much with 
programming.  I'm Joe Average Computer User (tm).  However, I dont' even 
encounter universal terminals in my limited experience.  Various NCSAs 
require me to stty erase to ^? and several programs forced me to play 
with local echo.  There are certain things that really need to be 
established.  I think we somehow need to establish all this in newuser 
without making it sound too complicated.  Is there anyone here with a 
gift for simplification?
pfv
response 41 of 79: Mark Unseen   Feb 11 14:25 UTC 1999

        hehe - Janc has some code that is the epitomy of "simplified",
        but I won't suggest using his time.. If I might, I'd be
        interesting in kibitzing/contributing - snot like mnut wants
        such a contrib..

        Might still behoove us to ask in agora/motd - or even do a bit
        of a search thru the .login's to see what settings are the
        most popular.. 

        Frankly, never having owned (or wanted) a Mac, and being now
        Doze-free, I'd need some data to work from.. It seems to me that
        - any way you want to slice it - you are still looking at
        "pick doze/mac/*nix/<whatever> & 'be a mensch!'"










 0-17   17-41   42-66   67-79       
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss