All
All
Projects
Snippets
Go
Explore
Home
About
Get Involved
IP
Legal
Interact With Us
Blog
Webinars
Discord
Twitter
YouTube
Facebook
OpenNTF GitHub
OpenNTF Connections GitHub
IBM Connections Downloads
DominoHelp (external)
Explore
Home
About
Get Involved
IP
Legal
Interact With Us
Blog
Webinars
Resources
Discord
Twitter
YouTube
Facebook
OpenNTF GitHub
OpenNTF Connections GitHub
IBM Connections Downloads
DominoHelp (external)
Resources
Discord
Twitter
YouTube
Facebook
OpenNTF GitHub
OpenNTF Connections GitHub
IBM Connections Downloads
DominoHelp (external)
Projects
Snippets
Collaboration Today
Sign In
Username
Password
Forgotten your login credentials?
Login
Register
All
All
Projects
Snippets
Go
LotusScript to manipulate XPages and other file-based Elements
Posted by
Andre Guirard
on
March 29, 2010
I've recently updated my collection of fancy LotusScript libraries (
see here
) with a new tool for reading the contents of file-based design elements, such as image resources, stylesheets, XPages and Composite Applications -- anything that has a $FileData item in the design note. This lets you, for instance, read the XML source out of an XPage, manipulate it, and put it back with changes. Because there's not yet a "descriptive" DXL notation for some of these design elements, the code contains logic to read the CD records in the binary data and extract out just the file data. Domino Designer plugins can access design element contents by using the Eclipse IFile interface, but there was not previously a way to do this in agents and client applications.
This release of the toolkit also includes an updated version of the StringDiff tool for finding the differences between two pieces of text; the new version lets you optionally enable "moved block" detection, so you can tell which parts of the text are new content vs. just having been moved around. This could, for instance, be used for assigning partial author credit on blog entries by comparing versions to see how much text the latest author added.
Please enable JavaScript to view the
comments powered by Disqus.
comments powered by
Disqus