Gizmox - Guy Peled's Blog

Visual WebGui 6.3.11 was released after we had a major breakthrough with an issue that had been with us from day one of the Visual WebGui designer. I guess most of you are used to reopening the designer after certain actions. You can imagine that we had sleepless nights thinking about this issue as we aim at perfection and this issue is far from being some thing you can live with. 

The issue I am talking about is this issue, which as its id (642) indicates is a long standing issue that has a few related issues.

The irony of it all is that all the hours spent on finding this issue resolves in simply deleting one extra disposing call. When renaming forms, changing certain parts of the code and some more places, Visual Studio requires the designer to reload and that simulates the closing and opening the designer but obviously not perfectly as one service required to be left between the first loading and the second one.

The new release is available for download here.

I would like to direct your attention to an interesting article targeted for Web developers and more specifically ASP.NET developers who would like to learn a way to focus their development efforts on algorithms, requirements and business logics using a new, highly productive, boosted web development paradigm which provides maximal flexibility, interoperability and interactivity with any other web applications, controls set and architectures.

The article compares between traditional web development paradign represented by ASP.NET and a new approach represented by Visual WebGui.

To read the article click here.

The following post is taken from an article that explore the differences, pros, cons and usages scenarios of the Server empowered web architecture of Visual WebGui and on the other side the Client empowered web architecture features by solutions such as Classic AJAX, Flex/Flash, Classic Silverlight, Java Applets.

Both server and client empowered solutions can support any kind of UI look & feel using Silverlight or rich AJAX.

Client empowered applications support the highest performance in applications that data interactions are less common than pure UI/animations/media interactions.

Gaming, animations, and, most of the editors are not security critical applications so that client solutions are valid for those, however, server empowered solutions and more specifically Visual WebGui is much more secured by design.

Client footprint is the parameter representing the download weight as a function of the application’s complexity. When client UI interactions, animations, and media are more common, and the software updates frequency is relatively low, then client solutions tend to be more efficient regardless their weight. However, in any other case the small & static footprint of Visual WebGui server empowered paradigm is much more efficient and reasonable.

Client empowered solutions are virtually more scalable as they reduce mass responsibilities from the server. However, when the intensiveness of data interactions is higher than UI changes or heavy animations and media, Visual WebGui server empowered paradigm provides the best scalable and redundant solution.

ull virtualization of the desktop environment i.e. Registry and File system is enabled within Visual WebGui server as a complementary service, providing full virtualization of desktop environment for web/cloud applications.

Media, streaming and animations based applications, require the flexibility of Silverlight and Flash client based applications, the set of tools offered in this family of development tools is more graphic designer oriented and adapted. Visual WebGui server empowered paradigm with single layered object oriented code, desktop like form designer, point & click customization, and data designed set of controls, developer gains great advantage when developing data/business centric application. It simplifies and cuts about 90% of this kind of apps development time.

Maintaining single layered object oriented code is preferable in all cases than any kind of multiple layers and technologies. Even Silverlight which enables Dot.Net in the client requires the establishment of application .NET client & XAML infrastructures and .NET server code as data infrastructures in different layers.

The same tools are available for web UI (DHTML/Silverlight) customization whether the architecture is client empowered or server empowered. However, customizing data controls and business functional UI is enhanced and boosted with the Visual WebGui server empowered paradigm point & click controls designer.

Sharing WPF/Silverlight XAMLs, code & resources may result in some level of presentation freedom (enabling the use of the same application from multiple devices and media). Though, the complete decoupling of Visual WebGui server empowered paradigm code from the presentation layer provides full capabilities to choose any device as an alternative presentation layer (plain browsers, Silverlight, Flash, mobile devices, smart clients etc).

You can read the original article here...

Visual WebGui 6.3.8a was released today as a fix to the following issues of the Visual WebGui 6.3.8 platform:

VWG-5087 - IE-Button: The right-side border should be rendered in the correct position
VWG-4256 - Button with 21x21 image should not crop image with button size of 25x25
VWG-5091 - OpenFileDialog non-Flash should not throw JS error (while calling parent.Upload_CloseWindow())
VWG-5092 - OpenFileDialog non-Flash should not hang when OK button pressed
VWG-5093 - OpenFileDialog in Flash mode should not throw JS error while Obscuring active
VWG-5090 - OpenFileDialog non-Flash should show frames around the buttons

Click here to download all 6.3.8a versions...

Visual WebGui Web & Cloud platform version 6.3.8 was released today.

This is a further stabilization of 6.3.x that includes some resolved button behavior issues, as well as features such as Flash 10 uploading compatibility and the ability to configure a virtual directory.

The full v6.3.8 change log can be found here.

Click here to download Visual WebGui 6.3.8...

Being ASP.NET based Visual WebGui is coded, parsed and executed on top of .NET and is most native application nature for Windows Azure, Amazon and other cloud providers.

Having an optimized received & sent data actually concludes in lowering the transportation and the costs when it comes to cloud deployment. The highest request-per-second compared to any other AJAX infrastructure proves the simple fact!, the CPU is much less occupied with allocations & disposals of objects and results again with lowering CPU usage and  the costs of  cloud deployment.

The internally optimized support for application scalability and redundancy enables cloud applications to scale as much as needed seamlessly.

Having a mechanism that saves the smallest amount of data required for state persistence, results in keeping the amount of data transactions low as possible.

Visual WebGui's WinForms identical API and desktop compliant development patterns, and visual WebGui capabilities of supporting  desktop's richness on web  make it only natural to port desktop business centric apps to the cloud using Visual WebGui maintaining  the same UI without the need to completely restructure and rewrite.

You can read more about the Visual WebGui technology here and view the Visual WebGui Catalog sample running on Azure cloud here.

Wiktor Zychla has assembled a tiny AJAX framework contest between Visaul WebGui, ASP.NET AJAX and Ajaxium. Comparing a givven scenario he checked bandwidth consumption, requests per second, etc. The results as Wiktor wrote them are: "The VWG is an undoubt winner. It did a great job of serving the highest number of requests per second, 422, and is also a clear winner regarding the amount of data sent to and from the server."

Contest context

More than two years ago we've built a small web application used to collect and print documents required to participate in secondary school final examinations in Poland. The application is used quite extensively by people from all over the country.

The application, maturzysta.vulcan.pl, is located here.

From the web developer's point of view there is one interesting aspect of the main form of the application: there are about 30 dropdown lists with complicated logic between their selections: when you change the selection in one list, few others should be cleared or repopulated with context-bound data. There is also quite a lot of validation of various dependencies between user's selections.

The first version of the application was built as a server-side application: all SelectedIndexChanged events were auto-postbacked and processed on the application server. This caused a lot of trouble since the heavy form had to be sent to and fro the server.

The year later we've completely redesigned the application, moving the interface logic to the javascript. The web traffic problem has been solved but two other appear. First of all - no one likes javascript, it's clumsy and error-prone. Then - we had to disable ASP.NET page validation mechanism because otherwise the page content modified on the client-side would be rejected on the server-side as potentially dangerous.

In the meantime, few promising AJAX frameworks appeared and we thought that it would be possible to go back to the initial version of the application but instead of expensive postbacks we could take the AJAX approach and replace postbacks with callbacks. This could solve all problems: reduce the traffic and still keep the application logic on the server-side.

Read more...

A new version has been released and it includes many bug fixes and lots missing functionality implementation mainly with in the DataGridView control. There are also lots of new features that had been requested by developers including redirecting, clipboard support, Invoking client side scripts, Calendar first day support, ListView auto resize and more.

The DataGridView control has been added many missing implementations including selection management and events, deleting rows, resizing columns and rows, changing captions and visibility, alternative row style and more. You should be aware that previous versions of VWG had added the DataGridView control with lots of unnecessary definitions. While not harmful in the previous version, in the new one those different properties are working and could cause unwanted behaviors. You should clean up the InitializeComponent code from the different DataGridView definitions keeping only the positioning,dimensioning and data source attributes.

We are currently also working on a Vista theme that will be released soon. The site demo has already updated to work with the new theme.

For a more detailed change see the issue tracker here.

As always you can download the latest version from here.

Yes I know I have not written for a long time.  I was kind of thinking about blogging and all and I did not get my self to start writing. Any way there is a new Visual WebGui version with extensibility features and we are working on supplying at last documentation. God knows way but documentation seems to be the hardest part of the development process and yes we all know its a very important part of any product.  Documentation is on the way....

As always you can find the new version here: http://sourceforge.net/projects/visualwebgui.

The new version contains many bug fixes and performance enhancements and the change log can be viewed at http://support.visualwebgui.com.

As always you can find the new version here: http://sourceforge.net/projects/visualwebgui.

There is a new version fixing a critical bug found in the last version regarding a new capability for boosting performance by caching resources in run time. The bug caused an error to be thrown when the application was executed which detailed a permission denied error on writing a file to the “C:\windows\system32“. Just to clear things up, Visual WebGui does not require these permissions and normally it does not attempt to write the disk. 

In order to test the new performance boosting capability a definition should be added to the WebGUI section:

<StaticResources Mode="On" />

There could be some permission issues with this feature as it uses a physical directory to store cache. You should add a "Route" directory under the site root and give it write permissions to avoid permission issues.

There is also a new Timer component that basically works just as the WinForms timer works. It is new feature that is still under QA. It is critical that you call Timer.Stop() or Timer.Enabled=false before the containing component dies as currently timers are not destroyed automaticly. Timers don't work currently by default and should be enabled by adding a definition to the WebGUI section:

<TimersEnabled Mode="On"/>

When this feature is released this definition will not be nacecery.

There is also a new configuration key called PrivateVersion that allows developers to add custom cache version dependency. The private version is concated to the public version cache key and enables invalidation of cache in cases like theme development or custom controls. The cache key is used both client side and server side so by changing the private version you actually are invalidating also all client cache. The private cache is used as following in the WebGUI section:

<PrivateVersion Value="2"/>

If the current public cache version is "1.24" the cache key will be "1.24.1".

As always you can find the new version here: http://sourceforge.net/projects/visualwebgui.