Client Side Scripting Client-side scripting is used when the users’ browser already has all the code and the page is altered on the basis of the user's input. Client-side scripting cannot be used to connect to the databases on the web server. Client-side scripting is possible to be blocked by the user. The Web Server executes the server side scripting that produces the page to be sent to the browser. The browser receives the page sent by the server and executes the client-side scripts. Client-side scripting can’t access the file system that resides at the web server. The files and settings that are local at the user’s computer can be accessed using Client-side scripting. Response from a client-side script is faster as compared to a server-side script because the scripts are processed on the local computer. Examples of Client side scripting languages : JavaScript, VB script, etc.
A WYSIWYG (pronounced "wiz-ee-wig") editor or program is one that allows a developer to see what the end result will look like while the interface or document is being created. WYSIWYG is an acronym for "what you see is what you get". An HTML WYSIWYG editor conceals the markup and allows the Web page developer to think entirely in terms of how the content should appear. One of the trade-offs, however, is that an HTML WYSIWYG editor sometimes inserts the markup code it thinks is needed all on its own. Then, the developer has to know enough about the markup language to go back into the source code and clean it up. The first true WYSIWYG editor was a word processing program called Bravo. Invented by Charles Simonyi at the Xerox Palo Alto Research Center in the 1970s, it became the basis for Simonyi work at Microsoft and evolved into two other WYSIWYG applications called Word and Excel. Adobe Dreamweaver (Windows/Mac, Paid) Adobe Dreamweaver is a...
Comments
Post a Comment