Re: how to solve a problem of fetchin' HUGE collection into form

2002-06-21 Thread Elizabeth Barham

A method that I used for a user to find out his or her employee id was
by having a 'search for employee id' link on a page next to a text
field where the user is to enter his or her employee id since most
employees don't know it.

This caused a new window to display, allowing the user to enter in his
or her name. They enter their name, hit submit, and in the same new
window, the results were displayed. When the user selects one of
these, the javascript populates the main browser window (the one that
launched the search page) and the new window closes itself.

Slava_L [EMAIL PROTECTED] writes:

 that's quite nice way.. but then i will need to truncate search
 results if they are too big to be send on client, wont i ?

In the above app, if the search resulted in only one record, then that
record was used to populate the main browser window, otherwise it
displayed all the results (which probably wasn't very wise in
retrospect).

Perhaps if the results are, say, over 25 records, then you could ask
them to be more specific or perhaps make pages for them to select from
- such as when you use a search engine on the web and receive a great
deal of results - 25 each page or whatnot (and perhaps with a text
field to re-do their search since at that point they'd realize that
their search wasn't specific enough).

An extension to the above method is by using javascript to initiate
the first query on the pop-up window, too. If there is only one result
then javascript populates the calling window (such as when a user is
pretty sure that the street name is correct but wants the system to do
a quick check; perhaps feedback could be provided in the status bar).

hth, Elizabeth

 - Original Message -
 From: Dan Cancro [EMAIL PROTECTED]
 To: 'Struts Users Mailing List' [EMAIL PROTECTED]
 Sent: Friday, June 21, 2002 10:01 AM
 Subject: RE: how to solve a problem of fetchin' HUGE collection into form
 
 
  It sounds like you need to replace your drop down box with a link to a
  search screen.  On the search screen, the user types in a few letters and
  the system displays just the streets that start with those letters.  Then
  the user picks one and goes back to the form.
 
 
   -Original Message-
   From: Slava_L [mailto:[EMAIL PROTECTED]]
   Sent: Thursday, June 20, 2002 5:49 PM
   To: Struts Users Mailing List
   Subject: how to solve a problem of fetchin' HUGE collection into form
  
  
   I have  a form with several fields.
   And one of them is SELECT field - 4xmpl streets names.
   All streets names are stored in database, amount 100-300
   thousands records
   And the problem is that when this field renders on the page,
   app is freezing for a long time.
   how am i suppose to solve kinda problem ?
  
  
 
  --
  To unsubscribe, e-mail:
 mailto:[EMAIL PROTECTED]
  For additional commands, e-mail:
 mailto:[EMAIL PROTECTED]
 
 
 
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




how to solve a problem of fetchin' HUGE collection into form

2002-06-20 Thread Slava_L

I have  a form with several fields.
And one of them is SELECT field - 4xmpl streets names.
All streets names are stored in database, amount 100-300 thousands records
And the problem is that when this field renders on the page, app is freezing for a 
long time.
how am i suppose to solve kinda problem ? 




RE: how to solve a problem of fetchin' HUGE collection into form

2002-06-20 Thread Dan Cancro

It sounds like you need to replace your drop down box with a link to a
search screen.  On the search screen, the user types in a few letters and
the system displays just the streets that start with those letters.  Then
the user picks one and goes back to the form.


 -Original Message-
 From: Slava_L [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, June 20, 2002 5:49 PM
 To: Struts Users Mailing List
 Subject: how to solve a problem of fetchin' HUGE collection into form
 
 
 I have  a form with several fields.
 And one of them is SELECT field - 4xmpl streets names.
 All streets names are stored in database, amount 100-300 
 thousands records
 And the problem is that when this field renders on the page, 
 app is freezing for a long time.
 how am i suppose to solve kinda problem ? 
 
 

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: how to solve a problem of fetchin' HUGE collection into form

2002-06-20 Thread Arron Bates

Dare I say it... better info design. The most I've had was 500. From the
user's point of view, this is not good.

The freezing will most likely not be the server side, but your browser
slowly rolling over and having a cardiac arrest.  :)

Take the lower end of 100,000 options. If eack option had only one
letter, one byte, the dowload is already 1MB. Take that to an average of
say 15 bytes per record up to 300,000 and the result is one impressive
drop-down box.

Try getting the text that would be rendered into Html, get it into flat
Html, and then test it on the browser. I'm quite sure that you'll be
changing your mind and making it a free-text field real quick.


Arron.


On Fri, 2002-06-21 at 10:48, Slava_L wrote:
 I have  a form with several fields.
 And one of them is SELECT field - 4xmpl streets names.
 All streets names are stored in database, amount 100-300 thousands records
 And the problem is that when this field renders on the page, app is freezing for a 
long time.
 how am i suppose to solve kinda problem ? 
 



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: how to solve a problem of fetchin' HUGE collection into form

2002-06-20 Thread Andrew Hill

You want to put 300k records in a select box!?
You havent really thought very hard about this have you?
I wouldnt worry about the app freezing for a long time. Its nothing compared
to the several days it will take your poor users to scroll through the
select box trying to select the street

rofl

Your best bet is to replace the select box with a popup window that has
somewhat more advanced methods for the user to find and select the street
name and then write the value back to the form field using javascript.

-Original Message-
From: Slava_L [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 08:49
To: Struts Users Mailing List
Subject: how to solve a problem of fetchin' HUGE collection into form


I have  a form with several fields.
And one of them is SELECT field - 4xmpl streets names.
All streets names are stored in database, amount 100-300 thousands records
And the problem is that when this field renders on the page, app is freezing
for a long time.
how am i suppose to solve kinda problem ?



--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: how to solve a problem of fetchin' HUGE collection into form

2002-06-20 Thread Slava_L

how to glue it with database table ?
should i always check if entered street are exist in table?



- Original Message -
From: Arron Bates [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, June 21, 2002 10:08 AM
Subject: Re: how to solve a problem of fetchin' HUGE collection into form


 Dare I say it... better info design. The most I've had was 500. From the
 user's point of view, this is not good.

 The freezing will most likely not be the server side, but your browser
 slowly rolling over and having a cardiac arrest.  :)

 Take the lower end of 100,000 options. If eack option had only one
 letter, one byte, the dowload is already 1MB. Take that to an average of
 say 15 bytes per record up to 300,000 and the result is one impressive
 drop-down box.

 Try getting the text that would be rendered into Html, get it into flat
 Html, and then test it on the browser. I'm quite sure that you'll be
 changing your mind and making it a free-text field real quick.


 Arron.


 On Fri, 2002-06-21 at 10:48, Slava_L wrote:
  I have  a form with several fields.
  And one of them is SELECT field - 4xmpl streets names.
  All streets names are stored in database, amount 100-300 thousands
records
  And the problem is that when this field renders on the page, app is
freezing for a long time.
  how am i suppose to solve kinda problem ?
 



 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: how to solve a problem of fetchin' HUGE collection into form

2002-06-20 Thread Slava_L

that's quite nice way.. but then i will need to truncate search results if
they are too big to be send on client, wont i ?


- Original Message -
From: Dan Cancro [EMAIL PROTECTED]
To: 'Struts Users Mailing List' [EMAIL PROTECTED]
Sent: Friday, June 21, 2002 10:01 AM
Subject: RE: how to solve a problem of fetchin' HUGE collection into form


 It sounds like you need to replace your drop down box with a link to a
 search screen.  On the search screen, the user types in a few letters and
 the system displays just the streets that start with those letters.  Then
 the user picks one and goes back to the form.


  -Original Message-
  From: Slava_L [mailto:[EMAIL PROTECTED]]
  Sent: Thursday, June 20, 2002 5:49 PM
  To: Struts Users Mailing List
  Subject: how to solve a problem of fetchin' HUGE collection into form
 
 
  I have  a form with several fields.
  And one of them is SELECT field - 4xmpl streets names.
  All streets names are stored in database, amount 100-300
  thousands records
  And the problem is that when this field renders on the page,
  app is freezing for a long time.
  how am i suppose to solve kinda problem ?
 
 

 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]