One addition was to replace the footer with W3.org validation links for every page. The infuriating HTML
\validation have been removed
Which is a total pointless waste of bandwidth, since normal users don't give a flying ****.
... again why I tell HTML 5 validation to f*** off at this point. JUST as omitting "projection" and "tv" from the media target breaks it for specific UA's like many kiosks and settops.
"fixing" said claims by the W3C of things that are NONE of the HTML specifications flipping business breaks things. Hence why "valid HTML" with this living document BULL is as much of a pipe dream as CSS validation was a decade ago.
NOT saying don't check it, but know which errors are total nonsensical mentally enfeebled "eye cans haz teh intarwebs" BULL!
Seriously, open your version of the page in IE11... now open my copy in same.
IE11, X-UA-Compatible IE=9, conditional comments strip off all broken CSS and Scripting:
IE11, X-UA-Compatible IE=edge, conditional comments are ignored and the page is a broken mess of broken non-working components.
And that is why I lack the words to use in polite company when it comes to the ****wit halfwit dumbass pedantic nonsensical BS changes they've made to HTML 5 over the past year or three. More so when there's ZERO blasted version tracking in document so yesterday's HTML 5 is invalid today, and today's HTML 5 has the potential to be invalid tomorrow.
It's the straw that broke the camel's back in my love-hate relationship with the W3C. They've gone from a well intentioned group of wishful thinkers pretending to be a standards body, to an abusive, manipulative, and duplicitous abusive spouse we're not "Allowed" to divorce.
Another addition was to add an Application Flow Chart image from another PHP Framework.
Ah, a flow chart... how quaint... in a "horse and buggy" career educator rel;ic of the early '80's (at best). "Hello computer... a keyboard? How quaint!"
Is it possible for anyone to create an Application Flow Chart for this framework?
Always possible, though the architecture logic isn't orthagonal; which is oft where flowcharts go bits -up. Much like the CISC vs. RISC debate, where one has the opcodes created as efficient as possible for performance and the support hardware (RAM, disk, BUS), whilst the other shoe-horns them into an organized grid where it's very efficient on the CPU die, but painfully inefficient for everything connected to it. Which is why ARM is cheap, very power efficient, and will NEVER match x86 on performance per clock or memory efficiency.
Orthagonal coding -- which is what a lot of those pesky "programming paradigms" try to be -- amounts to creating inflexible systems. They have a single over-reaching plan that often doesn't fit or allow for things to go outside their lines. MVC is an example of this where whilst it might make sense in certain very small corner cases -- event driven programming where it's single view-stack -- it's often a bloated pointless wreck when shoe-horned into request driven programming. (which PHP used for websites is most definitely request driven, not view driven).
This "square" layout that fits into nice pretty flowcharts is the proverbial round peg square hold problem. You pound hard enough it fits, doesn't make it right.
Also for the love of whatever flavor fairy tale genocidal maniac in the sky you happen to subscribe to, don't call this a framework. At best it's a "poor man's CMS" and that will change when I have the time to add database and user handling... which is around 70% complete with me plucking away it in my spare time between actual client proposals and some paying side-work doing builds and repair. Got a socket 1366 Xeon workstation on the bench right now that won't stay powered on and/or randomly loses video. Trying to convince the owner it's far past time to upgrade, and to buy a win10 license since they're on a bootleg of 8.1
I missed having PHP view files and far prefer them because I can change then according to the environment, etc
<?php // example view file
$tmp = LOCALHOST ? 'small.jpg' : 'large.jpg';
echo '<img src="' .$tmp .'" alt="myImage">';
It's also policy in how I write this that in normal echo commas are favored over string addition. Uses less memory and executes faster.
That's also a "variable for nothing" ... and you can go ahead and do that in the template or the content generation so I'm not quite sure what you're "missing".
<img src="', LOCALHOST ? 'small.jpg' : 'large.jpg' , '" alt="describe this properly!">';
Though when choosing a large or small image, that's typically the <picture> tag's job... well, at least it is if you tell IE to sod off.
I am also curious about adding a database and if this would ever be a replacement for the popular PHP Frameworks.
That is the next step to half-answer @benenaman's request, though overall what he's talking about and what I do and/or would do and/or would let clients do isn't even in the same galaxy, much less ballpark.