hi all,
on 2007-05-04 10:44 Aristedes Maniatis wrote:
> In our work to adapt Mantis to our own needs and
hopefully return our
> efforts back to the Mantis project, we are trying to
understand the
> code structure.
...
> Secondly, there is confusion about the way pages are
built.
This is one of my main hurdles as well. Together with the
complicated
execution paths and a lot of work being done as side-effects
of function
calls.
> I understand that some coding with Smarty templates is
already
> underway. Is it far enough forward that we should be
performing our
> work within that code? It would certainly make what we
are doing
> simpler. As is, there is considerable mixing of
functionality with
> presentation, making changes somewhat difficult.
[...]
> We are already wanting to make so many changes to the
code that very
> quickly our version will be very hard to merge with the
original
> should some of our changes be desired by the main
project.
Trying to move towards Smarty is my current headache project
 I've
been on and off working on that for some months, starting
from the
EXP_TEMPLATE branch of thraxisp. The difficulty is the
legacy of the
code: it all started with smart ways to build the
application
PHP-without-objects, but extending it over the years has
resulted in
quite a complex spaghetti to enable easy customisation
The work of thraxisp includes introducing objects, and
Smarty with
themes and multi-lingual extensions. We're doing our own
customisation
project based on that code, trying to rework the code more
toward a
layered architecture. With my colleague, I'm really
discussing these
days how to proceed: a full redevelopment of the core based
on
contemporary coding practices and PHP version actually
looks like the
most desirable approach. But for now, we're still trying to
rework
existing code to separate presentation, configuration and
business logic.
For our purpose, we're trying to maintain database and
screen
compatibility with Mantis (being able to run a standard
Mantis on the
same database, and having a "classic" theme that
renders the screens as
close as possible to the way Mantis does it). (We're not
strict on "URL
compatibility", but it's not easy to really remove
legacy code.) That
should make it possible to keep benefiting from eg. the
MantisConnect
bridge towards Eclipse's Mylar project, the wiki and email
integration,
and other nice things like that.
I'm happy to share more concrete insights, this email is a
bit abstract
/-- Kind regards,
/--- Rolf.
(I don't know if the core developers are already thinking
about a
"Project Phoenix" to revamp the code for a new
version?)
------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
mantisbt-dev mailing list
mantisbt-dev lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev
|
