The Robot speaking here ;-)
Thanks for the clarifications. I already understoud the reason behind, exactly as you explained, but for me, there are 2 classes of programmers addressed by VWG.
First, the programmers working for a company selling software developments and secondly programmers working for a company who makes other business and who are in charge to code for internal use.
The first group will for sure be highly interested in every aspect of the customization. The second group is interested in fast developments, the target is to bring solutions to business problems in a fast and easy way, often because the development is a single shot.
I belong to the second group, I have a Visual Studio programmer exprerience. I never wanted to invest time to learn Web publishing technology(which is frustrating and ever changing. VWG brings a great solution to that).
So those programmers know how to solve the business cases, but are missing components to do it in a "web enabled" development manner. Here comes VWG in play.
Having either out of the box, either an easy and functional wrapper, either VWG ready components to buy is really the missing part.
As a sample, currently I'm trying to create a VWG Gantt component out of some existing component, but without success so that it ruins the speed and ease of WVG.
I presume (and hope) my opinion is reflecting the case of many others.
I'm a big fan of VWG, which is a great product that I'm following since months. The energy put in it is easy to feel, and I which you a brilliant success worldwide.
Posted by lmp014 on Friday, June 26, 2009 4:46 AM