Navigation

RSS 2.0 New Entries Syndication Feed Atom 0.3 New Entries Syndication Feed

Show blog menu v

 

General

Use it

Documentation

Support

Sibling projects

RIFE powered

Valid XHTML 1.0 Transitional

Valid CSS!

Blogs : Archives

< Announcing RIFE/Crud 1.0: flexible CRUD scaffolding for RIFE   Ajax, the stink is already bubbling up >
EuroOSCON: Quickly Building Modular and Maintainable Applications with RIFE

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:

Keynote  Full quality Keynote presentation (76.54MB)

QuickTime  Self-playing QuickTime movie (18.43MB)

QuickTime  Interactive QuickTime movie (76.54MB)

Zip archive  Ready-to-run eCalendar example sources (5.31MB)

posted by Geert Bevin in RIFE on Oct 24, 2005 7:58 AM : 2 comments [permalink]
 

Comments

Re: EuroOSCON: Quickly Building Modular and Maintainable Applications with RIFE
The problem of understanding you are mentioning seems to be somehow similar to the difference between relational and oo databases. It always depends on where you are coming from. For me the way rife is taking is far more interesting and consistent than any other conmbination I have seen so far for java.
Not another language to be a pro in, no more mixing between html and code parts. Easy to customize. But this is only a programmer's point of view =)
Re: EuroOSCON: Quickly Building Modular and Maintainable Applications with RIFE
You're right, where you're coming from is important for the understanding. What I always noticed is that people are making assumptions on where you are coming from and evaluating your technology that way. In RIFE's case for example, the fact that it's done with Java and optionally some XML, makes a lot of people think that I come form a rigid and bloated enterprise development background. In fact, it's totally the opposite, I come from a scripting background and first programmed years in Perl and PHP.
It's after having been bitten by the maintenance and consistency problems of these, that I decided to create a quick-results framework in Java that still keeps a focus on maintainability.

Often it takes some explaining before people are prepared to look at things in that way.

Add a new comment

Comments on this blog entry have been closed.

< Announcing RIFE/Crud 1.0: flexible CRUD scaffolding for RIFE   Ajax, the stink is already bubbling up >
 
 
 
Google
rifers.org web