Hi Alexnaldo,
Thank you for the kind words and for pointing this project out for us. It's indeed a very neat and well known Ajax Framework.
Gizmox point of view is quite different comparing to other declarative based languages (such as XUL, XAML and others) which are rather a complementary and enhancements of the traditional web development rather than an adoption of another paradigm to develop web.
Visual WebGui addresses a much broader and a more pretentious target, which is extending the *full set* of the mature desktop development paradigms, with which developers could easily create very rich applications, to the web. I would say, to provide an object oriented, drag & drop like development with the richest set of events, making it possible to have at least the set of tools you would have with desktop (WinForms) development. It's seamlessly taking care of the presentation layers and client/server communication using a unique (patented) pipeline.
The last year+ of development efforts at Gizmox combined, among other targets, extending the basic WinForms model and actually resulted with a total new product in the sense that on top of the basic nice and quick WinForms development, you can now completely extend, customize and configure the application.
While previous versions (until 6.3) aimed mainly towards WinForms compatibility, the upcoming (already beta2) 6.4 version is a much extended form of development, providing a good starting point with desktop development but much extending it leveraging the web benefits and addressing web challenges. WinForms compatibility is very important for us in order to support both scenarios of WinForms and VB 6.0 migration to the web using VWG and immigration of developers and skills from the richest desktop development environments to the web. However, bear in mind that although we maintain "backwards" compatibility to WinForms, about 50% of v6.4 are extensions on top of WinForms and extensions for the web!
It is not one of VWG goals to complement the traditional web development with components and tools (such as jQuery, Dojo, ExtJS and others or even component vendors such as Telerik, Infragistics, ComponentOne, Syncfusion and others), but providing an end-to-end solution for development and runtime with which you can use proven desktop development paradigms to create the richest, best performing and fully scalable application using a single layer of object oriented code and event driven development only which enables combining other technologies as needed (i.e. we have added jQuery support within 6.4).
As for the maturity question of VWG and the "not all features are functional" claim, while that is probably true for a partly featured 6.3 pre-release it will not persist with the upcoming official 6.4 release version.
I hope this explains some about VWG targets and goals ;-)
Kind Regards,
Itzik Spitzen