This topic contains 5 replies, has 5 voices, and was last updated by admin 8 years, 3 months ago.
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic.
jQuery UI Widgets › Forums › General Discussions › using jqwidgets from bower even having commercial license
Tagged: JavaScript, jqwidgets
This topic contains 5 replies, has 5 voices, and was last updated by admin 8 years, 3 months ago.
Dear all
I think it is everybody clear that best practise to include dependencies in a project is by using a packaging system – for webs e.g. bower.
Till now, we included jqwidgets manually by adding the files to the project (and updating them manually). I remarked recently that I have missed that jqwidgets are also available as bower package -> so we decided to change our project to use jqwidgets also from there. So far so good…
But what I see now are the watermarks “www.jqwidgets.com” e.g. on the charts or on the jqxgrids.
Since we have a commercial license, I wonder if it is possible to let the watermarks disappear by e.g. applying the license key or any way else.
I hope your goal of offering jqwidgets as bower packages is not only for the users of the non-commercial license…
Thanks in advance for bringing light into this.
– badera
Hi Badera,
Thanks for sharing your thoughts on this matter. We will consider such ideas in the future.
Best Regards,
Peter Stoev
jQWidgets Team
http://www.jqwidgets.com/
Hi!
I would like to add a vote for badera’s post.
It will is really important feature!
Thanks!
Hi ebartashevich,
Ok. Thank you for the feedback.
Best Regards,
Peter Stoev
jQWidgets Team
http://www.jqwidgets.com/
Hi,
Any update on this one?
If I have internal bower repo then is there a way to use the licensed jqwidgets?
Regards,
Mohana
Hi Mohana,
Licensed jQWidgets version is available only from our website and our clients portal and the login is the license key which is individual.
Best Regards,
Peter Stoev
jQWidgets Team
http://www.jqwidgets.com/
You must be logged in to reply to this topic.