Visual WebGui Blog
ASP.NET Web & Mobile HTML5 Application Delivery
-
Silverlight development tips (part 1)
As you guys probably know, we (Gizmox) are working on an alternative UI layer for Visual WebGui, that will be based entirely on Silverlight and as the chief architect (and CTO) at Gizmox the hard core work was on my shoulders. When at first I look at Silverlight, I admit that I did not get what the fuss is all about, but just to make things right, I now get it.
-
Silverlight over VWG: lets you develop using simple WinForms API, and eliminates the restricting client dependency resulting in an ultra powerful UI.
Silverlight MP Barak Cohen, refers to the new possibility as more powerful UI for Silverlight, and enabling veteran, known and tested, best of breed (MS's ) programming API and methodologies for new technology development. Read more from Barak's blog: here. -
How to turn simplicity in programming Line-Of- Business AJAX into productivity ,and now, the demo
Here it is. Follow the 4 simple steps and you are going to build an AJAX explorer in 10 minutes. Yes 10 minutes, without all the web designing hassle and complexities.
You are going to use WinForms API and methodologies, debug with standard tools, and magic, compile and your application will be running on web, from a single layer source code. (8 minutes video is available here)
This is how it goes:
1. Create a new application ( you need Visual Studiou, and Visual WebGui installed, you can download free from here)
-
Simplicity is my message to you fellow developers, and I am not only preaching, I am actually doing!
AJAX has been breaking new grounds almost every day, with over 200 AJAX frameworks, there are plenty of options to choose from and one might say too many. Most of the AJAX frameworks provide you with browser extension libraries that will help you utilize the browser and interact with the server in a more productive way. What they are trying to do in most cases is to provide larger building blocks to achieve your goals by abstracting the calls to the browser API and to the server. The last is a significant improvement over the plain vanilla browser coding but you are still writing your application in a very poor environment with very poor developer tools and your end result is a JavaScript application vulnerable in terms of security, manageability and your IP protection.
