Quick Elementer 2.0
Updated version of Quick Elementer is now available.
Quick Elementer can now copy documents and have dependancies on other Quick Elementers in addition to Quick Elementer 1.1 features- copy elements and inherit elements on the same document. Each component that can make up a Quick Elementer will be displayed on a tab.
The Quick Elementer form
Inherit design Tab
Each of the design elements in the inherit list will have the design element's 'Master Template' field set to the master template name of the current database after it is copied to the destination database. You can sort the design elements base on the type of design or the design element name for each of the lists. There is also an option to limit the available design elements by type.
Copy design Tab
The copy is very similar to the Inherit tab, but when copied to the destination database the 'Master Template' field will not be set. You can sort the design elements base on the type of design or the design element name for each of the lists. There is also an option to limit the available design elements by type.
Elementer Dependancy Tab
Dependancies will reduced the number of design elements that need to be selected for each Quick Elementer. When implementing a Quick Elementer all elementer dependancies will also be implemented. Use the 'Select Elementer Dependancy' option to select Quick Elementers form the Quick Elementer view. 
Documnets Tab
Any document should be allowed to be copied not just Quick Elementers so the selecting of documents will be generic. The first step is to select the view that contains the document that needs to be copied. The second step is to select 'Select Documents'. Then Quick Elementer will prompt for which field should be used to describe the document. The view and the document unique ID will also be appended to the document description.
The Quick Elementer view
The view lists the design elements that are apart of the module following the following codes:
- I - Inherit design
- C- Copy design
- E- Elementer dependancy
- D- Documents
The 'Copy Elementer to Database' will prompt for a destination database and will implement the Quick Elementer as defined along with all dependancies.
Copy Elementer to Database
When the Quick Elementer has been implemented to the destination database Quick Elementer will ask if the destination database should be opened.
May 31st, 2005 - 07:23
Chad,
Handling elements within elements was my first wish while examining QE v1.1. I appreciate you added it.
My understanding is QE can be plugged within any templates/databases in order to enable design notes xfer. I think QE form should prompt for a source database instead, and design notes copy be enabled against a set of elements (i.e. UML components). Thus QE would behave more like an assembler (QA maybe
)
Can I suggest QE handles profile documents too and emcompasses platforms dependancies?
Cordially
Alain Romedenne
Ps: Shouldn’t “alias are seperated” be spelt “aliases are separated” instead in your form?
May 31st, 2005 - 20:52
Alain, thanks for the suggestions. I hope that I am not just developing this application for you.
I have a implemented the ability copy profile documents (new tab), but need to do some more testing. I need a little help understanding platform dependancies.
I like your idea of implementing an elementer from a destination database. How about the ability starting from the toolbar or Tools menu bar? Then it would always be available.
Chad
June 1st, 2005 - 01:03
Chad,
While mentioning platform dependancies I meant elements should be tagged as usable on all Notes/Domino supported platforms, or Win32 only, etc..
Similarly elements should be tagged as available on Release 6, Release 5 etc.. e.g. “Quick Elementer” library operates from R6 onwards..
I have the feeling your LS classes would benefit from using the “Composite” design pattern, any feeling about that?
Cordially
Alain