Andre Charland

+ Follow
since Jul 20, 2007
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Andre Charland

Ruby on Rails and JSP don't really make any sense together. I've seen huge productivity gains once a developer is comfortable with Rails, however there's not point switching if you've already proficient with Java and JSP. Stick with that and look to an Ajax library that plays nicely with Java like DWR, GWT or Nitobi for Java. There obviously lots of other libraries like Prototype, jQuery and Dojo you could look at too.
Yup, I'd answer the same as Bear on this one. Some server side Java frameworks are certainly better than others for working with Ajax. If Java is your like I'd check out DWR, GWT and the Nitobi CompleteUI for Java.
We don't cover jQuery or any other framework specifically. We do however provide code samples for all the topics covered in the book. We created the book and samples this way so you can get a deep understanding of what's going behind the scenes in Ajax. This is very important knowledge for building robust and high performance Ajax apps.
Yes the big win for Ajax is improvement of user experience in your web apps.

Some quick points:
-Ajax can run in any modern web browser (although there are some catches)
-Ajax can add new functionality only found in desktop apps before
-Improves the responsiveness of your web pages
-Reduce server load in some cases

Many chapters of "Enterprise Ajax" are devoted to this very subject so there is obviously lots to say
Yup. You can use Ajax on the front end with almost any modern server and server side language (i.e. php, asp, cfm, java, RoR,
Hi Hesham,

It's hard to say without more info.

[Warning: The sentence below may seem like a product plug]

We do have a sample like this with one of our *commercial* Ajax components: then go to ComboBox/Master/Detail for a demo.

Maybe this helps, if not please provide some more info.
It's difficult to come up with hard and fast rules on when to Ajax-ify an app. In general most web apps/sites can benefit from at least a little more Ajax;-)

Sites like news, blogs, home pages and other text content heavy sites should be very cautious about using Ajax. There are many risks related to SE0, linking, accessibility and just plain annoying users that you need to consider.

Data centric web apps like ecommerce sites, CRM, accounting tools, social networking, email clients, workflow tools will generally benefit from heavier use of Ajax. But when proper usability and interaction design skills are applied.

In Enterprise Ajax we cover many of these issues in the latter half of the book. The case studies in the last chapter will likely be of of particular interest to see how other companies have benefited. The usability chapter points out a couple common pitfalls that show where you can go wrong with Ajax.

I'm not sure I understand all your questions. But I think YUI library is a nice Ajax solution. However, it lacks server side support (i.e you have to do it all yourself). The widgets and framework are very nice and quite compact though.

We've also referenced their efforts in UI patterns which a lot of Bill Scott's work when he was an evangelist at Yahoo.
We don't really cover any DWR in the book.
I think this question would be better suited to somewhere in

Hi There,

We're just starting to dive into Flex development here at Nitobi so I'm not a Flex/AS3/MXML expert...yet;-)

I do know the chapters on usability, accessibility and ui patterns could be useful. Also some some of the JavaScript discussion like patterns, MVC and OOP could be useful since both JS and ActionScript are based on the same ECMA standard, but I'm not 100% sure on this.

15 years ago
Hi All!

Glad to be here and looking forward to some great discussions I'll do my best to answer any and all questions but my expertise is definitely in Usability, User Experience, Business Case and Patterns. Thanks!

Questions about the book:

>1) Is it for the AJAX novice or somebody with AJAX experience, or both.
It is definitely designed for intermediate to advanced developers with at least some JavaScript and programming experience. There are _many_ novice books out there. We definitely tried to cover more advanced topics in Ajax development.

>2) Is it designed to be read cover to cover, or for the reader to reference >depending on their project.
It's not necessary to read the book cover to cover. For example you could skip the Usability chapter with out reading the chapters before it.

>3) Is there a TOC onlive for us to view.
Check out the Safari listing here: Once we get the full up we'll have a better TOC and sample chapter up though.
Well, I guess there a number of different directions this could could go in. I'll try to share some thoughts from our experience building Ajax user interfaces for large businesses and relate that to Java.

First I don't think Java is going away anytime soon. In fact over 1/2 of the customers we serve (and they range across the world, industries and headcounts) are using Java in some flavor on the back end. One of the problems is there are so many different technologies and frameworks that fall under the Java umbrella: Java, POJO, JSP, Servlets, Struts, JSF, Spring, Hibernate, J2EE...just to rattle off a few. Let's not even get into app and web servers. But needless to say Java is going to be living on the server for a _long_ time.

As front end/ui technology for the web though I would have to say it's all but dead. Java applets never really delivered on their promise. Developing the UI layer of a web app through HTML and Ajax talking to Java on the server side makes a lot more from a user adoption point of view. The ability to run an Ajax UI in almost any web browser while providing a rich and satisfying user experience is really what makes it king.

I think I could ramble on forever here so I'll just let you ask more specific questions if you have any
Yes the iPhone and Nokia phones that run browsers based on the latest version of Webkit will run Ajax. It was actually Nokia that did most of the work to make Webkit work on mobile devices. I'm not aware of any other phones/browser combos that you can do true Ajax development on.