Robert,
Generally the designers I work with find conditional statements,
variable management and loop statements confusing and they would
rather concentrate on the physical layout and style of the interface.
Most XSLT I have been exposed to does not expose the aforementioned
constructs to the designer so I would not consider that code.
On Jan 2, 2:21 pm, Robert Kluin <robert.kl...@gmail.com> wrote:
> You could have your designer write little templates for each "thing"
> you would like to display. If they are named in some "standard" way
> your developers will know how to call the templates as needed. That
> sounds pretty close to what you are asking for. Not sure it sounds
> like a good idea though.
>
> Also, you do not have to use the django template engine -- I do not.
> I personally use mako templates for all of my App Engine apps. You
> can run any pure python template engine.
>
> Just out of curiosity do you define XSLT as code, design, or both?
>
> Robert
>
>
>
> On Sat, Jan 2, 2010 at 12:40 PM, Kelly A <kelly.j.ander...@gmail.com> wrote:
> > I have this problem with most templating systems, they talk about
> > separating code from HTML but then they define all these programming
> > constructs like if, while, for, etc.. For instance given the example
> > from the getting started guide:
>
> > <html>
> > <body>
> > {% for greeting in greetings %}
> > {% if greeting.author %}
> > <b>{{ greeting.author.nickname }}</b> wrote:
> > {% else %}
> > An anonymous person wrote:
> > {% endif %}
> > <blockquote>{{ greeting.content|escape }}</blockquote>
> > {% endfor %}
>
> > In the above "HTML" there are five lines of code, this is not
> > separation of code from HTML in my book. There is no ifs, ands or
> > buts about it, that is code, if a designer looked at that they would
> > say that is code. If this were HTML separated from code it would look
> > more like this:
>
> > <html>
> > <body>
> > <gae:list of="greetings">
> > <gae:listItem >
> > <div class="name"><gae:field name="author.nickname" /></
> > div>
> > <blockquote><gae:field name="content" /></blockquote>
> > </gae:listitem>
> > </gae:list>
>
> > The developer/programmer would handle the case statement and the
> > iteration back in the code where it belongs. All the designer needs
> > to know is that this will display a list and the list item allows the
> > designer to layout and style each element in the list.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appeng...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/google-appengine?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
