A few months ago, I tried to speak about simplicity and one of the real challenges of building Web 2.0 Apps is how to simplify your applications .
Rudi showed me Erik Burke’s blog and in particular these images which say it much better than I could ever do.
Some of our guys had the great luck to be in NY this week for the AjaxWorld Conference . While there they attended the 4D New York User Group. . They gave a demonstration of the new grid features of 4D Ajax Framework v11 Release 1. As usual the great Jay Harper did a wonderful summary of the session. Here is his summary. Thanks as usual Jay for the great reporting! And thanks to Paul, Gary, Jay and Christophe for organizing this.
Wow, time flies very quickly and the blog hasn’t been updated as Peter pointed out in a very very long time. A few months ago I blogged about a cool new listbox for the web we were working on A Listbox for the Web . No excuse but because of the intensive feedback we received at the summit, from our beta testers and the few kind souls who posted it took us a bit longer than we originally thought. We believe it incorporates everything that was asked for and even more.
Here is a sneak preview of what we will be releasing later this month ListBox Demos
We’d love to hear what you think!
The most common object used by most database developers is still the list view for data. In the 4D world, most developers use either Output forms, Listboxes, 4D View or popular plug-ins such as “AreaList Pro“. So when we were designing 4D Ajax Framework we decided this would be the object developers would use the most.
For that reason, a lot of our early design time was spent trying to create the foundation of a perfect data list view. One of the key features of version 1.1 of the 4D Ajax Framework is our Data Window, which we think is a fantastic composite object for displaying data in a list fashion.
Here’s some of what you can do with it:
Now that we’ve come this far with implementing data list views, we are at the point where we want to add extra features to this object. We’ve already had a number of feature requests from the current user base, ranging from the easy to implement (alternate row coloring), to much more challenging features such as locking columns.
However, we would love to hear from all of you. What are the features that make you drool when it comes to data list views?
Don’t hold back! With our rapid-release model, we are looking at multiple product revs over the next few quarters, so there’s a lot of room for us to add your feature requests.
When we started the Web 2.0 Pack project, one of our goals was to deliver rapid releases that could add more functionality and fix customer issues in a timely fashion. One question that we have debated is how often we should release. Developers want new features but also crave a stable unchanging platform. In short, having too many updates can be as bad as not updating enough.
Our initial release was on February 14th, and we followed that up on May 9th with the 1.1 release. Since then we’ve released a patch for 4D Live Window to fix an issue with “WEB_SetContent”. So right now we are on a 90 day release cycle, but we don’t want to remain in that cycle. Sometimes we will release sooner, and sometimes it will take longer to deliver the quality of release in terms of stability and features.
We’re more interested in getting things right than we are in meeting an arbitrary deadline. For example, another company in our business promised a quarterly release cycle and in a lot of cases their releases have been castigated by their users for being buggy and insufficient quality. Their promise of a release of every 90 days has locked them in to delivering a release even if it isn’t of the quality their users expect and demand. You wouldn’t want that from 4D, and we don’t want to be that company.
Having a rapid release cycle does pose some interesting opportunities for our development team. It necessitates very strong product planning so that we can add features in an incremental fashion, adding value with every release. Each feature gets built in steps and each step is validated and road tested before the next layer of functionality is added. This leads to a much higher quality of release than a “big bang” feature development approach.
Luckily, 4D Web 2.0 Pack is an ideal product for the rapid release model as so many new technologies are getting announced in this area of technology. For example, we are all very excited about the opportunities that the recent “Google Gears” announcement will offer Ajax applications. Our rapid release model ensures that we can look at these advancements in technologies and adopt those which will provide immediate benefit to you, the developer. This of course, ensures that our team needs to always be up to date and always on their toes.
It is exciting to be involved in a technology that is delivering on its promises so fast!
Well, the secret is out of the bag. Steve Jobs, today, announced the way to develop third party apps on the iPhone will be through Web 2.0 applications. In addition, primarily, we would guess, to facilitate the testing of such applications on windows, Apple also announced the release of Safari 3 on Windows. This is very clever of Apple because all browsers are not equal and we can tell you that a lot of our development and testing goes into ensuring browser compatibility, having Safari 3 available on Windows will allow windows developers to test compatibility with Safari before deploying to the iPhone.
Of course, 4D developers are now in a great position to be the leaders in getting their applications onto the iPhone. 4D Web 2.0 Pack, today, offers all of the tools to get your data onto the iPhone. We have already scheduled a session at the summit on iPhone applications, with their unique challenges and opportunities.
Company | Contact 4D | Privacy Policy | © 4D, Inc. 1995-2007 | 
| Powered by
WordPress | Entries (RSS)
and Comments (RSS).
