Let me just add that, once you know java, the learning curve is not that steep; it took me about 2 weeks of on/off playing around with the framework to finally "get it". My personal path was:
1. I read and understood the basic building blocks for templates... value(v), block (B, BV), include (I) [ http://rifers.org/wiki/display/RIFE/GuideTemplates ] 2. I followed the in-depth simple blog video, which iteratively introduces most of the key features of rife, essential for app development. [ http://rifers.org/rife_indepth_simple_blog ] After that, I started to move this about, get into the code to understand what's going on for some of the parts (especially with Authentication), asked questions on the list (it's a great community here, and one of the things that got me to get this far into the framework), search the wiki (http://rifers.org/wiki/display/RIFE/Home) and most of it finally makes sense now. Apart from a few extensions you have to make of the Rife classes to take advantage of some Rife features, such as Rife's validation implementations, the framework assumes very little about your code. And if I've not mentioned it yet, the feature I'm loving the most now is Rife's out-of-container testing ( http://rifers.org/wiki/display/RIFE/Out+of+container+testing ); just sweet! :) -- eokyere On 12/5/05, Geert Bevin <[EMAIL PROTECTED]> wrote: > > 1. If RIFE is really all it appears to be (e.g., a complete answer > > to the questions Ruby on Rails has posed to the Java community), > > how come it is not more widely used? It is still a very minor > > player (whether or not this is justified). I was wondering why this > > might be. Could it be to do with its Belgian (i.e., non-US) origins? > > I just wanted to add to this that RIFE never was and still is not > intended to be a RoR-clone for Java. We have been working on the > framework for almost 4 years now and only recently prepped RIFE/Crud > for public release after having used it a long time internally. We > have our own ideals and ideas. Some go intro the same direction as > RoR, but many are also the opposite. It just happens that RoR took > the community by a storm and that people compare RIFE with it. > > Personally I think that the best thing in RoR is Ruby, I don't like > the framework itself very much. Since a wealth of JVM scripting > languages are supported in RIFE (like Groovy), you can get much of > agility that scripting languages give you. > > -- > Geert Bevin Uwyn bvba > "Use what you need" Avenue de Scailmont 34 > http://www.uwyn.com 7170 Manage, Belgium > gbevin[remove] at uwyn dot com Tel +32 64 84 80 03 > > PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 > Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net > > > _______________________________________________ > Rife-users mailing list > Rife-users@uwyn.com > http://www.uwyn.com/mailman/listinfo/rife-users > _______________________________________________ Rife-users mailing list Rife-users@uwyn.com http://www.uwyn.com/mailman/listinfo/rife-users
