Blogs : Latest entries
|
|
|
Mark blogged about our recent release of RIFE/Crud, but sadly his blog doesn't allow comments, so I'm replying in a separate blog post. Rife CRUD scaffolding customization does not look nearly as flexible as Ruby Rails scaffolding, but that is fair: Rife does its scaffolding at runtime so there is no code to tweak - different than Ruby Rails where you can edit the generated .rhtml, Ruby controller, etc. files.
It depends on what you categorize as flexible, all distinct functionalities in RIFE/Crud have been extracted into dedicated methods in the RIFE element implementations (components). You can thus easily create your own element, re-use the automated logic and inject your element into the auto-generation logic. The benefit is that you don't modify the automatic behavior and still can benefit of library upgrades and bug fixes. You can of course also replace an entire element by your own. I like the superb runtime performance of simple JSPs (with custom tag libraries) but there is no reason to believe that the runtime overhead of Rife and Rife CRUD scaffolding would be too bad
The performance should be as good or better than JSP. All auto-generated views are on-the-fly compiled to byte-code and loaded as regular Java classes. You thus get all the benefits, agility and performance. Thanks for looking into RIFE/Crud, I hope you will look a bit further at all the rest that RIFE has to offer and consider it for a next project. |
|
I talked numerous times with people about which platform to adopt for RIA development. While I never have been a huge Flash fan, I've been continuously saying that using it instead of Ajax is still the best solution and that OpenLaszlo's choice of Flash makes a lot of sense. Just look at the innerHTML Gotchas blog post over at ajaxian.com. Some weird compatibility problem with Internet Explorer makes it impossible to dynamically add rows to tables. Can you believe that? It's not like adding table rows is some esoteric capability that nobody would ever use. This is just one of the many compatibility problems. To me, all this smells like the DHTML flop from 6 years ago all over again, except that they're doing it asynchronously this time It's simple, people, unless you have infinite resources (like Google), building a complex RIA using Ajax will just make your development team drown under the 'odd little compatibility problems'. And, after all the effort, you'll still target less users because the adoption of 'supported browsers' is less than the install base of Flash player 7. |
|
The RIFE presentation I did on Tuesday at EuroOSCON was a success. Even though I personally thought I rushed the presentation a bit, many people were truly interested by the project afterwards. I missed the presence of a clicker though. I had to stick close to the laptop or step back all the time while explaining, this made me reach out a lot less to the audience than I wanted to. People gave me a hard time during the questions, asking details about the logic-less template engine and other controversial aspects of RIFE. The template engine seems to be one of the features that people have the most problems with. I couldn't respond to every use-case immediately, but met up with some people afterwards and explained everything in detail. Anyway, for those that are interested, here are the files of the presentation:
|
.
Full quality Keynote presentation
Self-playing QuickTime movie
Ready-to-run eCalendar example sources