• Anonymous
  • Login
  • Register



RVEX

Owners Rob Pinion Category
Web Development Tools
Contributors - Platform
R 8.5.2
Downloads 356Download latest release Last Release Nov 6, 2007
Rating
(0 ratings)
 Project Creation Sep 27, 2007
Status Not active Short URL Not defined
Description Ouput nested XML or JSON from Notes views In Catalog
No


RVEX uses a single agent that you copy into any existing database to ouput properly-nested XML or JSON from your Notes views on the web. You can use the exported data as the source for AJAX / Web 2.0 systems, such as the data source for an XMLHttpRequest object.

While the ?readviewentries URL action provides an XML or JSON representation of a view, the values are unnested and are sometimes unusable without an XSL transformation. Developers usually bypass ?readviewentries and create an agent that properly nests views as XML or put XML tags around view column data. This works for simple views only, but fails when nesting categorized view data.

The goal of RVEX (pronounced AR-VEX) is to create an agent that will export a properly-nested XML representation of a view. The agent can then be included in any application without further modification.

For the base output, you simply call the agent and specify the view name.
Example: rvex.nsf/rvex?openagent&viewname=colors

The output of the agent is highly customizable through additional URL parameters. Parameters determine, for example, whether the column values should be presented as CDATA and if the results should be transformed with XSL or CSS. The "cat" parameter works like RestrictToCategory view command to return a single category from the view.

JSON output was added in release .92 and improved in release .93. You specify viewtype=102 in your URL.

JSON currently works for only the most simple views. Additional JSON output for more elaborate views will be forthcoming.

The name is derived as follows:
RVEX = ReadViewEntries - XML

Contributions and testers are most welcome!


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. Put the word 'OpenNTF' somewhere in the subject.
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.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
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.