Advantages / Disadvantages of DHTML & JS

[Pauly]

I started learning JavaScript recently with the sole purpose of when I come to learn ActionScript, I will be able to familiarise myself with it better. But thinking about it more I figured I might as well start using JavaScript in my online developments more to pass information through multiple pages or forms, something I never considered at first because I enjoy the visual side a lot more.

But other than browser compatibility are there any other disadvantages that DHTML and JavaScript have?

Please enlighten a JS amateur

[Jamie]

Not too sure but if it is just to pass information through multiple pages or forms, why not use PHP? Then you don't have the browser issues.

[Pauly]

Well I could but for my personal site .... I don't have a clue about PHP and how many people do stuff for free these days :wink:

[Jamie]

true. ;) I'm not much of a php man myself but I do know the basics, and I have stored information from a form and used it on a seperate page a number of times. Give me a shout if you decide to take the php option.

[Pauly]

Learning PHP would just add to my frustration. So much on right now, maybe in a year ;)

[sea otter]

I think JS and DHTML are highly UNDERused and UNDERrated nowadays. They are not the bugbears of "Accessibility & Standards" that so many people think they are.

As with everything, the more you are willing to sacrifice older browsers (what with their non-standard DOM models and dodgy CSS parsers), the easier time you will have.

The only downside to JS is that you must validate any data it generates/manipulates once it reaches the server. For example, if you display prices in a JS form and then process an order based on them without first confirming them in a serverside database, a user could spoof the values and pay whatever they wanted! Same thing goes for any form data. Don't trust ANYTHING that's been manipulated clientside once it hits the servers.

But for non-forms stuff (automatic code generation/manipulation, graphics, cool mouse/keyboard/window stuff, games, etc.) JS and DHTML are great.

[Pauly]

Yea I agree they are under used. You may be interested in a project I am working on, I'll let you know of its release, but the whole concept behind it is it's made to run for me and my friend an no one else, although it does seem targetted at an audience of some kind.

It uses the technology that is capable of running and being displayed on our systems without anything intrusive, different to say the least.

Thanks for the comments :)

[sea otter]

Can't wait to see it :)

I've been working on a very visually interactive proof-of-concept site for some code I'm writing. Lots of DHTML and JS. Yes, it passes the validators, but it's also as much about the look as the content, so sight-impaired users (my best friend happens to be near-blind) won't get the full enjoyment out of it.

And I added code so that NOSCRIPT users get normal, non-graphical buttons, whereas JS-enabled users get nice fancy 3-state rollovers (not too good for usability, that, but it's sorta ok).

<div class="rant">
I tell you, it's fun to do these graphically-oriented sites. It ain't all about WORDS! I like making forms that look like control panels, and letting the user drag them all over the screen to get them out of the way or whatnot.
</div> <!-- rant -->

[Pauly]

:lol: Yes, when you don't worry about usability the possibilities from even a limited skills developer are endless. But when it comes to commercial websites, it can be a pain in the neck.

[sonicgroup]

I'm actually currently working on an internal project that I can't discuss much of, but, in general, it's a web-based project management application.

It makes extensive use of DHTML/JS for certain functions within it's interface (especially on parts of it relating to tracking projects and financials for projects). Stuff like hiding and showing blocks, rearranging things on-the-fly, switching tabs in the interfaces, and doing calculations in realtime.

It's written in PHP and is designed to be run in an intranet environment. However, in the future, I plan on working the front-end over to use XUL and XML-RPC to provide a secure internet interface.

[Pauly]

Sounds interesting. I suppose the faster the system / network is, the fatser your application will be then?

[sonicgroup]

Well, the initial idea is for it to be used internally within a company intranet - this would be the target installation environment. It doesn't really have to do with speed moreso than it's intended audience.

However, the web-based interface would be for those users who are physically "on-site" and need to access the system outside the intranet.