Use of the Defriendify Utility assumes that you have had some experience of using webProg3, and that hopefully you have read the Full Help.
As you know, webProg3 is able to produce "Mobile Friendly" web pages, which means that they automatically adjust to whatever size of mobile device they are displayed on. However, they have 2 other important usages:
1) Display on PCs which have a screen size that is less than the one used to produce them (1920 x 1080 pixels).
2) For printing. They automatically adjust to the viewport of the paper.
The above applies to static webpages. "Friendification" can also be applied to dynamic Javascript apps produced in webProg3, but this needs to be done with great care since Javascript/JQuery does not always work with vw units instead of pixels. For this reason, you will see that the Defriendify Utility App divides "friendly" scripts into two parts:
b) One at the bottom that contains the JS (usually not completed for static web pages, but having necessary content if the page is
to be a dynamic one).
a) One at the top, which is everything else - basically HTML coding.
With this arrangement, you can decide whether to "defriendify" both parts, or just the top part. (Just to clarify. "defriendify" means nothing more that to change the Mobile Friendly page's viewport width (vw) units back into pixels.)
This utility app should not be necessary at all!
If you have read the Full Help provided, you will see that webProg3 is only able to upload its own "standard" pages. Even though it can produce "Mobile Friendly" pages, the current version is unable to understand them. You are therefore advised to keep your "standard" pages in a safe place, so that if future modifications are required, you can go back to the standard page, upload it, make your changes, and save another Mobile Friendly version. If you keep all your standard pages in a safe place, whatever their employment, you will have no trouble. However, if the pages involved really are for MOBILE usage, and you lose them, THERE IS NO RECOVERY.
However, if you have produced "PC Friendly" or "Printer Friendly" pages (including SOME "browser apps"), there is a chance of recovery if you have lost or mislaid the originals. And the Defriendify Utility is here to give you a hand.
The difference between true "Mobile Friendly" pages and other "friendly" (i.e. adaptable) kinds of web pages lies in the manner of production. See the WP3 HELP for elucidation.
Defriendify helps the defriendification process by separating the HTML and the JS.
Static web pages for the PC and for printing have no content in the Javascript section, so all you need to convert is the HTML at the top.
Adaptable Browser Apps require consideration regarding effects on the Javascript. Your browser app may or may not work satisfactorily under conversions between vw units and pixels. In general, or if you are in doubt, I suggest you try converting your page BOTH ways in order to check the result: once WITH Javascript conversion, and once WITHOUT Javascript conversion.
