A few nice to have feature requests: 1. Feature to save templates in Pro project, so we can save the the templates and related files at work in the project and go back home and be able to re-save and work with them without having to copy and paste the files manually would be helpful. 2. It appears like we need to close Template Studio so the Pro Gui picks up the changes for Generating. It would be nice if this can be fixed. 3. Editing the tasks in xml file is not hard but error prone and time consuming, an additional screen/tab to edit tasks would be nice to have. Thanks

npathuru wrote:

A few nice to have feature requests: 1. Feature to save templates in Pro project, so we can save the the templates and related files at work in the project and go back home and be able to re-save and work with them without having to copy and paste the files manually would be helpful.

Do you think that's really useful? I mean: the templates in the system are for general purpose and project specific templates should be saved with the project file, as part of the complete project (as are docs, designs, code etc.). Storing them inside the .lgp file is IMHO not wise as you then lose the ability to alter a normal text file.

1. It appears like we need to close Template Studio so the Pro Gui picks up the changes for Generating. It would be nice if this can be fixed.

Are the files locked? Because llblgen pro's designer re-loads the templates when you open the generator configuration dialog (by pressing F7), so this should pick up template changes.

1. Editing the tasks in xml file is not hard but error prone and time consuming, an additional screen/tab to edit tasks would be nice to have. Thanks

We provide a .xsd to help with that. Please check the xsd folder in the tasks folder and load the one for tasks into vs.net 2005 and then the tasks file you want to edit. You'll then have intellisense in the XML.

The system is designed to not have to add your own tasks: you can also add a base task to the run queue and set the parameters in the generator configuration dialog and save the settings into the preset.

Hi Frans,

on ur response to point 3, when using ur generic tasks like ConsumeLptTemplate the designer really suffers from not being able to put some kind of sensible name on the task in the preset (v2.0). They appear as "SD.Tasks.Base.ConsumeLptTemplate" (for example) and I can only guess their purpose by looking at the parameter values. I know I can go in and create a new task with a nice name but that, at least partially, defeats the purpose of having a generic task in the first place.

The taskPreset element in the preset file has a name attribute which appears to be used to match up against a task element in a tasks file in the current scope. taskPreset needs another attribute, like "label" or something that can be edited from within the preset designer. (I'm a big fan of clicking on something, and being able to hit F2 to rename it).

Also let us select multiple taskPreset nodes in the tree at once and delete/disable/enable them at once.

worldspawn wrote:

Hi Frans,

on ur response to point 3, when using ur generic tasks like ConsumeLptTemplate the designer really suffers from not being able to put some kind of sensible name on the task in the preset (v2.0). They appear as "SD.Tasks.Base.ConsumeLptTemplate" (for example) and I can only guess their purpose by looking at the parameter values. I know I can go in and create a new task with a nice name but that, at least partially, defeats the purpose of having a generic task in the first place.

That's changed in v2.5 There you can specify a display name in the preset for tasks and taskgroups

The taskPreset element in the preset file has a name attribute which appears to be used to match up against a task element in a tasks file in the current scope. taskPreset needs another attribute, like "label" or something that can be edited from within the preset designer. (I'm a big fan of clicking on something, and being able to hit F2 to rename it).

Also let us select multiple taskPreset nodes in the tree at once and delete/disable/enable them at once.

multi-select isn't possible with the .NET treeview, so I can't do that unfortunately.