> You could also change the 1.x code and just "hide" stuff if you want.
First off, I'm not trying to be harsh, but it's 1.1.x (stable) and 1.2.x
(development); 1.x would ambiguously refer to both.
> (Question, does version 2.x use a code/markup separation layer?)
We have no plans for integrating output templates within Mantis 1.2.x
(which is heading for RC status soon). It would be a large,
complicated, and time-consuming task; the existing codebase makes far
too many assumptions about interactions between API's and output. There
are, however, a couple initial attempts at templating in various places,
and we're generally in agreement that we need to make the move; it's the
effort/time-to-reward ratio that tends to be rather low as compared to
fixing actual bugs or adding requested features.
Maybe for some future version 1.3/1.4, we might eventually get to the
point of implementing templates, but it's not in the cards for anytime soon.
> (Mixing HTML and script/code is too ASP-like for me and about 5 years
> out of date)
Mantis dates back about nine years, if that helps to explain it's
less-than-stellar appearance. :P
> Don't get me wrong. I like Mantis. Just wish the code base wasn't
Don't we all...
> This is the whole reason why C#/Java have developed great layer separation.
> Isn't there something out there for PHP?
Great layer separation doesn't require anything special in PHP; PHP is
in fact its own templating language (that's what makes it so great for
web apps). The problem is that much of Mantis was developed before such
concepts as MVC, templating systems, separation of layers, etc had
really become mainstream for web applications, and we are now tasked
with, in the little amount of developer time available, whether to make
the code look nice, or to fix bugs and/or add features...