| form & lookup columns [message #172352] |
Mon, 14 February 2011 09:55  |
![Wolf[1] is currently offline](/forum/theme/default/images/offline.png "Wolf[1] is currently offline")
Wolf[1]
Messages: 2
Registered: February 2011
Karma: 0
|
Junior Member |
|
|
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
|
|
|
|
| Re: form & lookup columns [message #172353 is a reply to message #172352] |
Mon, 14 February 2011 10:00  |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
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?
>
If you want that to hapen without submitting the page back to the
server, you have two possibilitioes. One is a partial resubmit using
IIRC Iframes, the other is to downlaod the whole bloomin lot and use
javascript - and a lot of it - to dynamically change what appears on
one box as a result of selecting in another, without reference to the
server..
This means effectively replicating a lot of what SQL does in javascript
on data held in javascript arrays.
It is not trivial.
I am not clueful on iframes, but these may represent a simpler approach.
> Thanks a lot
>
> Best regards
|
|
|
|
|
|
| Re: form & lookup columns [message #172357 is a reply to message #172353] |
Mon, 14 February 2011 10:30 |
Captain Paralytic
Messages: 204
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On Feb 14, 10:00 am, The Natural Philosopher <t...@invalid.invalid>
wrote:
> 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?
>
> If you want that to hapen without submitting the page back to the
> server, you have two possibilitioes. One is a partial resubmit using
> IIRC Iframes, the other is to downlaod the whole bloomin lot and use
> javascript - and a lot of it - to dynamically change what appears on
> one box as a result of selecting in another, without reference to the
> server..
>
> This means effectively replicating a lot of what SQL does in javascript
> on data held in javascript arrays.
>
> It is not trivial.
>
> I am not clueful on iframes, but these may represent a simpler approach.
Actually you have forgotten AJAX.
|
|
|
|
| Re: form & lookup columns [message #172358 is a reply to message #172352] |
Mon, 14 February 2011 10:31 |
Captain Paralytic
Messages: 204
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On Feb 14, 9:55 am, Wolf <wolfinforma...@gmail.com> 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
Did you try searching the web for
php dynamic drop down list
Worked for me
|
|
|
|
| Re: form & lookup columns [message #172360 is a reply to message #172355] |
Mon, 14 February 2011 10:53 |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
Wolf wrote:
> Thanks a lot for your suggestion; have you got some links with
> examples of this solution?
>
which one?
Iframes - there probably are solutions out there. I dunno.
Javascript? its a question of replicating a lot of SQL style stuff in
javascript and no I have no examples. Took me long enough to write a
much less complex version of this myself.
The approach I followed was to have EVERY POSSIBLE screen loaded, and
hide everything except the starting point, and unhide the bits that
became relevant as selections were made. In my case it was a giant
flyout menu system, so my event triggers were onmouseover events. In
your case you probably want to use onselect() events or onclick()..
Really you are building a custom web page without the convenience of
form input elements, if you go this route.
And RELYING 100% on javascript being enabled.
However to do this seamlessly without the user actually pressing a
button, you will have to use some form of javascript event handler, even
if its as crude as an onselect.. to trigger either javsacript driven
page reformat, or a partial reload of the page.
What iframes allow, is that partial reload into an area of the page
without reloading the whole page, which means you can do a mini form
submit of a part of a form to allow the server to dish up the clever stuff.
You still have to trigger that somehow, though, and I am not enough of a
guru to say whether or not that can happen without some sort of javascript.
I am hoping that better gurus will be able to help more.
I think the main point to make is that this is a very big task
indeed..days if not weeks, of work. Not a quick cut and paste of some
crib code.
And will require you to acquire some pretty in depth knowledge of bits
of javascript, the DOM and the way server and client side languages
work, to get it done.
> thanks
>
|
|
|
|
| Re: form & lookup columns [message #172361 is a reply to message #172357] |
Mon, 14 February 2011 10:54 |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
Captain Paralytic wrote:
> On Feb 14, 10:00 am, The Natural Philosopher <t...@invalid.invalid>
> wrote:
>> 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?
>> If you want that to hapen without submitting the page back to the
>> server, you have two possibilitioes. One is a partial resubmit using
>> IIRC Iframes, the other is to downlaod the whole bloomin lot and use
>> javascript - and a lot of it - to dynamically change what appears on
>> one box as a result of selecting in another, without reference to the
>> server..
>>
>> This means effectively replicating a lot of what SQL does in javascript
>> on data held in javascript arrays.
>>
>> It is not trivial.
>>
>> I am not clueful on iframes, but these may represent a simpler approach.
>
> Actually you have forgotten AJAX.
Bugger, Captain, that is what I meant.
If you can fill him in on that..I'll step back.
Not having ever used it, I am off my sphere of competence.
|
|
|
|
| Re: form & lookup columns [message #172362 is a reply to message #172352] |
Mon, 14 February 2011 11:02 |
 |
richard
Messages: 213
Registered: June 2013
Karma: 0
|
Senior Member |
|
|
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.
|
|
|
|
| Re: form & lookup columns [message #172363 is a reply to message #172362] |
Mon, 14 February 2011 11:05 |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
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.
|
|
|
|
| Re: form & lookup columns [message #172364 is a reply to message #172353] |
Mon, 14 February 2011 12:02 |
Tim Streater
Messages: 328
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
In article <ijaugn$7at$1(at)news(dot)albasani(dot)net>,
The Natural Philosopher <tnp(at)invalid(dot)invalid> wrote:
> 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?
>
> If you want that to hapen without submitting the page back to the
> server, you have two possibilitioes. One is a partial resubmit using
> IIRC Iframes, the other is to downlaod the whole bloomin lot and use
> javascript - and a lot of it - to dynamically change what appears on
> one box as a result of selecting in another, without reference to the
> server..
>
> This means effectively replicating a lot of what SQL does in javascript
> on data held in javascript arrays.
>
> It is not trivial.
That was my first approach when faced with the problem. Doesn't scale as
the amount of JS (and I was generating it using PHP) goes up as the
product of the number of selects.
> I am not clueful on iframes, but these may represent a simpler approach.
That was my second approach. I constrained the iframe's size by putting
it in a table cell (and there may well be better ways of doing *that*),
connected an onselect handler to the first select, that caused a reload
of the iFrame based on what had been selected. I still had to generate
the whole page for the iframe using PHP, including, obviously, onselect
handlers for the next select. You need one iframe for each select except
the first. This approach works better, but still transfers more data
each time than you'd like.
In the end I learnt about ajax, and used that. The onselect handler
makes an ajax request, and the PHP script returns the appropriate data
so the adjacent select can be loaded by the callback function you
specify in your ajax call. No iframes, and a lot less data transferred.
I'm assuming, here, that you've got some method of putting data into
your database which is separate from what we're talking about here, and
so you need a method that works independently of the amounts of data in
each table. So when the page is loaded, it should use ajax to load up
the first select (regions). When the user chooses one, you load the
second select (province). And so on.
But note this: if the user chooses a region, then a province, and then a
town, you've got three selects populated. If now the user goes back and
chooses a new region, you'll have to dump the data in the second and
third selects (province, town) and repopulate the second select
(province).
--
Tim
"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted" -- Bill of Rights 1689
|
|
|
|
| Re: form & lookup columns [message #172365 is a reply to message #172363] |
Mon, 14 February 2011 12:01 |
|
richard
Messages: 213
Registered: June 2013
Karma: 0
|
Senior Member |
|
|
On Mon, 14 Feb 2011 11:05:40 +0000, 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.
Tough shit. I'm not writing code to satisfy 5% or less.
Do you think the people at the big corporate sites are gonna give a rats
ass because a few whiners who use some obscure browser on some obscure OS
can't see half the data?
I write my code for functionality first, looks second.
I'm working on a page now that has JS in it but that's purely for
navigational purposes. If they have JS turned off, fine. They just get one
extra long page to look through.
|
|
|
|
| Re: form & lookup columns [message #172366 is a reply to message #172360] |
Mon, 14 February 2011 12:11 |
Tim Streater
Messages: 328
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
In article <ijb1id$bq3$1(at)news(dot)albasani(dot)net>,
The Natural Philosopher <tnp(at)invalid(dot)invalid> wrote:
> Wolf wrote:
>> Thanks a lot for your suggestion; have you got some links with
>> examples of this solution?
>
> which one?
>
> Iframes - there probably are solutions out there. I dunno.
>
> Javascript? its a question of replicating a lot of SQL style stuff in
> javascript and no I have no examples. Took me long enough to write a
> much less complex version of this myself.
>
> The approach I followed was to have EVERY POSSIBLE screen loaded, and
> hide everything except the starting point, and unhide the bits that
> became relevant as selections were made. In my case it was a giant
> flyout menu system, so my event triggers were onmouseover events. In
> your case you probably want to use onselect() events or onclick()..
Use ajax as I just posted.
> Really you are building a custom web page without the convenience of
> form input elements, if you go this route.
>
> And RELYING 100% on javascript being enabled.
Of course it will need to be enabled. I'm always amused by people saying
make your page work without JS.
> However to do this seamlessly without the user actually pressing a
> button, you will have to use some form of javascript event handler, even
> if its as crude as an onselect.. to trigger either javsacript driven
> page reformat, or a partial reload of the page.
>
> What iframes allow, is that partial reload into an area of the page
> without reloading the whole page, which means you can do a mini form
> submit of a part of a form to allow the server to dish up the clever stuff.
True but see my other post.
> You still have to trigger that somehow, though, and I am not enough of a
> guru to say whether or not that can happen without some sort of javascript.
"No" is the answer.
> I think the main point to make is that this is a very big task
> indeed..days if not weeks, of work. Not a quick cut and paste of some
> crib code.
>
> And will require you to acquire some pretty in depth knowledge of bits
> of javascript, the DOM and the way server and client side languages
> work, to get it done.
This is all true. It's quite a big task if you don't have much
experience.
--
Tim
"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted" -- Bill of Rights 1689
|
|
|
|
| Re: form & lookup columns [message #172367 is a reply to message #172365] |
Mon, 14 February 2011 12:13 |
Captain Paralytic
Messages: 204
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On Feb 14, 12:01 pm, richard <mem...@newsguy.com> wrote:
> I write my code for functionality first, looks second.
> I'm working on a page now that has JS in it but that's purely for
> navigational purposes. If they have JS turned off, fine. They just get one
> extra long page to look through.
You crack me up! Since practically nothing you write actually works,
it doesn't matter what is turned on or off.
|
|
|
|
| Re: form & lookup columns [message #172370 is a reply to message #172366] |
Mon, 14 February 2011 13:06 |
sheldonlg
Messages: 166
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 2/14/2011 7:11 AM, Tim Streater wrote:
> In article <ijb1id$bq3$1(at)news(dot)albasani(dot)net>,
> The Natural Philosopher <tnp(at)invalid(dot)invalid> wrote:
>
>> Wolf wrote:
>>> Thanks a lot for your suggestion; have you got some links with
>>> examples of this solution?
>>
>> which one?
>>
>> Iframes - there probably are solutions out there. I dunno.
>>
>> Javascript? its a question of replicating a lot of SQL style stuff in
>> javascript and no I have no examples. Took me long enough to write a
>> much less complex version of this myself.
>>
>> The approach I followed was to have EVERY POSSIBLE screen loaded, and
>> hide everything except the starting point, and unhide the bits that
>> became relevant as selections were made. In my case it was a giant
>> flyout menu system, so my event triggers were onmouseover events. In
>> your case you probably want to use onselect() events or onclick()..
>
> Use ajax as I just posted.
>
>> Really you are building a custom web page without the convenience of
>> form input elements, if you go this route.
>>
>> And RELYING 100% on javascript being enabled.
>
> Of course it will need to be enabled. I'm always amused by people saying
> make your page work without JS.
>
>> However to do this seamlessly without the user actually pressing a
>> button, you will have to use some form of javascript event handler,
>> even if its as crude as an onselect.. to trigger either javsacript
>> driven page reformat, or a partial reload of the page.
>>
>> What iframes allow, is that partial reload into an area of the page
>> without reloading the whole page, which means you can do a mini form
>> submit of a part of a form to allow the server to dish up the clever
>> stuff.
>
> True but see my other post.
>
>> You still have to trigger that somehow, though, and I am not enough of
>> a guru to say whether or not that can happen without some sort of
>> javascript.
>
> "No" is the answer.
>
>> I think the main point to make is that this is a very big task
>> indeed..days if not weeks, of work. Not a quick cut and paste of some
>> crib code.
>>
>> And will require you to acquire some pretty in depth knowledge of bits
>> of javascript, the DOM and the way server and client side languages
>> work, to get it done.
>
> This is all true. It's quite a big task if you don't have much experience.
>
Absolutely AJAX! It is not such a big deal. There are links out there
with sample code to do the send and to process the receive.
For the OP:
It basically works like this:
1 - The selection of the region invokes a JS call.
2 - That call sets up a listener and sends an asynchronous message to
the server where the php file it calls does a db search for the provinces.
That file also creates a message that it sends back to the listener.
3 - The listener receives the message in JS and processes it creating
the proper HTML.
Google for some examples. What I did when I learned it was to set up my
own general purposes modifications from that code I found and now I use
it as a sort or library whenever I need to use AJAX.
Of course what Tim says is quite true. If you are the beginning stages
of programming, it will take a bit to understand the concept of this
kind of programming.
Without JS, just forget it.
--
Shelly
|
|
|
|
| Re: form & lookup columns [message #172371 is a reply to message #172363] |
Mon, 14 February 2011 13:14 |
sheldonlg
Messages: 166
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
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.
--
Shelly
|
|
|
|
| Re: form & lookup columns [message #172373 is a reply to message #172371] |
Mon, 14 February 2011 16:28 |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
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.
|
|
|
|
| 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: 0
|
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
]