We are happy to release a preview of QuipuKit version 1.1 to let its users try the new features before the official release is announced.
This release mainly concerns compatibility with Portlets (JSR 168), Ajax4jsf and JBoss Seam. To get your hands on it, please download the distribution package here: http://www.teamdev.com/downloads/quipukit/quipukit-1.1.eap1.zip
This build is bundled with a built-in evaluation license which expires January, 20, 2007.
Our plans is to release 1.1 at the beginning of January, 2007.
New in this version:
Portlets compatibility
Ajax4jsf compatibility
JBoss Seam compatibility
JavaScript function for refreshing DataTable/TreeTable using Ajax (see "Using Dynamic Loading" section in the DataTable and TreeTable documentation)
Various bug fixes
Known issues:
Client-side validation doesn't work in Portlets so far.
When used in Portlets, Ajax-enabled loading modes don't work in QuipuKit components.
Client-side validation doesn't work inside components reloaded with Ajax.
Problems when using Ajax4jsf version 1.0.5. These appear occasionally resulting in "A4J is undefined" JavaScript error. As a temporary solution, we recommend using Ajax4jsf version 1.0.3.
Usage instructions:
No additional configuration is required to ensure compatibility of QuipuKit with the mentioned frameworks. However, the following should be noted:
For Portlets: To ensure that default styles of QuipuKit components are correctly applied, you should specify the following CSS reference in the page before specifying any other CSS files:
<link rel='stylesheet' type='text/css' id='main_css'
href='/<AppName>/teamdev/internalResource/teamdev/jsf/renderkit/default.css'/>where is a Portlet context path.
For Ajax4jsf: To reload some components using Ajax4jsf, it's necessary to wrap them into the <a4j:outputPanel> tag. The exact list that requires such wrappers is not yet known as the testing process is still in progress. For example,
<a4j:outputPanel id="tableWrapper">
<q:dataTable>....</q:dataTable>
</a4j:outputPanel>Please note that because this is a pre-release version, QuipuKit functionality and stability may appear below the quality standards you would normally expect of beta versions.
We encourage you to share your ideas, problems and experience with us. Visit our forum at http://support.teamdev.com/quipukit or e-mail to quipukit-support@teamdev.com.