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

[Dimitri Tarassenko]

Christopher,

On 4/12/06, Christopher <bedlamhotel at gmail.com> wrote:

> > 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)...

What I am arguing is displayWeek() function should not be in the
calendar class at ALL. If it just displays something (as its name is
hinting), it should be implemented in the presentation layer
(template), and it's too damn bad TypoScript can't do it because it
can't iterate sets/arrays.

> 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.

Separating control structures from markup limited practical value at
all if you don't separate the objects' logic from their presentation.
In the example I was talking about the control structure that iterates
over days in a week clearly belongs to the presentation level
(template),  but not the object logics itself.

It is a feature, however it's a "crippled" one, because you can only
change _some_ things about how an object should be visualised by
changing the template, but not all.

--
Dimitri Tarassenko