I am going to have a couple themes running through my posts over the coming weeks and months.
The first is “Why Spry?”. In this, I will discuss how and why Spry came about, what our goals were and where we are going.
The second is “What’s Next?”. This will talk about some of the features and changes coming up in 1.5.
Today, we will start with “Why Spry?”
The Spry team is a small subset of the Dreamweaver team. In the fall of 2005, we were starting to think about the next set of new features. Ajax was making its name known and it was pretty obvious, as a web design tool, that we should look into it.
We started looking into the various frameworks that were available. After looking through a bunch, some themes developed:
- Many had a lot of dependencies: many files had to be corralled to enable functionality.
- It was hard to style: Markup was injected programmatically. It was hard to know what code ended up on you page.
- It wasn’t easy. The learning curve was pretty steep.
But we didn’t want to make our own framework. We thought that maybe Dreamweaver could support a popular framework or two…