Printing has long been a huge weak point for Notes. It would be really great if we could have a parameter for the print method that would allow us to control whether a document should be printed in portrait or landscape.
Allow selecting a number of fields and then allow editing all those properties that can be common to all those fields together. Some properties I would like to be able to set on multiple fields will include style properties, formatting, multi-value handling, etc...
For action buttons and menu items, include a "Disable-when" formula that would work similar to the "Hide-when" formula for these controls. The difference being that the "Disable-when" formula would display a grayed-out, disabled control when the formula evaluates to true. In most cases, if you don't want a user to ...
This method might also have parameters to specify which columns to copy and whether to include column headers.
When I dynamically generate HTML I would like to be able to import it directly from the memory buffer where I created it such as a string variable or a NotesStream, etc. I see no need for me to have to create a temporary file to do that.
An indicator on the tab to know if an open design element has been saved or not would be very helpful.
This is response to Ben Langhinrichics' request for book proposals.
This book discusses real world scenarios for XPage application. It provides examples & tips on how to build attractive interfaces for your Domino applications using IBM Lotus User Interface.
If you happen to have questions when to ...
A lot of websites have a menubar/actionbar below the banner/logo/title. This gives the user a better experience, and looks nicer too. Notes currently has the actionbar always at the top.
I propose to have a setting in the actionbar to define/compute an optional subform to put above the actionbar.
Not being able to use the enter key slows down data entry, especially when entering a series of numbers from the keypad.
It is accepted keyboard practice with most other PC applications and it would reduce user antagonism when using data entry forms.
The standard RGB color picker is just not enough for real application development. It would be better if the color schemes for an application can be stored in the application itself. Then, when developing, the stored colors in the database are the ones that can be picked easily (not the ...
I can't think of how many times I would have appreciated being able to get a handle on another document open in the UI. Ideally, the NotesUIWorkspace should return handles on whatever is open in the UI, whether its a database, view or a document.
This method would fire for each key entered while in a text or numeric field. The method would have the key pressed as a parameter, and parameters for shift,control and alt keys. The method would return the key pressed by default.
This would allow the developer to mask/modify/format during data ...
You can set the width of a combox but the dropdown is limited to 5 entries; it would be nice if you could set this to another value: 10, 15, 20 etc
I would like to see a few colour schemes that can be applied with a click of a button to a form, view, or a whole app. These would have to be designed by some graphics pro so that they are aesthetically pleasing and follow the usability rules.
Create a software/Designer component that allows you to create custom themes.
Using a graphical user interface should be possible to define the positions of the various components(Banner, TitleBar, Main, Content) and ...
It would be nice to use quick keys to convert a selection to "Pass Through HTML".
I am thinking of your stock standard grid view control/widget. In Notes this design element could be used for displaying and editing multiple documents. So instead of embedding a catgegorized view showing only one of the categories this element could do the same but also allow easy editing of the ...
When viewing the Objects list for a form in designer, instead of just fieldname (Field), tell me what kind of field "(Field)" is.
e.g. (Field - Text)
Suggestions to improve the Search from the Designer Search menu:
When you open a form to create a new document and the form sets some hidden fields up, say to provide values to drop downs, as far as the user is concerned they have not done anything. But if they cancel they will be prompted with save dialogue. It can ...
Did you ever open a document and wonder where a specific field is used? Of course, you can open a form in Designer, but then you don't see the value. So you'll have to go back to the client, look at that spot where you find your field and see ...
This would be an editable field that would not be saved. Essentially it's an area where I can edit some data and then have it parsed or in some way processed but the field itself would not be saved. It would exist only when the document is opened for editing.
It would be useful to have the list of views in the Designer client either display the "Last Indexed" date or the "Last Accessed" date, which are already stored and accessible in the properties, in a column, so that it is easier to determine which views are no longer used and ...