Aaron,
You couldn't be more correct. I like to first do it myself, and then if there's
some tool I can use to automate things, great I'm there. Since Ajax can be made
to work in many apps/webpages with just a few dozen lines of code, its worth it
to a developer to know how things are pieced together--by writing it themselves.
Then if you want to use a library that allows you to establish DIV or SPAN names
and link those to database fields, great! One toolkit/library I like is the YUI
(Yahoo's User Interface library) its pretty easy and has a small footprint. But
there's also Dojo--but Dojo, like a lot of Open Source, is a Resume tool for
recent college grads (you know "Hey Microsoft or Google, look what I can do!
Please Hire me.") But DOJO does do some pretty cool stuff.

-Bob Cozzi
www.iSeriesTV.com
iPod your industry news instead of reading it.
Coming July 18, 2006
Ask your friends to tune into iSeriesTV.com

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf
Of albartell
Sent: Thursday, June 22, 2006 9:53 AM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Ajax via RSP/CGIDEV2

One of the things that has amazed me about all these Ajax posts is that
everyone is writing (or attempting to write) the client-side javascript code
themselves. WHY? 

I see where you are coming from Walden and agree with you that a library
should be use.  But also understand that this is a new technology that does
not have all of the wrinkles worked out yet and for a CGI programmer to have
the knowledge of how the grears work under the covers is a great
ace-in-your-pocket to have when the app breaks.

Aaron Bartell 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.