News for hackers. Stuff that matters.
Re:Retiring Chrome Frame by jordanthoms on Thursday June 13, 2013 @04:43PM (#5876447)
If Chrome Frame is necessary for you, why not continue it as a separate open source project? Google has already helped you massively, it's not their job to manage your backwards compatibility issues for you...
Re:Retiring Chrome Frame by dubcanada on Thursday June 13, 2013 @05:35PM (#5876748)
Because they made it nearly impossible by only releasing half the code, not releasing any installer build, and only releasing parts of the build system.
Re:Retiring Chrome Frame by robertshield on Thursday June 13, 2013 @05:43PM (#5876793)
All of the code necessary to build a working Chrome Frame and an installer binary is present in the open source repository. The code for the MSI isn't there, but that's just a very thin wrapper around the Chrome Frame and Google Update exe installers.
Re:Retiring Chrome Frame by dpedigo on Thursday June 13, 2013 @11:14PM (#5878084)
If you've got a copy of the MSI already, run it against Dark (the WiX decompiler) and you'll be pretty much handled a copy of the MSI source. Obviously you'll have some cleanup work, but it's a hell of a start. http://wix.sourceforge.net/manual-wix2/dark.htm
Re:Retiring Chrome Frame by dubcanada on Thursday June 13, 2013 @09:01PM (#5877737)
Yup it certainly is... too bad that the build is not usable without extensive knowledge of how to integrate it into IE. Something which a very limited subset of people know.