Here's where I'm at on templates. Feel free to critique.
Goals (in order of importance):
1. Get data from an object model
2. Minimize or eliminate programmatic logic inside the template
3. Make as simple to read/write templates as possible
4. Give feedback on all possible errors
5. Make the data
Roy G. Biv wrote:
Here's where I'm at on templates. Feel free to critique.
Goals (in order of importance):
1. Get data from an object model
2. Minimize or eliminate programmatic logic inside the template
3. Make as simple to read/write templates as possible
4. Give feedback on all possible errors
Thank you for the reply. I realize that I'm trying your patience. I
appreciate you bearing with me.
Daniel Fagerstrom wrote:
Roy G. Biv wrote:
Goals (in order of importance):
1. Get data from an object model
2. Minimize or eliminate programmatic logic inside the template
3. Make as simple to
Roy G. Biv wrote:
Here's where I'm at on templates. Feel free to critique.
[snip]
I have to admit there is interesting value in your everything is a
transformer position. There are two things I dislike:
1) your pipelines are big and complex
beans
|
Stefano Mazzocchi wrote:
2) at the end, the template is not a file, but the result of a
pipeline fragment. In short, the template that DW designers will have
to use is a pipeline view, not a file on a disk.
How so? The preliminary step(s) before data injection include such
items as macros
