From here you can get to all of the documentation for Resolver Systems' products.
Contents |
Getting Started
- A good way to get started is the Quick-Start Guide, which is also put onto your Start menu when you install Resolver One.
- There are also step-by-step guides to the Sample Spreadsheets that come with Resolver One.
- ...and a feature-by-feature overview
- Frequently Asked Questions
- Support and Contact Details
Some examples
- The Sample Spreadsheets that are packaged with Resolver One.
- How to do Charting
- How to put Buttons on the grid.
- For the .NET developer - .NET Objects in the Grid
- Loading data from CSV files
- Loading data from a database with Database Worksheets
- Loading data from a database in user code
- Reading from databases to arrays
- Writing to a database
- For hard-core Python users - how to put List Comprehensions in the Grid
- A nifty trick: The Auto-Total
- Extreme Programming Pair Generator
- Our Usage Tracking Spreadsheet, showing getting data from a Web server, charting, and more!
- Caching data between recalculations
- How to get Resolver One working with Google Spreadsheets
- Loading data into Resolver One from Amazon SimpleDB
- How to use CopyRange
Detailed documentation
Some specifics:
- The complete API documentation covering all of the functions available from your formulae and user code.
- Complex numbers
- Header Rows and Columns
- Named Ranges
- Cell validation (for drop-down menus in cells)
- Arrays
Writing your own Python code:
- Tips for Writing User Code
- Python for non-programmers
- Creating a standard location for your own Resolver One functions using IRONPYTHONPATH
Avoiding confusion:
- Differences Between Resolver One's Formula Language and Python Expressions
- Model vs Results
- Identifying Errors
Beyond Resolver One:
- The Resolver One Web Server
- Access to data from Bloomberg from the Resolver One financial Edition.
- Access to data from Thomson from the Resolver One financial Edition.
- The Ironclad project to get Python C extensions working in IronPython.
Comments
If you have comments, questions or suggestions about any of the Resolver One documentation, please post them to the Documentation Suggestions Forum.
This is fantastsch (OK, fantastik in English.) I wish I had this when I was an M&A investment banking analyst on Wall Street decades ago. In fact my boss (who like I was also an engineer) wished we had something like this instead of Lotus 1-2-3. On occasion I had to write C or higher level language programs to meet our requirements which neither a spreadsheet nor the legal language of USA's best law firms could render into an M&A deal contract language that met with our client's conditions (then the biggest computer co. in the world ;-)
--Alif Shirali 06:09, 10 June 2008 (BST)