Apache License

Releases are only availlable for registered OpenNTF users. Login or Register to: get access to all OpenNTF project releases participate in the Mainbar participate in OpenNTF projects or start your own

This release:	55
All releases:	13487

Release Info

Release Name	v0.1a (pre-release)
Build Number	(used by version checker)
Released On	01/23/2004
Released By	Jerry Malsam
Released for ND version
Status	Released
Feature Requests addressed	No feature requests addressed in this release
Reported Bugs fixed	No reported bug fixes addressed in this release
Project Category	Software Development Tools, Web Development Tools
Sub Category
Download Classification	Registered User

What's new

- Revised layer names to be more functionally descriptive -- updated divBody, divRow, etc. to more layerViewBody, layerViewEntry, etc. - Added .CSS stylesheet with all class and element names for easier CSS development - Automatically switches between .js files depending on server version to ensure correct XML element & attribute names (different in r5 vs. r6) - Automatically determines whether "Show selection margin" is checked and renders selection margin accordingly - Hidden Option fields in $$ViewTemplateDefault set how many docs to retrieve, what style to render view as (tables vs. layers), and whether to run in "debug" mode

Minimum Reqirements

- MSIE5.5+ (maybe less? -- need to do platform testing) - Um... javascript - No client-side XML control (MSXML) nor java VM required

Known issues

- Rendered view is still very basic (just proof of concept) and doesn't yet interpret attributes of the viewdesign object - Writing the rendered view to a div.innerHTML has limitations (ex: browser Back button doesn't work properly); considering using iFrames instead, but that would make it more platform (MSIE) dependent - Some Domino view design attributes are not listed in the ?ViewDesign XML, so we'll need some other way to specify them (CSS? .js header? subform?) Also, more design attributes are available for r6 than for r5. - Need a better name than jsviews.nsf, as database will also replace outlines - Have one report that the XML from the ?ReadDesign and ?ReadViewEntries URL commands may render differently in r5.0.5 vs. other r5 versions -- need to confirm and/or find a good workaround - Code is believed to only work with MSIE, as the IE:Download object is used for loading XML. A more generic approach would make this available to more platforms. (Any suggestions?)