|Professional Services||Second Signal||Presentations||Andrew's Blog||Support|
I've spoken about Code Templates before, and how I think they're one of the best new features in Designer. Now I want to suggest a next step. I want to be able to define a different subset of code templates for different kind of agents. In other words when I create a new agent, I'd like the option to select what kind of agent it is and have different (or additional) template code dropped in.
For me, the biggest key would be for what I'd call "Web Action Agents" I would include some standard code I use to parse the document context and url parameters, grab the current userid or other session information, and potentially include a specific script library I use for those kinds of agents. There are some very different sets of standard code I use when dealing with agents that are triggered on different kinds of events as well. Agents that handle unprocessed documents, agents that run on a time schedule, and other factors all determine which base set of code I want to include.
Another critical classification for me, might be the project or client set the database falls into. That one is critical for error handling routines. At some clients I have built in error REPORTING as well as handling, but of course it goes to different places. The same kinds of features probably apply to other design elements -- forms and views, but more importantly Xpages. The idea of create my new design element based on "THIS" predefined template would be very powerful indeed. How often do we "copy/paste" an element then change its name and remove the "functional" code to begin work on some new feature?
Microsoft has done this for years in Visual Studio, with project types. Eclipse also has this feature when you're writing in Java using the "standard" Eclipse client.
Please wait while your document is saved.