I would like to suggest adding a view to DDE in which I can see a list of all design elements. This view should be sortable by Name, alias, date created, and date last modified. This would allow me to:-
An All Design Elements view would assist in:
1. Sorting by Last Modified
2. Sorting by template inheritence / other design element properties
3. Deleting / copying ALL design elements from one database to another
Allow the actionbar to be displayed even if there's no buttons in it. This will allow for consistent UI's and branding without having to fudge the solution with an empty action just to display the bar
Allow a developer to select a folder as a data source in the view control in XPages designer. Currently only allows views, but folders can be manually selected in the source code editor.
Redundant design elements often sit around for the life of an application since it's difficult to be certain that a design element is no longer used.
It would be extremely useful to have a tool or special design view showing reference elements that are not referenced anywhere (eg subforms, ...
Suggestions to improve the Search from the Designer Search menu:
1. When you create a design appears a dialogue with the three fields: Name, Alias, Comment. When renaming - a dialogue with one field: Name. Please do that flew dialogue similar creation.
2. In the right window (in the list of elements) in the context menu to add an ...
Include a dojoType property box in the "All Properties" of a form control like EditBox, ComboBox, Button, etc. This would allow making a form element a dijit.form element declartively instead of having to write a script to add (dojo.behavior.add) to select elements.
.. extends NotesDocument (I suppose). Would allow access to 'prohibit design/refresh' flag, Template inheritence and other options.
I know some of this stuff can be done using tricks, but I think it's worth formalising the class.
I propose to add this possibility for element "Database Script" (tick "Prohibit design refresh or replace to modify"), as well as the full inheritance of "Shared Actions" ( Link ).
In the design client, when working on a view, allow the document properties box to work on documents in the view -would be incredibley helpful to check a doc when writing a complex selection statement, for example
Why are Shared Actions not in the category Shared Elements of the designer outline?
This might sound like a slightly off-beat idea, however I wonder how many coders would find it useful to be able to trigger a script whenever a design element is updated in designer.
In my case, I'd like to trigger a a design 'push' because I have engineered my ...
Script libraries, computed text, selection context, xPages, events, session scope, etc. One language to rule them all.
And please let it be a proper object orientated language.
At present this is not possible, I propose to add it. In systems with a hierarchical structure ptemplates it will be useful, since it eliminates the multiple copy-paste, and make it easier update the changes in the code.
The same may apply to a Shared Actions.