http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/ Computers are useless. They can only give you answers. Wed, 08 Sep 2010 20:34:38 +0000 http://wordpress.org/?v=2.6.3 http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-10610 Noah Macias Fri, 28 May 2010 15:10:49 +0000 http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-10610 If I had a penny for each time I came here.. Amazing article. If I had a penny for each time I came here.. Amazing article.

]]> http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-4431 Atif Khan’s Blog » Blog Archive » Is RIFE dead? Tue, 28 Apr 2009 18:52:28 +0000 http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-4431 [...] wrote a blog entry in April 2007 about RIFE. It has been 2 years since I wrote that entry. I had mentioned that RIFE [...] [...] wrote a blog entry in April 2007 about RIFE. It has been 2 years since I wrote that entry. I had mentioned that RIFE [...]

]]> http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-210 Geert Bevin Wed, 11 Apr 2007 01:24:33 +0000 http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-210 What particular part makes you uncomfortable? I know of several people that were not thrilled about the templates until they started to look at them as being entirely different to what they expect from other templating solutions. You really heave to compare RIFE's templates with PowerPoint templates where you provide all content elements and placeholders and then assemble the final result from the template inside your application (which is in Java in this situation). Your comment about the template syntax not being designer friendly is not true however since this is totally up to you. I've been using the comment syntax for years and created many templates that look just fine in the browser. Of course, if you really want the design to show up correctly in a visual manner, you do have to add template content that will not be used in the final result. This is similar to Wicket's template inheritance where they just mark up which part of a child template has to be considered for inclusion in a parent template. With RIFE there's nothing explicitly created for that since block values and block solve all of this implicitly. RIFE 1.6 has a new tag however, which is the comment tag, that allows you to really remove a chunk of content from template processing. Of course, some of this can also be attributed to taste, but many users that didn't like the template syntax at first end up really loving it after using it for a while. It's just totally different from what you've come to expect from other solutions. What particular part makes you uncomfortable? I know of several people that were not thrilled about the templates until they started to look at them as being entirely different to what they expect from other templating solutions. You really heave to compare RIFE’s templates with PowerPoint templates where you provide all content elements and placeholders and then assemble the final result from the template inside your application (which is in Java in this situation). Your comment about the template syntax not being designer friendly is not true however since this is totally up to you. I’ve been using the comment syntax for years and created many templates that look just fine in the browser. Of course, if you really want the design to show up correctly in a visual manner, you do have to add template content that will not be used in the final result. This is similar to Wicket’s template inheritance where they just mark up which part of a child template has to be considered for inclusion in a parent template. With RIFE there’s nothing explicitly created for that since block values and block solve all of this implicitly. RIFE 1.6 has a new tag however, which is the comment tag, that allows you to really remove a chunk of content from template processing.
Of course, some of this can also be attributed to taste, but many users that didn’t like the template syntax at first end up really loving it after using it for a while. It’s just totally different from what you’ve come to expect from other solutions.

]]> http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-209 Atif Khan Tue, 10 Apr 2007 23:58:00 +0000 http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-209 Thanks Geert. I will look at the information you provided. As I said, I think I didn't get what I wanted due to steep learning curve. May be your links will help me locate the information. Also, I did look at all the template syntax and I must say that I was still uncomfortable with it. Thanks Geert. I will look at the information you provided. As I said, I think I didn’t get what I wanted due to steep learning curve. May be your links will help me locate the information. Also, I did look at all the template syntax and I must say that I was still uncomfortable with it.

]]> http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-208 Geert Bevin Tue, 10 Apr 2007 22:02:59 +0000 http://www.khanspot.com/2007/04/10/impression-of-rife-web-framework/#comment-208 I also posted this comment on my blog. The content is a bit better written since I re-read it a couple of times ;-) http://rifers.org/blogs/gbevin/2007/4/10/re_impressions_of_rife I also posted this comment on my blog. The content is a bit better written since I re-read it a couple of times
http://rifers.org/blogs/gbevin/2007/4/10/re_impressions_of_rife

]]>