Hi again guys,
Michael:
Royalties are for premium products only, this means that unless you are using premium products you don't have royalties fee. When premium extensions become ready to release, they will be added to the products section on the web site and they will be delivered with a license to the end customer based on the deployment model.
OEM license is required when you develop a "shelf product" (rather than develop a specific project to a customer or use it for an internal system); then the OEM licensing will entitle you to embed visual WebGui SDK within this product and then the fee will be determined according to your needs (especially according to the volume/distribution). Using VWG within specific customer’s projects will not require commercial license only if your customer understand the meaning of LGPL fully, knows that the infrastructure is based on LGPL and is ready to accept the terms; in any case that the customer requires full proprietary, then a per seat developer license has to be purchased for any of the application developers/maintainers.
In general, I truly believe that you guys are ready to pay for licensing as required, and that it is of your interest to support the VWG solution and to push is forward until it becomes the top leading solution for building business apps over the web.
We are still thinking over the business model, examining it on a regular basis and making adjustments to it according to the market response and that is why it does change from time to time and is still subject to change.
As for early adopters, we will add a mechanism to enable partial licensing for any control which was previously free and now it is not. This means that you will be able to deploy the ScheduleBox for example but not the RibbonBar even though they share the same Office extension assembly.
HappyFirst:
As for using the LGPL or the early adopters’ free license, you can deploy on as many domains as you like with any number of CPUs freely.
In order to be released from the LGPL you will have to purchase a commercial license (per developer seat) and then you can develop projects freely and deploy an non-LGPL solutions to your customers, not having to tell them you use an open source library.
As I wrote before, any other premium will be charged on separately as per deployment (royalties) according to the licensing of each premium (per domain for SDK extensions such as Office or per CPU for server extensions such as Scalability server).
Let me know if you still have questions.
Regards,
Itzik Spitzen