[EMAIL PROTECTED] wrote:
what will be the differences between $tile.setTemplate and
$navigation.setTemplate except that the templates will
probably in another directory than templates/navigations ?
The difference is mostly the order of processing. It basically allows
you to have any number of "screens" to build your application from as
opposed to one. My first implementation was indeed a derivation of
$navigation but this turned out to be confusing and clumsy.
I do agree that we need to provide a kind of web component
that pull it off from the layout template but do you think
that it will be easy to maintain x-web-component-templates ?
Actually my suggestion was to (medium-term) get rid of the strict model
that Turbine uses and to offer more screen element flexibility to the
framework user. More or less in the lines of the Turbine 2.4 pipeline
concept, if you want.
what about if I need n-types of calendar in my application ?
should this to be process from the server side ? I say that
because there are some technologies that do it well from the
client side prospective such as dojo:
The calendar was merely an abstract example. I have different data grids
to display and the tile approach allows me to display them freely
depending on data availability and user choice. The level of code-reuse
has been improved a lot.
I agree that AJAX basically does the same thing on the client side but
this is not always feasible or desirable.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
