4 Replies Latest reply on May 22, 2009 7:53 AM by techieg

    Prototyping with Richfaces 3.x Needed for Non-Profit Open So

      Hello All,

      I figured there's nowhere else to go but where expert Richfaces developers reside...right here. After reading about Richfaces 3.x realizing the high potential of this beast, amidst our contemplation between YUI3.x and Richfaces Javascript libraries we decided to prototype on both libraries to enable us derive the ideal library to standardize our projects on based on the outcome. So here I am writing on behalf of a technology non-profit looking to standardize on a Javascript library for a new and all subsequent projects. We need Richfaces 3.x experts to help use the complete Richfaces 3.x package in prototyping the UI (about 2 unique page layouts and about 13 page body variations) of our first planned and flagship open source application. The preferred prototype will be extensively used as part of the actual open source project, the developer(s) will be recognized as a contributor and featured on our Wall of Fame. Interested parties should please email me at techiegz (at) gmail.com with the following details:

      1) your name and contact info (phone # and email address)
      2) Geographic location (for example, Washington, DC, USA)
      3) your reason of interest in volunteering your expertise
      4) level of expertise with YUI 3.x
      5) Interest in further volunteer work in overall and other project scope beyond this
      6) availability and time to complete
      7) willingnes to sign an NDA

      Brief design requirement: will mimic general Zimbra UI layout only (http://www.zimbra.com/products/screenshots.html). I look forward to hearing from you experts.

      Thank you.

        • 1. Re: Prototyping with Richfaces 3.x Needed for Non-Profit Ope

          item number 4 above has a typo, the correct statement is;

          4) level of expertise with Richfaces 3.x

          • 2. Re: Prototyping with Richfaces 3.x Needed for Non-Profit Ope
            ilya_shaikovsky

            From the beginning we should mention that Y! UI is a client side library. And RichFaces provides JSF components and tools for its development. You can't just compare two libraries because it's lives in a different dimensions.. Using just Y! you should carry out wrapping it to JSF components.

            You could check our new layout components page, layout/layoutPanel. The components fully based on Y! UI layouts and grids but wrapped to JSF components using RF CDK. So there are no problems to integrate rich UI widgets from any third party to JSF world using RF Components Development Kit.

            • 3. Re: Prototyping with Richfaces 3.x Needed for Non-Profit Ope

               

              "ilya_shaikovsky" wrote:
              From the beginning we should mention that Y! UI is a <b>client side library</b>. And RichFaces provides <b>JSF components</b> and <b>tools for its development</b>. You can't just compare two libraries because it's lives in a different dimensions.. Using just Y! you should carry out wrapping it to JSF components.

              You could check our new layout components page, layout/layoutPanel. The components fully based on Y! UI layouts and grids but wrapped to JSF components using RF CDK. So there are no problems to integrate rich UI widgets from any third party to JSF world using RF Components Development Kit.



              Than for your response. So basically you mean that Richfaces can be used to develop directly with our project(s) while YUI can be used for its front end?

              Also, please elaborate further on "JSF Components & Tools for development" and its advantages over YUI which does not have these.

              • 4. Re: Prototyping with Richfaces 3.x Needed for Non-Profit Ope

                ilya_shaikovsky, are you offering to help with this prototyping? It will not involve backend programming just yet, just front end representation of ideas and features so that other volunteers can pitch in from that point to extend it with backend programming.