If I write an agent to copy a Java script library into / over an existing one, Domino Designer goes a bit crazy. It complains that anything calling the script library doesn't find it, even after a "Build All".
This kind of copy-design-element is essential when using multiple templates ...
Thanks to XPages, Java development takes a bigger role in Notes dev. However, while an agent, web service and XPage app can all be written in Java, the compilation paths for them are different. An Java agent can use a Java script library but not a Java code or package ...
Notes C API does not fit - do not cross platform.
Server task is not suitable for all, such as transfer design to the local databases.
NB. It would be desirable to have an option (bool paramether) that ignores and deactivates "Prohibit design refresh or replace modify" and "Prapagate ...
The presence of a profile without a key can be verified with getProfileDocCollection.
If the profile with the key, then using getProfileDocument has old and serious problem - profile is stored on disk, that by logic of the application can be very undesirable.
This can be implemented with ...
Work on the interface (XPages) - very good, but would like to not forget about the improvement of Domino API.
I beg to add the ability to search in collection of documents using @formulas, by analogy to Database.search(). The FtSearch method is inconvenient for programming and not as flexible.
Often, for other task, it is necessary to get or set data in the item as an array, for example String. Now you can get the data only as Vector, which is not always convenient, since you have to manually distil data into an array.
Please add the methods for ...
Currently, the method returns all the elements, separated by a semicolon. This can be inconvenient, because the field values may also contain a semicolon.
I propose to add an optional parameter to specify the separator: Item.getText([String sep])
Domino Designer's XPage interface has a masterful way of managing items so I'm not chasing around for the random file in the random directory. I'm heavily indebted to the designers of Designer for this.
The bean & controls file arrangement needs that kind of treatment. I wish all the java, ...
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 ...
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.
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 ...
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 ...
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 ...
Good idea, but there are some disadvantages in its use. I propose:
I propose that it's method returns the result as Boolean, is quite enough. It is better add to Desinner Help describe the situations where the method may return False, and this:
Generating the error ...
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.
Generation of this error is useless, it only hinders. Quite enough to return Nothing.
Similar GetDocumentByID method does not generate errors.