|
|
The style section is relatively less used but takes much space in the properties panel, especially inconvenient on small screens like my laptop. If you want to edit the more useful section e.g. Resources, All properties, you have to scroll down. Collapse the style section by default, please.
|
|
|
calDAV and cardDAV are open standards for access to calendar & contacts, and IBM is all about open standards!
We already have support for iCal, vCard, and webDAV in Domino... please stitch them together to provide calDAV & cardDAV support.
|
|
|
Just very hard to read all the properties without scrolling. copying them to compare them is even more difficult. A simple 'copy properties to clipboard' would be an improvement.
|
|
|
It would be nice if there could be some type of indication on the field, like there is for Authors/Readers, when you have the field, on standard forms, as computed, computed for display, or computed when composed and on xpages as Visible/Not Visible, Read Only/Not Read Only, and Disabled/Not Disabled.
Of
|
|
|
The xPages team was extremely thoughtful in designing of the developers capabilities, but one capability I just needed which wasn't available was having the 'Computed Property Menu Button' on the Display tab for a viewpanel column. Specifically the checkbox to 'Show values in this column as links'.
This would be helpful because
|
|
|
The "floating" properties is quiet annoying because you have to move it around the design area when it is on top of items.
For traditional Notes design elements (Forms, Views) it would be more handier to have the properties box appear in the Outline panel, simply because that panel is not
|
|
|
with a simple copy and paste (in a rich text field) you can easily see all the properties, instead of having to go through the 7 individual tabs.
|
|
|
The only FTI properties of notesDatabase exposed to LotusScript are .FTIndexFrequency, .IsFTIndexed, .IsMultiDbSearch and .LastFTIndexed.
The methods, CreateFTIndex(), RemoveFTIndex() and UpdateFTIndex() also exist.
Yet the Notes Client UI shows Count unindexed documents, Size, and the FTI settings for Case sensitivity, index breaks, index attachments and index encrypted fields.
Why are there not
|
|
|
When you want to replace an inline image (imported image) you basically have to delete the current image and replace it by importing a brnad new image.
This causes you to loose all the properties set.
In case you could from the image properties - first tab - select a new 'source'
|
|
|
Custom controls now support a wide range of property types but they do not appear to recognize NotesXspViewEntry as a valid property type. This would be especially useful for the Repeat control where you wish to output category entries as well as document entries found in a view.
Note: It does
|
|
|
I have a properties window pointing at the Form properties of an opened form. When I switch to another (opened) form the properties window will no longer show the Form properties, but switches to a Text properties window.
Why can't the former selection not be kept? I see no reason for
|
|
|
A great time saver would be to be able to copy all style settings for text, tables, hotspots and paste them somewhere else.
|
|
|
There is no way to copy the replica ID from the Database properties dialog. So the only way to save that information to use somewhere else is to take a screenshot, paste it somewhere else, like Paint where you can read it from and type in where you need it.
|
|
|
In the current Text Properties toolbar, there is no button to select text color. If you want to change the color, you have to display the Text Properties dialog first or use the Text\Color menu. It's rather inconvenient and I cannot figue out why Lotus doesn't provide that obviously useful
|
|
|
I would like an 'AllDocuments' property that would return all documents in the NotesView. This would work in a similar way to the "AllEntries" property for the NotesViewEntryCollection.
So you would be able to code:
Set view=db.getView("MyView")
Set col=view.AllDocuments
etc.
|
|
|
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.
|
|
|
A database property where we can specify a logical name for the database where the Domino web server will use that to generate URL using the logical name instead of using the file path name.
Example: A database under Domino data root \folder01\folder02\filename will generate a url hostname\folder01\folder02\filename
Instead we specify a
|
|
|
Make available an option to never save a form on the form properties so that whether the form is closed via a button or the ' X ' for the database tab you don't have to worry about coming up with some ingeniuos programming to prevent the user from being
|
|
|
Give us a property to specify any http header and value ("expires" for instance) for the Domino server to append to the http response. Make this property available in every design element.
@SetHTTPHeader only really works in the context of forms and pages.
I know this can be done using site rules
|
|
|
The Field class in LotusScript only contains events. It would be great if it contained properties like Value (read/write) to make it easier to manipulate in the events. For example, if I want to handle the OnChange event in the client, I can use LotusScript but I have to write a
|