| Re: form & lookup columns [message #172375 is a reply to message #172373] |
Mon, 14 February 2011 17:07  |
sheldonlg
Messages: 166
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 2/14/2011 11:28 AM, The Natural Philosopher wrote:
> sheldonlg wrote:
>> On 2/14/2011 6:05 AM, The Natural Philosopher wrote:
>>> richard wrote:
>>>> On Mon, 14 Feb 2011 01:55:42 -0800 (PST), Wolf wrote:
>>>>
>>>> > Hi,
>>>> >
>>>> > I've got a database with these tables:
>>>> >
>>>> > Region (id, name)
>>>> > Province (id, id_region, name, shortname)
>>>> > Town (id, id_province, name)
>>>> > Shop (id, id_town, name...)
>>>> >
>>>> > I've made a form and I'd like that when I choose a region, in the next
>>>> > drop-down menu I want to show provinces of that region
>>>> >
>>>> > I've searched the web to study how to do this thing, but I haven't
>>>> > found anything: could you please give me some hints/ideas/links to
>>>> > tutorials?
>>>> >
>>>> > Thanks a lot
>>>> >
>>>> > Best regards
>>>>
>>>> chained select.
>>>> I've seen plenty of examples of multiple chained selects using
>>>> javascript,
>>>> dhtml, ajax and others.
>>>> What is selected in form 1 dictates what loads into form 2.
>>>
>>> But this does require javascript.
>>>
>>> I can't think of any way of doing it without.
>>>
>>> And then the accessibility brigade will be all over the site complaining
>>> it wont work with Lynx or something.
>>
>> Hell, if the way to make a site work requires JS, then, damn it, it
>> requires JS. If you want to be nice, you can put a message there to
>> tell all those who have it turned off that if they want to see the
>> site they need to turn it back on.
>>
>
> That works fine with a commercial site, but oh boy, try that on a state
> funded site.
>
> Like a hospital or something. Or chairity. Then here is the mobile 'i
> want an app for that' crowd too.
>
From http://www.w3.org/TR/mwabp/#bp-devcap-scripting-support:
=======
Essentially this BP states that it is favorable to support "Class 1"
devices as defined in the first example above if appropriate. Doing this
will ensure that the application can be used across as broad a range of
devices as possible. Furthermore, in some cases a non-JavaScript version
can be useful for simple operations in low-bandwidth situations.
In some cases, however, a particular application simply has no
non-JavaScript counterpart (e.g. a Web based game, an Instant Messaging
client) in which case the server should return a response with human
readable content explaining the situation in more detail.
Ideally, content should be adapted before transfer by checking whether
or not the device supports JavaScript using a DDR or local index.
However, in some cases (e.g. if the device has disabled JavaScript)
JavaScript may still be sent to a device that can't process it. To cover
this case, a <noscript> element should always be included and contain a
suitably informative message.
========
to me that means that the if the app needs JS, then they should turn not
turn off JS. Who does that, anyway? Nearly anyone I talk to who uses a
computer at all doesn't even know the word Javascript, much less
actively disable it. Anyway, who other than paranoid computer geeks
deactivates JS?
--
Shelly
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]