evaluate templating

Posts   
 
    
pdegoede2
User
Posts: 9
Joined: 28-Sep-2005
# Posted on: 01-Oct-2005 08:22:36   

Hi,

I'm trying to evaluate gen pro however am hitting a wall with the templating provided.

The TDL isn't rich enough. I'm trying to auto-generate UI based off the schema.

There are articles regarding .net templates and there is an engine to emit code for that but I can't seem to access it via the demo version.

Is this expected behaviour? Is there a way I can get an idea of the power of this templating with the demo version?

Thanks Paul

Aglaia avatar
Aglaia
LLBLGen Pro Team
Posts: 535
Joined: 07-Sep-2003
# Posted on: 02-Oct-2005 10:44:28   

Hi Paul,

I'm afraid Template Studio is only available for licensed users.

Aglaia

MacDennis avatar
MacDennis
User
Posts: 50
Joined: 03-May-2005
# Posted on: 02-Oct-2005 13:57:51   

Paul,

So called lpt templates might be what you're looking for. From the SDK manual:

".lpt templates are templates written in VB.NET or C# which are parsed and executed by the DotNetTemplateEngine task performer and which result in whatever output is formulated in the templates. As with TDL templates, Lpt (LLBLGen Pro Template) templates are also defined in template sets. For now, these template set config files have to be stored in the drivers<driver of choice>\templates folder. TDL is the language of choice for the templates which are used to generate the code build on top of the LLBLGen Pro runtime libraries, but .lpt templates are preferred when it it comes to code generation which requires access to the complete project contents and for code generation tasks for which TDL is too limited. TDL though is powerful with its simplicity: a single statement can represent a lot of logic, logic which would otherwise require a lot of code inside the templates. So if you want fine-grained control, .lpt templates are for you, but at the same time it might require more code to write inside the templates and because of the lower-levelness of the template logic, it might also result in more time being spend on debugging the templates. A facility is build in the DotNetTemplateEngine to make debugging easy. "

You could also opt for writing your own plugins or taskperformers.