|
Gateways symptoms |
|
Itzik Spitzen's blog
|
By Itzik Spitzen on
1/1/2008
|
|
|
|
There are 2 common cases on which gateways do not work correctly, in this forum entry I'll try to characterize them and help you on fixing them.
|
 |
|
|
More...
|
|
|
Versions Revisions and Releases |
|
Itzik Spitzen's blog
|
By Itzik Spitzen on
12/27/2007
|
|
|
|
Since I'm not convinced that everyone is familiar with VWG versioning procedure and version numbering system, I would like to share some important information with you regarding our versions, revisions, releases and roadmap, and hopefully make them clearer.
|
|
|
|
|
More...
|
|
|
Gizmox R&D Team Starting To Work |
|
Guy Peled's Blog
|
By Guy Peled on
8/3/2007 7:41 AM
|
|
|
|
As you might read in my last post we are deep in the process of developing Gizmox the company behind Visual WebGui. We have finished the work on our office and we have all we need to start working.
Last week we welcomed our first R&D recruitments which are Itzik Spitzen as VP R&D and Tamir Zaslavsky as our first R&D developer. Both our new employees came from our community...
|
|
|
|
Comments (0)
|
More...
|
|
|
|
|
|
Customizing the Visual WebGui design templates |
|
Guy Peled's Blog
|
By Guy Peled on
12/11/2006 9:39 AM
|
|
|
|
Visual WebGui is fully xsl driven, which means that every component has an xsl that renders its presentation on the browser. The Visual WebGui developer uses the SDK abstraction layer defining controls and their relations, where as the rendering is done through a set of dedicated xsl templates that render the components. This means that you can take an existing application and use different xsl templates to create a different look and fell.
|
|
|
|
Comments (2)
|
More...
|
|
|
ASP.NET and Visual WebGui sharing the same application context. |
|
Guy Peled's Blog
|
By Guy Peled on
12/11/2006 9:37 AM
|
|
|
|
Visual WebGui is actually based on the core objects of ASP.NET but implementing a different pipe line. This means that a Visual WebGui application project is actually an extended ASP.NET application project to support the new pipe line. ASP.NET entities can be created the same way they are created on a regular ASP.NET application project. This also means that the Visual WebGui entities and the ASP.NET entities are sharing the same application context.
When you use the Visual WebGui Context.Session object you are actually refereeing an object that is hosted with in the ASP.NET session object and the same applies to the Context.Application which is actually an object hosted with in the ASP.NET application object. You can easily refer to the original ASP.NET objects by using the HttpContext.Current.Session or HttpContext.Current.Application but by referring directly to those object you loose the ability to also deploy a Visual WebGui as a client application which is a featu ...
|
|
|
|
Comments (5)
|
More...
|
|
|
Design differences between Visual WebGui and WinForms |
|
Guy Peled's Blog
|
By Guy Peled on
12/11/2006 9:32 AM
|
|
|
|
The main difference between a WinForms application and a Visual WebGui application is the execution context. Visual WebGui being a platform for building web applications, is a multi-threaded environment that needs to serve many users. While a WinForms application serves a single user on a dedicated machine.
A major built in difference between WinForms and Visual WebGui is the ShowModal method of the form object which in WinForms halts the execution of the code until the window is closed. In Visual WebGui the ShowModal method returns immediately and the developer must attach to the closed event to continue execution after the window is closed. This actually means that in Visual WebGui a modal dialog is only modal on the client side.
A side from the ShowModal method, designing a Visual WebGui application is pretty much the same as designing a WinForms application.&a ...
|
|
|
|
Comments (0)
|
More...
|
|