8 sheets tagged with "api":

Cell ranges, offsets and headers

This sample spreadsheet takes a worksheet of transaction data, and summarises and formats it using cell ranges. The user code in this example makes use of several of the features of cell ranges.

The idea of the spreadsheet is that we have a long list of individual transactions (the 'Transactions' worksheet). Each transaction is a trade of shares (either a buy or a sell) for a particular customer. We want to be able to summarise this, so that we can see the total trades for each customer and for each stock.

This spreadsheet is one of the sample spreadsheets that comes with Resolver One.

02 February 2009. Tagged with api, cellranges, headers, offset, sample, user code

Range Slicing

The Resolver One object model uses an API that allow spreadsheet objects to be treated as ordinary Python objects as much as possible - making them natural to work with from user code and even formulae.

Cell ranges can be sliced as if they were collections. You can use numbers and the names of header rows and cols in slices. Unlike worksheets, you can use negative numbers as either the start or end of a slice. Cell range slicing is right-exclusive. It may seem little counter-intuitive, especially when you use names from headers, but it's consistent with Python slicing.

This spreadsheet is one of the sample spreadsheets that comes with Resolver One.

02 February 2009. Tagged with api, cellranges, sample, slicing

Simple functions and formatting

This is the example that is worked through in the Quick Start Guide.

It demonstrates creating a simple Python function in user code and using it from formulas.

It also uses the BackColor property on rows for conditional formatting (BackColor is available on all the spreadsheet objects including cells and cellranges as part of the formatting API).

This spreadsheet is one of the sample spreadsheets that comes with Resolver One.

02 February 2009. Tagged with api, formatting, functions, sample, user code

Worksheet slicing

The Resolver One object model uses an API that allow spreadsheet objects to be treated as ordinary Python objects as much as possible - making them natural to work with from user code and even formulae.

Worksheets can be sliced as if they were collections. You can use numbers and the names of header rows and cols in slices. You cannot use negative numbers as either the start or end of a slice (they don't make sense since worksheets are infinite). In formulae, the colons are replaced by arrows, because colons are already used to specify cell ranges, eg. '=lst[1 -> 4]'. Worksheet slicing is right-exclusive. It may seem little counter-intuitive, especially when you use names from headers, but it's consistent with Python slicing.

This spreadsheet is one of the sample spreadsheets that comes with Resolver One.

02 February 2009. Tagged with api, sample, slicing, worksheets

Resolver One and Frontline Systems Solver SDK

Solver is a .NET-based optimisation library from Frontline Systems. Since it is a .NET library, it is very simple to use from Resolver One. Here are a few sheets translated from the examples that ship with Solver. The numbered examples are taken from the Standard Examples project. You will need to install the Solver Platform SDK which can be downloaded from the Solver website at http://www.solver.com.

05 March 2009. Tagged with api, chart, integration, optimisation

In-cell visualization and graphing using simple ASCII graphs

In-cell visualization and graphing using simple ASCII graphs

Resolver One doesn't support showing images in cells and you need to open new image worksheets in order to see them

but it is sometimes crucial to see data and graph side by side

this is my solution to this problem for stock prices

this code gets live data from Google finance API then visualizes the data using ASCII codes in it's "Graph" column

it is very handy for me and wanted to share it with others

03 April 2009. Tagged with api, competition, csv files, google finance, graphs, stock price, visualization

Generating Sparklines from real time financial information with Resolver one and Google finance API

Generating Sparklines from real time financial information with Resolver one and Google finance API
Sparklines are the greatest inventions of Professor Edward Tufte (statistician and Professor Emeritus of statistics at Yale University), a Sparkline is a proper tool to visualize financial information in a very small space. Sparklines are tiny informative graphs that can be inserted in financial reports.
Sparkline tools are available for MS-Excel. Our code generates sparklines from financial information in Resolver One; these sparklines can then be inserted in-line with texts in financial reports.
In our code, we read Google closing price from an API provided by Google finance, this API provides us with a CSV stream that we can load into Resolver One. We can additionally change the date range for the data stream from within Resolver One.
The code should work right out of the box and there is no need to download any additional package, it calls GDI+ functions and it should be very easy to modify and customize

07 April 2009. Tagged with api, competition, csv, excel, financial information, google finance, sparklines, stock price, visualization

QuantLib Example

This is one of the QuantLib Python examples converted to run in Resolver One. Instead of printing the results like the original example, this sheet puts the results in the grid.

See the notes in the spreadsheet for details about the conversion.

This example assumes that you have a working installation of QuantLib and the C# bindings. If you don't, you can download a binary distribution from the link below.

29 January 2010. Tagged with api, finance, quantlib, sample

<< Resolver Exchange