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

The reason why I think it's a terrible way to go about it is it completely violates good web app design concerns. It uses the View and the Model and half of the Controller as a TERRIBLE API to construct a new view, a new hybrid model which consumes the view and the model and turns it into a new model, and new controllers which have to account for all this mess to create a new, more reasonable, interface. It's possible, sure, and if someone smarter than I am can show how to do it well, I'd rejoice and sing hosannas. I've been doing this awhile though and CSS improvements, like what tobyink did, and perhaps some Ajax voting are about as much as could be expected and it wouldn't be super easy and would (probably) still require user action to add the CSS and JS manually. Therefore this would be of zero use to newcomers and casual visitors... If the Gods determine the scripts/CSS are safe enough to implement in the actual site delivery, maybe... I would never advise anyone to build out technical debt though. I wouldn't try to stop them to strongly either. :P

The core of what this site is/does is quite basic and if just a couple of monks with the chops committed to it, it would be done in 6 months. Less if bikeshedding could be avoided.

Comment on Re^11: Update the GUI (What we want?)

Replies are listed 'Best First'.
Re^12: Update the GUI (What we want?) by LanX (Saint) on Jul 24, 2016 at 13:11 UTC
> 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!}	[reply] [d/l]
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]