Hey gang,
As part of my previous post on ajax frameworks, I went ahead and created a page here on the libraries I use and why. I link to the download (the version I use, which usually is the released version but in some cases not; I also talk about what’s different when this is the case) and documentation.
I’d love to hear back from you about libaries you like and why. I’ll add them to the page.
As we as a network start playing with ajax more and more, the questions come up regarding the frameworks we use to do all the gruntwork for us. I’m a big fan of the Prototype library for many reasons and I’ve blogged about it here extensively, but I don’t use Prototype’s Ajax code.
Instead, I use moo.fx’s ajax library, moo.ajax. The thing is 3K and standalone. It doesn’t have all of the Prototype librarie’s functionality, but it has most of it. Read the rest of this entry »
Question..if we were to standardize on a textarea replacement editor…which one would you use?
I have tried a couple on side projects, eventually I picked FCKeditor (yes, funny name). I looked at jot’s editor but couldn’t get it to work, though I wasn’t very persistent. I also couldn’t do much with Wordpress’s, though it also seems to work well.
Question 2: as we try to remove markup from the data, is there a place for textarea fields with markup? Or is it a sign of a bad design if users are entering in markup?
-ned
via ajaxian
Particletree has posted two parts in a series for designers trying to develop site structures that will use Ajax for some of their functionality – “A Designer’s Guide to Prototyping Ajax”. Read the rest of this entry »
One of the aspects of having a lot of action going on around a development space that’s rather new is that you get a lot of people solving problems just like the ones you’re having. These people release their work and you can make use of them if you like.
So you go download a few, pick the one that looks best and get started working. Meanwhile ten more solutions hit the market and you’ve already commited yourself. Stopping what you’re doing and going back has that oh-so-familiar pitfal that we’ve all experienced: you either waste a lot of time reading up and trying out those ten new things or, almost worse, discover that someone has a better solution than the one you’re half way through implementing.
I saw this post below on Ajaxian today and figured I’d read it because I’d been curious about Rico and Dojo in particular but hadn’t gotten around to trying them out. Dojo is friggin awesome. From a tech prod perspective, I think it’s the slickest thing I’ve seen yet. Implementing the various aspects of the Dojo platform seems super-duper easy, almost to the point that you don’t need to know a lot of javascript. So now I gotta go download, install, and fiddle with it for a few weeks and then probably rewrite some of my existing work. Sheesh.
In the article linked to below, you’ll find screencasts for each of the six frameworks. They aren’t terribly detailed, but the give you a decent idea of what it’s like to actually use the libraries. Read the rest of this entry »