Even having a rough way to do this in Midas, I would really like to see a simple @formula (and matching LotusScript) method for determining if there was anything in the rich text. Even better would be if it took an argument that specified whether whitespace was included, so you ...
I wish we have a programming API to access and edit the mail database, the
personal address book and the Domino Directory
The API must support LotusScript and Java.
It is not professional to create a document with field and than find ...
The Document/NotesDocument classes currently allow read access to things like creation date, last modified, etc.
However, there are a lot more properties to documents than that (when created in the current file to name one).
These should be made available as properties like the others.
I've seen a LOT of workflow processing agents in Notes. And the one thing they all have in common is that they have to waken up at a regular interval, check all pending documents, and move around document status.
What any workflow system needs is the ability to ...
Most developers are used to Lotus-Script. They would not have much of a problem to write scripts in Java. The general syntax can be learned in a few hours and the main knowledge lies actually in the object-modell of the Notes-Classes, which are identical to LotusScript. However what ...
Make file (and other) resources' data available programatically. I can currently grab a resource design doc using a NotesNoteCollection and find what I'm looking for by searching for the $Title that I need, but if the resource is -say- a file I can't get the file data in any simple manner using LS ...
To unify the use of code and design elements (Subform) is sometimes useful to know we are in dialogue or not. Example: Subform used as embedded (checking for filling in the fields needed on QuerySave) and as a dialogue (on QueryClose). I propose to add a property IsDialog as Boolean ...
There should be no need calling recycle() on Domino Java objects. Java has a garbage collector and for almost every other Java API there is no need for doing this kind of memory clean-up.
The knowledge and documentation of how the use the recycle() (and if you need to ...
Generation of this error is useless, it only hinders. Quite enough to return Nothing.
Similar GetDocumentByID method does not generate errors.
I would very much like to see some new Classes or API's if you like, that makes it easier to create Appointments, Memo's and other Mail/Calendar entries, without having to remember all the speciel fields, that have to be set. Then we could create AppointMent and memos as objects and ...
In Designer 8.5.1 I've added the Tasks window to the Domino perspective (Window>Show Eclipse Views>Other>General>Tasks), which will list the stuff I've still got left to do when writing Java, if I add "// TODO...etc" comment lines in my code, which is great. It would be lovely to have this feature ...
Add the NotesUI classes like NotesUIDocument, NotesUIWorkspace etc. to the Java Notes-API.
A lot of notes developers who want to start java development on their prefered platform are scared away by the well known recycle() and error-cleaning-up-agent-threads issue. For those with a bit more experience with and confidence in java, this is not so much of an issue. At least that has ...
With notesDxlImporter we can insert code in for example database scripts. In the process the compiler tries to automatically compile this fresh code. Unfortuatedly I get no information about if the code actually did compile or did not due to errors in the inserted code in the new environment like ...
I think the web service support in Lotus should be modernized and support the JAX-WS (JSR 224), which is the standard web service API in Java from Java version 6.
As far as I know, the built-in web service support in Domino 8.x is based on the ...
Propose to add type RTELEM_TYPE_PICTURE into NotesRichTextNavigator.FindFirstElement, etc.
The Domino Object Model classes for Java that deal with multi-value items use the java.util.Vector class for item values. For example, see the lotus.domino.Item.setValues(Vector) method. That was a good design back when those classes were first created for Java 1.1. But since Java 1.2 the recommended best practice ...
Good idea, but there are some disadvantages in its use. I propose:
Generation of this error is useless, it also hinders. All error handling should be done in the proper place - on QuerySave.
I propose that the Save method returns the result as Boolean, it's would be very convenient and usefull.