Hello, again, Rick,

Thanks for the clarification. Your posts are always enlightening and
informative. I mean that. I am not being sardonic in the slightest.



I have to admit that I don't think they look bad either. However, they
do greatly restrict the GUI team. I like my taste but I know that I do
not have the taste of someone with artistic talent, just like my singing
is rather humdrum. I like my singing too, but no one is going to pay to
hear it for sure. So, I like to have buttons that allow the GUI team to
do their thing. I understand you point on that and have absolutely no
dog in that hunt. I agree that what you do is entirely reasonable.



I do wonder in this case, however, whether you use buttons or rely on
the auto-gui, why use "button" rather than "submit", if you want to
submit? I might also say, that is what submit buttons are for. I
assume, however, that there is a reason to use <input type='button'>
rather than <input type='submit'> and would like to understand that. I
have an old prejudice against JavaScript which may be partly
irrational. I have learned that some things I can only do with
JavaScript. And, that has loosened my prejudice a bit.



Michael McGrady

Rick Reumann wrote:

> I often use the regular html buttons for various things. Users are
> used to seeing these buttons so they know they can click on them. So
> for example someone might have a button "view logs" which doesn't
> necessarily submit a form but opens up a pop up window or maybe goes
> to some other url. Sure you can make images in place of all standard
> html buttons but that that certainly isn't required or necessarily
> even always better. You asked with what seemed like a suprised
> question "Why use an button?" and I'd answer that's what html buttons
> are for - for users to click on. (Actually when you change their
> background color form the default gray, they don't even look that bad
> - although I do realize custom images used as buttons do look the best.)
>
>
> Michael McGrady wrote the following on 10/10/2004 8:56 PM:
>
>> Hi, RIck,
>>
>>
>> I don't understand why this would make someone "make an image look
>> like a form button". I am not sure what that means. All my form
>> buttons are images. They look however I want them to look. I
>> probably don't see what you are saying either. We may be coming from
>> different directions and are passing in the night here.
>>
>>
>> My understanding is that you use an <input type='button'> primarily
>> to do things other than submit. I was not particularly set on <input
>> type='image'>. Why too is he not using <input type='submit'>? I
>> assume there is an answer to this, but I cannot see it in the posts.
>> So, I asked the question.
>>
>> Michael McGrady
>>
>> Rick Reumann wrote:
>>
>>> Michael McGrady wrote the following on 10/10/2004 4:42 PM:
>>>
>>>> Wjau are you using button? Why not use image?
>>>
>>>
>>>
>>>
>>> What's the advantage of using an image in this case? Wouldn't this
>>> require someone to make an image to look like a form button? I'm
>>> probably missing something obvious here:)
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@(protected)
>> For additional commands, e-mail: user-help@(protected)
>>
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)