Limitations of trial

We are thinking of using this for one of our projects but we would like to test it out properly. What are the restrictions on the Free Trial? What can we expect on the Full purchase?

If we develop with the Trial now can be buy the license when we go in production or is the trial license going to "crap" out on us with 15 day limitation? thus we would have to start developement again with full software version?

Ideally what we would like to do is develop the software with Trial, test it using the trial for as long as possible then when deploying out production application on the clients server, we would just buy a license for them. Can we do this? Saves us having to buy a license if we don't need it.

Sorry just to add, we won't be using the datagrid just the panels and tabs and things. So what are the limitations of these? They're not going to act erratic are they?

The trial license allows using the code for testing and evaluation only. If you are using the library for the actual development of your applications - each developer should have a valid ActiveWidgets license. The license applies to the developers only (not to the deployment) - you may deploy the application to one server, multiple servers or do not deploy at all - still every developer using the library should have a license during the development phase.

Hold on a minute, it's a bit of a catch 22 situation; How can you Evaluate and Test an application written using the ActiveWidgets without developing an application that has the components implemented within them in the first place?

I think what you mean is - write the applications using the ActiveWidgets components, test your application, then during the rollout phase purchase the licence? This is the logical phase of any software development method, I can't see any other way we would implement this.

Guess, prototype development using trial is fine but product development requires license. My 2 cents.

Cheers,

Prototyping is part of Product Development.

James,

Test the functionality of the grid, learn its capabilities and then decide whether you will use it in your software. When you say "Saves us having to buy a license if we don't need it.", you imply that your decision to use the grid in production would be affected by something other than the capabilities offered by the grid, such as lack of funds.

This issue is still not clear. We've decided to build our apps with the widgets then during rollout, we'll replace the trial with the real source code and purchase the license if we have to.

Let me clarify this - you CANNOT use the trial version for the actual development of your application. The trial version is licensed for testing and evaluation only. If you hesitate where is the borderline between the evaluation and the actual development, please use this example - as soon as someone checks in the code depending on ActiveWidgets into your application main development branch - at this point each developer should have a valid ActiveWidgets license.

ActiveWidgets is licensed per developer and this does not depend on how and when you will deploy your application (or whether you will deploy it at all) - in any case each developer should have an ActiveWidgets license during the development phase.

I see what you mean.

However from a consumers perspective surely you can't expect developers to purchase multiple licenses without implementing the code within their own project to see how it runs? That would be like purchasing a car without actually taking the testdrive yourself.

The main concern is that we don't know how well it will integrate into our existing systems and whether we can manage a fullscape code conversion to the ActiveWidgets components, I'm not sure I say a way out for either party on this front, hence we might have to reject this product and move to something else as it seems to be based on a "leap of faith" principle.

Is there an opensource version available that would allow us to implement the Widgets according to our implementation models?