[03:50:18] TimStarling, I overlooked one detail about the parsermigration api ... which is that the output is only contents of the body tag without modules, css, etc. Is it easy to fix that? [03:57:23] well, the API can provide the contents of ParserOutput::getModules() etc., but I'm not sure if that would answer your needs [03:58:13] that function only returns modules that are specific to the page [03:58:23] like TMH when a video is displayed [04:03:21] CSS would probably be sufficient for the purposes of this project. [04:03:41] one alternative would be to fetch a whole page view, and replace the content area of it with what ParserMigration returns [04:04:37] do you mean that as something to do in the visual diffing code? [04:05:14] yes [04:05:59] ok ... ya .. i can explore that tomorrow ... for now, i hacked and messed with cookies with phantomjs to use the regular parsermigration-edit view and hide form, and selectively hide left/right .. but, it is unreliable and a hack. [04:06:19] instead fetching pge, and fetching the API and selectivey plopping the body in place might work better. [04:07:10] at this time, i've figured out some of the kinks in the phantomjs and rendering from file uris .. so, alright. i'll pick that up tomorrow. [04:10:09] alright, off now. talk tomorrow. [22:49:32] SMalyshev, is there an EOL defined for PHP 5.6 somewhere? [22:49:55] MaxSem: http://php.net/supported-versions.php [22:50:17] It's already past active support, it's security-only for another year [22:50:18] thanks! [22:51:02] oh heh, 7.0 goes out of support before 5.6 [22:55:23] php 5.6 is the last 5.x release [23:01:20] MaxSem: there's PHP_EOL [23:01:44] ohh you mean different EOL :) [23:02:16] hahaha [23:02:28] lol [23:03:02] ok, so yeah 5.6 is kinda LTS, so security fixes until 2019. Maybe even more if people scream really loud, but likely not [23:03:26] most likely it will be EOLed in 2019