Data Driven Views
I am always looking for new view technologies. Of special interest to me are what I would refer to as "Data Driven Views". There are 3 aspects to any page.- Structure or Layout
- Style
- Content
Some people might argue that Structure/layout and style are perhaps one and the same. Perhaps, but there are enough differences for me to consider them in their own right.
HTML munged all 3 together, and thus created a mess from which we have ever since been trying to dig ourselves out. CSS tried to extract style out and enable better control and authoring. Support for layout and structure have been improving over time.
It comes down to Who or What controls or generates each aspect of the page. From that standpoint in terms of view/page technologies there seems to exist a continuum from 100% manual on the left to totally machine generated on the right. Typical brochure ware/small website is at left end (manual) of the spectrum. Computer applications push towards the right to varying degrees. Being in this industry, I have an obvious interest in these technologies and am always on the look out for new technologies that push to the right.
A large set of templating technologies (ASP, JSP, XSL...) have been trying to nibble away at this for a long time. Another set of technologies that have been aiding this push to the right have been Content Management Systems. This is an area I will be returning to often.
Data driven views is all about this push to the right. How to enable the the
data being presented to determine all aspects of a page - Structure, Style and
Content. This is one theme I will be repeatedly returning to.
StringTemplate
Some time back I came across StringTemplate and what really caught my attention was that it was created by Terence Parr, who I respect a lot for his contributions to Computer Science. Despite the pedigree, it is still a hidden gem, I wonder why?From what little I have seen here are Pros and Cons of StringTemplate
Pros
- Strictly separates and enforces Model and View
- Small API
- Small language and syntax
- Flexible - can be used to generate pages or code.
- Great support - Terry himself answers a lot of forum posts.
Cons
- Yes, it lacks good documentation.
- Absence of IDE support
- Examples are lacking somewhat.
- Support from major frameworks like Spring are lacking.
- Yet another piece of technology to learn. Adds to the overall complexity of web applications.
I will be kicking the tires of this a bit and let's see what I can find out and if possible help mitigate some of the cons as well.