I have been hard at work on version 2 of LotusScript.doc and I’m getting very close to a beta candidate. My main issue is that I keep adding features instead of finishing the core product as I now have a framework that is far more extensible than the version 1 code.
I’m currently finishing the framed HTML output that also shipped with version 1 and in that regard I have a question for LotusScript.doc users. Which parts of the HTML output do you actually use? In version 1 you could select to include the follow design element types and have output about these output to the documentation:
- Script libraries
- Database script
- Shared actions
Which parts do you actually use? Is there a better way to do it? Any parts that should highlighted differently?
Based on prior and recent recommendations I have set up a Paypal account to accept donations to finance the development of the free version of LotusScript.doc version 2. All donations will be very much appreciated and help me justify the time I put into this.
The following is a technote was sent to me from a LotusScript.doc user: LotusScript and Java code hangs Notes when exporting certain documents to .dxl/.xml. Only difference was that his client redboxed.
Anyways – upgrading to Notes 6.5.6 solved the issue.
…I have been hard at work and I’m getting close to a pre-release of LotusScript.doc v.2.
LotusScript.doc v. 2 is being completely rewritten from scratch (in Java), supports multi-threading and handles a wide array of new design elements compared to the 1.0.x code stream. The code and comment parsing is done and I’m currently working some of the more esoteric parsing bugs out.
One of the design goals for version 2 is also adding support for other output formats than the “traditional” framed HTML view. Writing custom output formats will also be possible using a template engine. I’m planning to ship the following documentation formats:
- Traditional framed HTML
- A more comprehensive HTML report
The main XML format is almost done and it’s what I wanted to show of today and is what I’m showing above. Click the image (or here) for a larger version. The larger XML snippet shows:
- Ability to see which subforms are used from which forms
- Ability to see which embedded views are used from which forms/pages and what their singlecategory formula is (if any)
- Support for buttons (anonymous and named)
- Support for actions (in action bar and as shared actions)
- Ability to see which shared actions are used from which action bars
- Support for subforms
The list of new features is quite a lot longer including vast performance improvements but lets not get carried away. Of cause the XML format will also carry the code comments.
I’m starting to think of features and improvements for LotusScript.doc version 2 and was thinking what you had to say… What issues/problems do you have? What kind of features are you lacking? Please let me know so I might include them.
Please send comments and suggestions by e-mail to lekkim [at] lsdoc.org or as comments to this post.
Apart from being told that the DXL implementation in Notes/Domino 8 will be able to surface the source code and WSDL from web services the session was below my expectations.
The fact that the source code of web services will be surfaced will make LotusScript.doc able to pick it up which is nice since I’ve had problems with this in the past (Domino 7 web services woes). I talked to the developers about this last year and it appears I’ve been heard. Thank you for that!