• Anonymous
  • Login
  • Register



JSON LS

Owners Alan Faubel Project Creation Oct 16, 2006
Contributors - Last Release Oct 16, 2006
Downloads 1890Download latest release
Rating
(1 ratings)
Description LotusScript tool to parse and create JSON


This isn't really an application; it's just a couple of LotusScript classes to provide a LotusScript implementation for creating and processing JSON (http://www.json.org). (I think it was the only language not on the list).



I first used JSON with a Flash/Zinc application to pass arrays of objects between movies. The only way I could find to do this was via a String and since ActionScript is very similar to JS, this turned out to be a great solution.

After using JSON with ActionScript and reading Jake's article "XML is Dead. Long Live JSON" (http://www.codestore.net/store.nsf/unid/BLOG-20060612?OpenDocument), I thought it would be useful to write an implementation for LotusScript. Since then I've used it for creating and processing JSON sent to and from LotusScript agents and the browser via Ajax calls.

NON AJAX EXAMPLE

More recently I had a requirement to have a multi-row table in a web form that users can add and remove items from. The users also wanted to report on this information every year. Initially I thought I would do this with some Ajax and a Document / Response arrangement where each row of the table would be stored on the server as a response. I finally decided to use JSON to store the row information in a multi-value field on the document. When displayed on the web, JS converts the JSON strings to objects and then builds the table on the fly. When it comes to reporting I use these LotusScript classes to build objects from the JSON, sort and walk through them to produce the reports. The advantage with this approach is that the UI is fast, with no need to make server calls and I didn't have to write code to maintain relationship integrity. The disadvantage is that the report creation process is slower, but since it is only an annual task, that was not such a problem.


Projects can have short and readable URLs, e.g. http://mobilecontrols.openntf.org.

You can request a short URL to your project by sending a mail to support at openntf dot org.
Owners are the people with maximal rights. For example they can create releases and add more contributors.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter the contributors or owners here who you want to receive notifications and questions by email.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
In addition to the owners additional OpenNTF contributors have to be listed here. Contributors don't have the same access rights as owners, e.g. they cannot create releases.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter a short description of the project here (up to 100 characters).

The short description shows up in the project UI and in some of the views.
In this field you should enter a more detailed description of your project.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.
A Catalog Release is for projects that are production ready and that are end-user "install friendly".

This property describes whether any release of this project has been added to the catalog.

Learn more about the catalog.
GitHub can be used as source control repository for OpenNTF projects. In this case the Issues from GitHub are used instead of the Defects from OpenNTF.

Contact ip-manager@openntf if you want to have a GitHub project created in the OpenNTF space.

Learn more about OpenNTF on GitHub