My project is open source (not making any $$).
Is it okay to use kendoUI for angular2 without purchasing license?
Kendo UI for Angular is a commercial product that requires a license in order to use it in production. More details can be found in Licensing and Pricing section:
http://www.telerik.com/kendo-angular-ui/
I suppose that you can get the most accurate answer if you contact Telerik sales representative directly:
http://www.telerik.com/contact
Related
We have a custom solution made up of several screens that are packaged as a customization package. We'd like to be able to lock that down so that users need to purchase a license key to use these screens. I don't want to re-invent the wheel, so I'm wondering if there are standard examples (if this has been done before) on how to integrate this with Acumatica's license system.
It is not possible to integrate with the Acumatica licensing system. We implemented our own licensing and required the license when the Acumatica license has been applied. This is indicated by PXLicenseHelper.License.Licensed
I should point out I did spend a good amount of time on this very question before we implemented licensing for our product.
I am currently working as sharepoint developer in a product based company.We are moving ahead and enhancing our products to work with react.js and typescripts and other technologies. but a major thing to notice is that we are not dependent on SharePoint anymore. i.e. our new product will work indepent from sharepoint.
So my question is, as i have a profile of sharepoint developer is it beneficial to work in that product and learn and understand React.js and Typescript ? Will it be beneficial in the future for me for the Profile of SharePoint developer?
Please reply as I am confused with this..
EDIT :
Also, Is it good to be a sharepoint developer or a .net developer with intermediate knowledge on both technologies?
Thanks
Yes it will be help full for you to develop on SharePoint online and 2016, because microsoft is introduced new platform for SharePoint SPfx. It is completely with Typescript and the React.js is recommended for this. All the best.
I have to implement product configurator in hybris platform that allowing users customization front office interface (product details).
Like changing color of product, size, make text and managing prices.
I'm looking actually for open source product desinger.
Anyone has an experience with any integrated framework or any other recommendations ?
Kind regards,
Soufiane
If you are not using SAP CPQ which is integrated with Hybris out of the box, you can have a look at openCPQ
Managing the sizes, prices etc of products is performed via the productcockpit. Changes you make here will be reflected in the Accelerator storefront. This is also extensible and customisable.
I just want to ask what improvements Microsoft has done in Sharepoint 2016 for the developer perspective.
There are several new functions in SharePoint 2016 but from a developers perspective there is nothing published already. There is also no developer preview/tool preview for SharePoint 2016. Only an IT Preview with the OOTB functionality is available.
You get much information about the IT preview at the following links
http://www.c-sharpcorner.com/UploadFile/fc34aa/new-features-vs-deprecated-features-in-sharepoint-2016/
http://en.share-gate.com/blog/whats-new-in-sharepoint-2016
https://blogs.office.com/2015/08/24/announcing-availability-of-sharepoint-server-2016-it-preview-and-cloud-hybrid-search/
http://blogs.technet.com/b/wbaer/archive/2015/05/12/what-s-new-in-sharepoint-server-2016-installation-and-deployment.aspx
Here is the list of features and improvements for Developers
Custom Web Parts
Faster Site Creation
Document Library Access
Scalability
Open Document Format (ODF)
Access Services
Project Server
Web Application Open Platform Interface Protocol (WOPI)
5,000 List View Threshold
Durable Links
New Recycle Bin
For detail information you can visit this link.
Hope this helps
-John.
Let's assume that you've created a SharePoint solution - a WebPart, a feature for a List Template, whatever - that you are planning to sell as a product.
How would you go about handling licensing of your solution?
I'm looking for some input in at least the following areas:
Code-wise:
1.1. Where do you keep the license itself? as a file somewhere? (then what happens in farms?) as a property in the property bag of the farm?
1.2. Do you implement "home-calling" - where your solution validate the license every now and then against your company's servers?
1.3. Any other best practice in this area will be welcome...
Business wise: How do you license - per user? per server? per instance (in case of WebParts or List Templates)?
Thanks.
I could tell you what we do:
We have a separate farm solution that handles trial/registration support for all our products
The license is eventually stored in the farm property bag (you have to support multiple servers)
We have a page to enter license key under the central admin solution's page
We license by front-end, you can know the number of front-end in the farm in code.
All products have a product name and the license key is a one-way encryption containing the product name. the trial support solution handles key validation.
1.1 You have to put in in the documentation and in the distribution files.
1.2 I would not do that for a sharepoint web part.
1.3 Invest in layout, documentation, support... Not just in the product itself.
Nobody will be able to answer that without knowing detailed information about your product, your market, your competitors, the alternatives, etc. Consider this book if you are serious about pricing.