Purpose...
Builds...
Latest Build...
Mini-Help...
Full Help...

https://webprog3.com/purpose,sametab

https://webprog3.com/builds,sametab

https://webprog3.com/latest,newtab

https://webprog3.com/mini-help,sametab

https://webprog3.com/help,sametab

https://webprog3.com,sametab

Save
Just like the "Preview" function, there a 3 short steps to the Save process, and the first 2 steps are identical. First, you are asked to decide what margin, if any, you would like at the bottom of your webpage. Second, the output script is displayed in an HTML editor to give you the opportunity to hack the code if you wish. In the Preview, you are then shown a simulation of the webpage display in an iframe, but in the Save function you are simply asked to choose where, on your computer, you would like to save the output web file. The file you save is an exact copy of what was shown in the HTML Editor.
It is never a bad idea to save your work as often as you can, whatever system you are using and whatever you are doing. This is especially true in the case of browser programming. For example, you can be happily working away and everything has been working smoothly for a long time, but then the browser tells you (if you can find the warning) that you have exceeded what it considers to be your appropriate quota of memory, and it goes on strike! You can also suffer temporary glitches on the Internet which defy explanation. And so on.....
There are also limitations to saving files which do not occur in normal programming. In normal programming, you do a "Save As" the first time you save a file. Once its name and location have been established, you can then just do a quick "Save" to update the output. Not so in browser programming. Doing a tiresome "Save As" every time is the only solution. On top of that, the path and name of the file you save cannot subsequently be retrieved. That's why the name of the "Source File" in the top left-hand corner of the main screen cannot be updated with the new name you have given to your script. Browser makers usually decide to do what they do on the grounds of "security", which of course we must agree is admirable. But instead of making potentially unsafe things safe, they just block them, which is certainly easier for them!
Those things said, here are a few screenshots of the Save process, the first 2 steps of which are identical to what happens in the Preview:
If the height of your webpage is near, or greater than, the height of the browser's display area, you might want to ensure that the blank margin you have at the bottom, after the last widget, is of adequate size.
If so, type it in here. It can have any number of pixels.
The output script for your webpage will then be opened in the HTML Editor, and you can make alterations to it if you want.
The alterations you make, if any, will be included in the script that is subsequently saved.
When you click on the red "Exit" button at the bottom of the screen, you will be presented with a "Save As" dialogue:
Just type in the name of the file, navigate to the folder of your choice, and save.
A final word about the alterations you may decide to make to the script in the HTML Editor.
You can change anything you like, but your changes may produce a file which becomes incompatible with further uploading and processing in webProg3. That's perfectly OK if you want to do it. Personally, I often hack files to death, including all kinds of things that are above and beyond WP3's ability to handle. WP3 has done its job, which is to set up my app without having to type tedious lines of HTML coding, and I am happy to carry on without further help.
For a little bit of guidance over what alterations may or may not interfere with WP3's uploading/handling ability, please refer to the next section in this Help.