You can download the products from this page for evaluation purpose only.

JIDE Docking Framework, JIDE Action Framework, JIDE Components, JIDE Grids, JIDE Dialogs, JIDE Shortcut Editor, JIDE Pivot Grid, JIDE Data Grids, JIDE Code Editor, JIDE Feed Reader, JIDE Dashboard, JIDE Charts, JIDE Gantt Chart and JIDE Diff (version 2.9.6)

Download Now  | Change Logs | Release for JDK1.4 (jars only)⁽¹⁾ |  Debug Release⁽²⁾ 
Last update on August 20, 2010.

JIDE Desktop Application Framework (version 2.4.0)

Download Now  | Change Logs | Release for JDK1.4 (jars only)⁽¹⁾
Last update on July 6, 2010.

The icon means the link is password protected. You can click How to evaluate JIDE products on the developer forum to see the password. Registration on the forum is required. In your web browser, please allow cookies for jidesoft.com. If you failed to login 5 times in 30 seconds, your IP address will be blocked and have to be unblocked manually so please make sure you wait a while before you try to login again.

Please note, this evaluation package will expire on September 28, 2010. Before it expires, please visit this page and download it again. We will put a new evaluation package once in a while with a new expiration date.

If you have any questions, please feel free to contact us at either sales@jidesoft.com or support@jidesoft.com or post a message on our developer forum under pre-sale support forum. We will be happy to help you.

The evaluation package is for evaluation purpose only. Deploying it in a production environment is strictly prohibited. After you purchase from JIDE and receive a valid license key, you must download a formal release package (the last link on your left) from customer download area. License key will not work on the evaluation package.

⁽¹⁾ JDK5 and above is required. If you are running JDK1.4, please use this line to download the jars generated by Retroweave.

⁽²⁾ In the regular release version, you will not see the line numbers in the stack trace because the debug information is removed from the jars. But if you use the debug jars to run your application to reproduce the stack trace, you will see exact line numbers in the stack trace. Please note, jars in the debug release should only be used for troubleshooting purpose.