[TYPO3-dev] Moving the topic of the discussion a little bit--Based of thread "Change roadmap..."

[Christopher]

Hiya,

On 4/12/06, Dimitri Tarassenko <mitka at mitka.us> wrote:
> JoH,
>
> On 4/12/06, JoH <info at cybercraft.de> wrote:
>
> > > Iterating items in a set just to display them is the task of
> > > presentation layer. And right now in Smarty you can do it in the
> > > template, while in TS+Markers you have to do it in your object code.
> >
> > Where it belongs IMHO.
> > As far as I understood seperation means
> > Design - Logic - Storage
> > for current TYPO3
> > HTML/CSS - TypoScript/PHP - MySQL
> >
> > I don't see how this can be realized with smarty.
>
> I think we are talking about different things. HTML/CSS is just a part
> of presentation layer, and a very small at that. To give you a
> real-life example, let's take calendar extension.
>
> Russians are somewhat weird people and their week starts on Monday.
> Does this fact change any _LOGICS_ as far as the calendar should work?
> No, it just changes the way it should be rendered when we are viewing
> a month at a time (we should put Monday at the beginning of the line,
> all other things being equal). Therefore, only a change in
> _PRESENTATION_LAYER_ is needed, while all the code that handles
> recurring events and so on still makes sense.
>
> Can you implement this change that in TS+Marker _templates_? No, you
> have to modify displayWeek() function in class.tx_calendar_pi1.php by
> XCLASSing it, while in reality all you need is just a different look.


I'm not following the logic here--this is _exactly_ the sort of
thing--configuration--that TS is purpose-built to do. It doesn't
reflect well or poorly on either Smarty or TS if the design of the
displayWeek() function in the main calendar class is not well-adapted
to the framework it runs in (i.e. if the class has not been made
TS-aware for such a commonplace calendar operations)...

Whether TS or Smarty are part of the presentation layer or not, I
think that one of TYPO3's _strong_ points is an almost total
separation of any kind of control structures from the markup. It's a
feature, not an omission.

-Christopher