Client-side object framework
One of the key strength in WebUI Framework is the new Client Side Object Framework.
WebUI Framework does not only contain server-side class libraries used in .NET Environment,
but also offers huge libraries and resources in the client side for better OOP structure
and design consistency in high-end components derived from the framework.
The Client Side Object Framework (further called CSOF)
fully takes advantage of JScript language to provide true inheritance object model
to expose common properties and methods to all WebUI Studio components. The parallel
consistency between client side and server side object model really introduced a
new achievement and capability in increasing developer's productivity.
One of the biggest advantages is the engine-model libraries replacing traditional
global functions which took more memory consumption and thus impacting client side
performance. Although the engine classes are not intended to be used by developers
directly, we have made all necessary functionalities to be accessible in the object
level and performing mapping to the engine libraries. The engine model also allows
multiple versions of libraries to be run simultaneously between different versions
of components, enabling long-term investment for mature, rock-solid high-end components.
The result of the inheritance and many new features available in CSOF that we can
see is the ability to access any instances in client-side with only one single function.
In this purpose, Intersoft has taken the giant steps to really focusing on developer’s
productivity. For example, in common ASP.NET components, one has to remember the
function name to access the object for each component. Imagine if you have about
10 components in a page where you need to access them in scripting, then you would
have to remember 10 function names. This is no longer required by the introduction
of CSOF.
All WebUI Studio products should be automatically derive from the CSOF and therefore
should meet the requirements and new standard in client object's structure. The
CSOF requires the object's structure to be as similar as possible against the server0-side
object model including the name of the properties and the hierarchy of public objects.
This will in return producing self-understandable syntax and properties. You can
consider the client side object structure as a mini-version of server side object.
All WebUI Studio products automatically take advantage of the common client-side
events available in a W3C browser context.
Each client side event now exposes at least 1 parameter that is the controlId. The
controlId is actually the ClientID of the server control, enabling the script to
run properly when running in complex user control or portal-based environment.
These client side events are specifically designed for element such as DropdownButton,
CalculatorOperandEvents etc. These events also expose at least 1 parameter, the
controlId as the standard.