Search KB Filter article types
Obscuring
Categories: Server
Tags: Developers, Visual WebGui Pipeline, JavaScript, 2. Intermediate, 3. Advanced, Optimizing Performance, Pre v6.3, v6.3, v6.4 and Later
Revision: 1
Posted: 07/June/2010
Updated: 11/Oct/2010
Status: Publish
Types: Article

Overview

Obscuring is the name of a compression mechanism that is used by default on the Visual WebGui framework's client resources.

Details

Basically what obscuring does is the following:

  • It removes unnecessary white spaces and comments from the CSS, JavaScript, and XSLT client resources before they are uploaded to the client.
  • It Renames all JavaScript functions to coded names, that for example can begin with "sb" followed by the unique id number of this function.

This step also changes all the function calls to those functions to call the functions with their new names.

All of this dramatically reduces the size of the client resources, resulting in much shorter load times.

What this also does though (as a side effect) is that it makes the JavaScript file uploaded to the client virtually incomprehensible.
In a development phase when client resources need to be viewed and interpreted visually, it is good practice to temporarily disable the obscuring mechanism.
To learn how to disable the obscuring mechanism, please see the Disable Obscuring article.

JavaScript intercommunication

Obscured JavaScript functions can call JavaScript functions of other applications that are deployed on the same domain.

There is however an issue with JavaScript on external applications calling obscured functions.
The reason is that when calling those functions you would use their non-obscured name, and when the function is obscured, it's name is changed to some other coded name.
There is an issue on the subject, that you can see here.
Within this issue we will add a client library that will allow access to the obscured JavaScript functions using their original names.

There is an article showing how to workaround the obscuring mechanism and still be able to communicate with obscured client resources from an external source (on the same domain).
You can view this article here.

ReferencesArticlesForumIssue tracker

About the author

Related Articles

Server  
Title Update Author
In this video we show the new ability to develop Visual WebGui application using Xaml in what is called Visual WebGui Sites. Visual WebGui sites lets you work as a web site editing code and design and simply refreshing the page to see the results.
Tags: Architects, Developers, Windows & Dialogs, XAML, 1. Beginner, 2. Intermediate, 3. Advanced, v6.4 and Later, Visual WebGui Pipeline, C#, XML, Customization
19/Aug/2010    2010/08/19
Tags: Architects, Developers, 1. Beginner, 2. Intermediate, 3. Advanced, Pre v6.3, v6.3, v6.4 and Later
04/Jan/2007    2007/01/04
The following code is the application that was used to introduce the new Visual WebGui Xaml concept.
Tags: Architects, Developers, C#, XAML, 3. Advanced, Visual WebGui Pipeline, XML, 1. Beginner, 2. Intermediate, Customization, v6.4 and Later
19/Aug/2010    2010/08/19
Tags: Developers, Events, 1. Beginner, 2. Intermediate, 3. Advanced, Pre v6.3, v6.3, v6.4 and Later
04/Dec/2010    2010/12/04
Tags: Developers, Visual WebGui Pipeline, 1. Beginner, 2. Intermediate, 3. Advanced, v6.4 and Later
02/June/2010    2010/06/02
Tags: Architects, Developers, 1. Beginner, 2. Intermediate, 3. Advanced, ASP.NET, Pre v6.3, v6.3, v6.4 and Later
24/Sep/2010    2010/09/24
.NET HTML5 Web, Cloud and Mobile application delivery | Sitemap | Terms of Use | Privacy Statement | Copyright © 2005-2012 Visual WebGui®       Visual WebGui weblog on ASP.NET Gizmox Blog Visual WebGui Group on LinkedIn Visual WebGui updates on Twitter Visual WebGui Page on Facebook Visual WebGui YouTube Channel Visual WebGui Platform News RSS