"Degrade", in the parlance of coders, means "doesn't break other stuff if it's not supported". So, if the user's browser doesn't support AJAX, this module shouldn't prevent the calling module from functioning normally, albeit without the nifty AJAX functionality.
<br clear="all"><br>-- <br>Dan Ziemecki<br>Philosopher. Curmudgeon. Nerd.
<br><br><div><span class="gmail_quote">On 3/16/06, <b class="gmail_sendername">Derek Wright</b> <<a href="mailto:derek@dwwright.net">derek@dwwright.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Fri, 17 Mar 2006 00:19:42 +1100 "Jeremy Epstein" wrote:<br><br>> (since the current method degrades well without JS).<br><br>pardon my general ignorance of AJAX and JS, but what does "degrade"
<br>mean in this context? normally, i'd think "code that degrades" isn't<br>something to cheer about. ;) if there's a quick 1 sentance<br>explaination (or a link), i'd appreciate it.<br><br>otherwise, thanks for this contribution. from what i can gather, this
<br>seems like it could help a lot of module UI's out there.<br><br>here's one: i'm thinking of event-enabled nodes... when you enter the<br>start time, the end time could be automatically pre-filled to be some<br>configurable event duration (
e.g. 1 hour) into the future from the<br>start time. that'd be a nice feature. don't know if this requires<br>activeselect or not (see <a href="http://drupal.org/node/25618">http://drupal.org/node/25618</a>), but maybe<br>
activeselect would make it easier to do...<br><br>thanks,<br>-derek (dww)<br><br><br><br><br></blockquote></div><br>