RE: non-editable text area

Since my request started this, I guess I'd better say
something here.

I do agree that generally speaking it is a bad idea to
have read-only form attributes, and I understand
John's point completely.  Its generally confusing to
the user and against the entire premise of an HTML
user input form. 

However, there are times it is necessary and there are
things that can be done to make it less confusing.  In
my case I have a description memo field in a database.
 Due to issues beyond my control the memo field
essentially is a series of comments by people all
contantenated together.  

The form I have allows the user to add to the
description field in the database.  Due to the nature
of the description the user is likely to add, they
need to be able to see the current database
description field in front of them while they are
entering data in my form.  The suggestion of a pop-up
window was made, but it was decided the user could too
easily 'lose' the window.  Thus the information needs
to be on the same page the data is entered into. 
Since its in a memo field it needs to be in a
scrollable box to allow maximum viewing capabilities
with minimum screen realestate being used.

There was a DHTML solution that was suggested to me
and looks very interesting.  Its not what I was
originally thinking, but it can be made to look very
different than typical HTML text area boxes.  This
would lessen user confusion by making the viewable
description section look very different than the rest
of the form.

I have not yet decided exactly how I will implement
this.  I appreciate everybody's comments and help (and
warnings!).  I've got several ideas now on different
ways to deal with this problem.

Rebecca

--- Jim O'Brien <JObrien(at)witness.com> wrote:
> I've read several of the threads on this matter and
> while I do agree that
> "input" boxes, etc. ARE indeed for user input, I
> disagree that there is
> never a case where a "readonly" text box can be used
> and used successfully.
> 
> Let's say that you have a form that as the user
> picks his/her options the
> form calculates and gives the total at the bottom of
> the form.  There is
> absolutely nothing wrong with the total dumping into
> a textbox that has been
> given a readonly command.  When the form, with the
> completed  calculations,
> is sent; then you don't have to worry about the
> "grand total" being altered
> by the user... (barring Netscape, of course ;) )
> 
> I know. I know.  There are better implementations of
> calculators, but for a
> simple calculator where e-commerce doesn't really
> exist and JavaScript
> works.  Then, I say use it.  This is just one case I
> can think of off the
> top of my head.
> 
> - "the Design Guy"
> 
> 
> 
> -----Original Message-----
> From: Kukla Fran and Ollie
> [mailto:weblists2001(at)yahoo.com]
> Sent: Wednesday, August 22, 2001 22:39
> To: woodduck(at)mbay.net; hwg-techniques(at)hwg.org
> Subject: Re: non-editable text area
> 
> 
> Input boxes are for user input. Period.  If used
> them differently than what 
> the user expects, the problem belongs to the code
> designer and not the user.
> 
> If you are relying on a multi-page order form where
> page one provides for 
> inputting data by the user, then use the input boxes
> as intended.  When the 
> user submits the page for verification prior to
> final submission, the data 
> collected can be displayed via JavaScript and thus
> prevent any user 
> modification.
> 
> At 17:41 2001-08-22 +0000, woodduck(at)mbay.net wrote:
> >Hi John,
> >
> >Well, I do differ.  There are times when you don't
> want the user to mess 
> >with the
> >info in the box.  For instance, I have an order
> form.  The user inputs the
> >quantity he/she wants and the calculated amount
> appears in a text box 
> >elsewhere
> >on the form.  If that user were to have the ability
> to make changes in the 
> >box
> >reflecting the calculated total, it could cause
> real problems.
> >
> >Peggi
> >
> >Peggi Rodgers
> >Flash Developer
> >Misty Canyon Designs
> >www.mistycanyon.com
> >prodgers(at)mistycanyon.com
> >
> >
> > > While others may certainly differ, I think form
> controls are best used
> > > to allow user input. Period.
> > >
> > > --John
> > >
> 
> 
>
_________________________________________________________
> Do You Yahoo!?
> Get your free (at)yahoo.com address at
http://mail.yahoo.com


=====
Do while Project<>Completed
   if impossible = true then
      rethink(approach)
      set impossible = false
   end if
loop

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA