Hello Everybody,
I wrote a couple functions for WAA to create a oHTML:SLE() with a list box
dropped down via a mouse dblclick. It works fine with MSIE.
Does anybody want to validate/append JScript code to make it working with NS
browser?
--
Regards,

Vladimir

Vladimir,

> I wrote a couple functions for WAA to create a oHTML:SLE() with a list box
> dropped down via a mouse dblclick. It works fine with MSIE.
> Does anybody want to validate/append JScript code to make it working with NS
> browser?

Hey, I could really do with one of those.  How did you do it?

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

I brake for animals - and accelerate for small children.

Hi Phil,

> Hey, I could really do with one of those.  How did you do
it?

Maybe I am missing something but this is really simple and
does not require JScript:

<td>Gender
                <select name="xxxx"
                size="1">
                    <option value="">
                    <option value="F">F = Female
                    <option value="M">M = Male
                </select>

Robert

Hi Robert,
In your case you can only select a value from the list. You cannot edit it.

--
Regards,

Vladimir


"Robert Major" <major@symetric.ca> wrote in message
news:qHsc1DNlEHA.2992@S15147418...
> Hi Phil,
>
> > Hey, I could really do with one of those.  How did you do
> it?
>
> Maybe I am missing something but this is really simple and
> does not require JScript:
>
> <td>Gender
>                 <select name="xxxx"
>                 size="1">
>                     <option value="">
>                     <option value="F">F = Female
>                     <option value="M">M = Male
>                 </select>
>
> Robert
>
>

Hi Vladimir,

> In your case you can only select a value from
> the list. You cannot edit it.

Ah -- I knew I missed something .

Robert

Hi Vladimir,

> In your case you can only select a value from the list.
> You cannot edit it.

If you allow any garbage in the SLE, why do you provide a
restricted list of allowable values at all??

Mind you, I can see reasons for this, but I would like to
know why you think this is a useful feature.

Robert

Robert,

>> In your case you can only select a value from the list.
>> You cannot edit it.
> 
> If you allow any garbage in the SLE, why do you provide a
> restricted list of allowable values at all??
> 
> Mind you, I can see reasons for this, but I would like to
> know why you think this is a useful feature.

I know why I think it' a useful feature.

The users quite often enter the same data again and again - so we can
build an arry to populate the picklist from previous entries.  However,
sometimes they need to enter a new value.

We can capture the new value, run it through a Proper() algo and store it
in the picklist table so that they (and others) can select it next time
(rather than typing it in).

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

Press  to Adopt Me!  I need a better home.

Hi Robert,
Thanks to Phil, he explained instead of me. But actually I didn't think to
capture new values from SLE. I was going just to use a picklist been built
from some dbf data scope. Phil's idea looks more advanced.

--
Regards,

Vladimir


"Robert Major" <major@symetric.ca> wrote in message
news:Nu3ImZPlEHA.2992@S15147418...
> Hi Vladimir,
>
> > In your case you can only select a value from the list.
> > You cannot edit it.
>
> If you allow any garbage in the SLE, why do you provide a
> restricted list of allowable values at all??
>
> Mind you, I can see reasons for this, but I would like to
> know why you think this is a useful feature.
>
> Robert
>
>

Vladimir,

> Thanks to Phil, he explained instead of me. But actually I didn't think to
> capture new values from SLE. I was going just to use a picklist been built
> from some dbf data scope. Phil's idea looks more advanced.

We're back to the quote from Larry Wall:

The three chief virtues of a programmer are: Laziness, Impatience and
Hubris

Laziness is King of course.  There's no reason to re-invent the wheel
unless you think you can make a better wheel.  There's also no reason to
maintain picklist data when the users will do that for you 

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

This BBS has achieved Air superiority.

Hi Phil,

> There's also no reason to maintain picklist data
> when the users will do that for you 

Well, I'm not sure if I agree that is really more efficient
when it comes to validate, clean up and analyze the data.
There is no benefit if the domain of values is known and
fully closed and can lead to a lot of garbage being
collected.  In that case, laziness can be a costly virtue
.

The only situation where I have used such an approach is for
fields where the domain of values is not fully closed.  An
example would be a person's occupation or job title.  In
such cases, a picklist provides the most common values but
allows for exceptions.  But even in those cases, the
exceptions are analyzed as a whole in an "other" category.
If some exceptions tend to reccur, they may get added to the
picklist later.

IMO, it's a very special situation and should be used
sparingly.

Robert