Hi Ryan,
Thank you for the information.
I'm quite happy you gave me an opportunity to clarify some issues, since allot of VWG capabilities are not so documented, and you guys don’t even know they exist, you've created a stage to present them to you.
It is most certain that VWG is not good for all kinds of purposes, though, your reasons for not using VWG are almost completely wrong:
1. *wrong* “You Cannot use any third-party ASP.NET controls” - with VWG you CAN combine third party ASP.NET controls, by wrapping them. As for now you should wrap them manually, since we did not release an automatic wrapper creation tool, but we are going to release such tool in the near future. Anyhow, since this issue is not very documented I can't blame you for not knowing .
2. *wrong* “You Cannot integrate with other WebPages” - with VWG you CAN integrate with other WebPages in an HtmlBox and an AspPageBox, please have a look here.
3. *wrong* “You Cannot have any HTML / Javascript in your application” - with VWG you CAN combine HTML in an Html-Box and add any HTML and Java-Scripts in your Custom Controls or Custom Themes.
VWG is aimed to creating web applications as appose to web sites, this means that in case you are building an internet/intranet application i.e. Administration, CRM, ERP, BPM, ECM etc. then VWG is best for you, but if you are programming an internet web site (i.e. Commercial site, Perception site or any other public non-applicative site) then VWG is much less good for you. I believe that this should be the right distinction.
Regards,
Itzik Spitzen
|