I was going to leave posting on all of this for a few days (still working my way through the backlog - I figure by now that the backlog is permanent though), but we have a one day special offer for Resolver One. 66% off ($75) on March 17th 2009 only.
If you've been considering splashing out on Resolver One, now is the time to grab it:
Resolver Systems. Resolver One has the largest known codebase of IronPython anywhere (around 40 000 lines of code in production plus around 130 000 or so in the test framework). Resolver One brings a better (and more Pythonic) programming model to creating spreadsheets and spreadsheet systems.
Resolver One 1.4 was recently released. The major new features are that Resolver One is now built on IronPython 2, Numpy integration, model side scripting and a bunch more spreadsheet functions. You can read all about it, along with the latest winner of the Resolver Spreadsheet Challenge which integrates the R Statistical Programming Language with the Resolver One spreadsheet UI. You can read all about it in my blog post:
Resolver Exchange showing you how to get the most from Resolver One. Here are some of the latest:
A simple demo of the Resolver One Numpy integration that approximates Pi. (We missed Pi day for this one - shame.) You'll need to read our docs on Numpy integration to use it. If you're running 64 bit Windows then this may be of interest too.
Using Numpy inside the spreadsheet grid (even with arrays holding a million numbers) totally rocks. See this short screencast for a demo. Mad props to William Reade and his work on Ironclad that makes it possible.
Using the new Formula property on cells to import CSV files into Resolver One.
Part of what makes Resolver One unique is that every spreadsheet is an IronPython program - with your own code in as well (the Dreamweaver of spreadsheets is one way it has been described). The new RunWorkbook function allows you to integrate spreadsheets together, but can also be used directly from IronPython (without the UI) allowing you to use the Resolver One calculation engine from Python or .NET programs. This demo / library shows you how.
One possible use case for the IronPython integration is to unit test your spreadsheets - or even use TDD (Test Driven Development) to create them! This is an example of testing a spreadsheet from the Python standard library test framework unittest. This would actually be fantastic to bring to the mainstream spreadsheet world and I intend to write an article to go with the demo soon.
An example of integration between Resolver One and the Frontline Systems .NET optimisation libray, using their platform SDK. Also a good example if you are interested in using this library from IronPython. Combining Solver libraries with traditional spreadsheets with Excel is pretty common, so nice to see that you can also do it with Resolver One.Even without the special offer, you can get a free 31 day trial of Resolver One, and if you are sharing the spreadsheets you create or using it within an Open Source project then you can request a free license.