Jun 26

Would you…


use an alternate editor for auto complete(type ahead)?  I have not been doing much development in Domino these days, but I have been developing in other editors that support auto complete.  You could say that I have been spoiled, but I look at it as a necessity for todays development.

When developing in OO there are some many classes each having its own list of methods and properties.  The auto complete is just required.  What can make things even more challenging is how frequently the classes are being used.  

Since Domino Designer only supports native objects for auto complete I had to start looking other places for my dependancy.  Yes, I do use ScriptBrowser which is great for quick reference, but for developing a new class the auto complete is required.  The only other option was LotusScript Editor for Eclipse , but once again there was an browser but no auto complete.  Took a look at other editors like NotePad++ and TextPad but once again no auto complete.  

The next option was to see if VB6 could handle what I need because it has similar syntax as LotusScript.  Yes it is closer to LotusScript but that is also its drawback.  The UI did not give me enough control over organizing my classes.

The last options was to use Visual Studio and VB.NET, this seems to be the best fit.  There are two issues that I am working threw: no LotusScript functions like, StrCompare, StrRight, ArrayGetIndex and class properties.  I am not looking to run LotusScript through Visual Studio, but to create the initial shell of methods and classes.  Yes, this might come back to hurt me but for now I need the auto complete.

Has anyone else consider this and done any research?
Jan 27

Open Audit 1.2.1

A bug fix and some minor improvements, and an additional request for Open Audit.
Version 1.2.1:
A minor fix for the authors fields on audit logs, the field was being set as a readers field instead of authors.  Added some more methods to access reader and author fields on audit logs.  Updated the hide whens of action buttons so they are not visible if the ‘form’ field is not set.
New Features:
  • Updated hide when of action buttons to only show when the form field is set
  • Updated Using this Database to specify steps to implement Open Audit
  • Addd some new Reader and Author methods to OpenAuditLog class.
Bugs Fixed:
  • Authors fields for logs was actually set as reader access, run ‘(1.2.1 – Fix Authors fields on audit logs)’ agent in any database that has audit logs to fix the problem.  This bug was introduced in 1.2.0 and only needs to be ran if logs where created with author fields.
Not Implemented:
  • Java audit class
  • Deleted documents – option to delete audit logs when document is deleted
  • Archived documents – option to move audit logs to a archived audit database when the document is archived
  • Ability to Roll back a document using the audit log to determine the values of the fields
  • Audit access of documents