Path Tab

The local and remote path options will make it easier to test the script in local computer as well as publish/upload the script to Web server. If Upload to Web Server is selected, all item links that contains the path specified in Root Directory for Local Computer will be replaced to the path specified in Root Directory for Web Server in the JavaScript config file which will be saved along with the project file.

To use this feature, make sure that you keep the same directory structure of the files both on local computer and the Web server. For example, in local computer, the file A can be accessed through the following path:

file:///E|/Projects/websites/usingit.com/products/webtoolkit/index.html

In this case, set file:///E|/Projects/websites/usingit.com/ to Root Directory for Local Computer and set http://www.usingit.com/ to Root Directory for Web Server EXACTLY (the path will be replaced exactly so you can't add space before or after the path if there isn't spaces in actual path). Select Upload to Web Server and save the project, all local path will be replaced by web path in saved files (only in JavaScript file). But the local file path will still be saved to project file for future use. Now you can only upload the file and test it on web server. If you still try to preview the project in local computer, the error may occur because the generated files now contain web paths. You may encounter 404 error (page no found) if there isn't such files on the web server but the item links to them. If you still would like to test the menu in local computer, switch from Upload to Web Server to Test on Local Computer. Then you can preview the menu on local computer because the generated files will now use local paths.

Anyway, if you would like to upload the menu to Web server, switch to Upload to Web Server and then save the menu to get the web paths saved within generated files and then upload them to web server. If you would like to test the menu on local computer, switch to Test on Local Computer.