> It uses the View and the Model and half of the Controller as a TERRIBLE API

I agree.

But what are the alternatives?

(Closing PM down and "defecting" to SO? ;-)

Since you are rejecting the DB scheme, even building an new alternative MVC application on top of the data seems out of discussion, right?

And if you did this new MVC front end, it might take so long that new requirements would arise, not talking about all the additional legacy plugins which might get obsolete in the meantime.

I have a strategical point of view on the things, improving the design will bring the best and fastest return of investment ... politically, technically and from a marketing perspective.

And afterwards a long term strategy can improve the other issues you listed

> If the Gods determine the scripts/CSS are safe enough to implement in the actual site delivery, maybe

That's my plan.

For me Toby's approach is "only" a prove of concept.

I plan to invest a week to improve it (in my own "dogfood" interest ;) after YAPC::EU, build a show case and try to convince the gods of a long term strategy.

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

In reply to Re^12: Update the GUI (What we want?) by LanX
in thread Update the GUI by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.