In ExeOutput 2018, EXE starts slower because the Chromium engine is fat. We must first unpack all required resources. It will be the same in HTMLEXE 2018 if you decide to merge the runtime module files into the EXE.ukmas78 said:you replaced the old HTML Viewer engine with the new Chromium engine. can the file out still be separated into .exe, and .hedata? This is very important since the .exe file becomes small and run faster because that is not the case with ExeOutput 2018
We hope so. We’re still studying the legality of this.ukmas78 said:Flash content still remain smaller than HTML 5 content, can the Chromium engine come with an inbuilt flash plugin for the Chromium engine if flash is enebled?
Not sure what to answer. Each time we give an estimated date, we’re unable to achieve that. Like someone said, “soon”. Anyway, it will be in the beginning of 2018.ukmas78 said:Can we get an estimated release date?
Thank you for the update, does it mean if we don’t merge the runtime with EXE. it will run faster? and will .hedata not apply when Chromium engine is used?gdgsupport said:if you decide to merge the runtime module files into the EXE.
ukmas78:
It will also be nice if there is no legality issue on this or leave it to the us to request permission from Adobe, as we have also sought for it.gdgsupport said:We hope so. We’re still studying the legality of this.
That will be awesome, We have waited 2 years for this and we look forward. I will also suggest you create an insider program for all your application for early review and suggestions. God’s speedgdgsupport said:Anyway, it will be in the beginning of 2018.
We use essential cookies to make this site work, and optional cookies to enhance your experience.