Re^12: Update the GUI (What we want?)

> 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!}

Comment on Re^12: Update the GUI (What we want?) Download Code

Replies are listed 'Best First'.
Re^13: Update the GUI (What we want?) by Your Mother (Archbishop) on Jul 25, 2016 at 00:02 UTC
I look forward to your stabs, as it were. Who knows, maybe you will decynicize me into participating.	[reply]
Re^14: Update the GUI (What we want?) by LanX (Saint) on Jul 25, 2016 at 00:17 UTC
> maybe you will decynicize me Nahhh, never! > I look forward to your stabs, as it were. stabs ? Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]


There's more than one way to do things
	PerlMonks