Do I need a license to use CKEditor5 to build internal admin applications? - ckeditor

I am looking to build an internal admin application which needs to have the ability to add some rich text. I am looking to use CKEditor5 and wanted to understand how the licensing works.
Do I need to get any license if I am not looking to use any premium features right now ? And maybe in future if I decide to use premium features then only think about purchasing a license ?
Tried going through the license but wanted to be sure before using it

Related

How to use PowerPoint templates as theme in Data Studio?

I want to create a dashboard on Google Data Studio using a template provided by my organization but I can't find any helpful resource to do that so I'm tempted to think that's not even possible. I tried to use "Extract theme for image" option in GDS but didn't work properly since it just tries to emulate the colors from the image and not the template itself.
Any advice or suggestion will be much appreciated.
Unfortunately, there is no way to achieve this.
Although last versions of Google Data Studio contains resources to allow it to present dashboards as it were a presentation software, I don't think it is intended to offer advanced resources for this task, neighter make it compatible with other presentation softwares (especially if you're talking about third party software, as Microsoft PowerPoint).
The best you can do is to create your own dashboard, and try to mimic your company's provided template.
you could also use an image as theme, it will at least uses the colors of you company as you can see in the image below.
And that's unfortunally what you can do with it, and for powerpoint themes, you could also use Microsoft Power bi which is way more advanced that Google Data studio

GUI customisation support in Reporting/OLAP servers

I have been researching OLAP servers such as Tableau, Jasper, BIRT iHub, etc.
but it appears that none of them provide reasonable support to customise the
user interface. All of them use the browser as the rendering system but
changing their default screens or "viewer" windows is not encouraged
(possible?).
I DO NOT want to write a full fledged J2EE application and drop JAR files
in the WAR. I have done it in the past and was expecting improved support
for this type of requirements.
Any pointers?
Thanks for the additional info.
May be the Swiss tool, icCube, can help you. icCube ships with an in-memory OLAP engine and built in web reporting application. You can embed the software seamless in other web applications, so adjusting the look-and-feel and customer branding is relatively simple.
As the reseller of icCube in The Netherlands, I have implemented icCube at several clients that were looking for an affordable dashboard solution that could completely blend into their product. Based on our customers' enthusiasm I think I can say we succeeded in that.
You can view some live demo's on our website. Also tons of info is available at icCube´s site. If you want more, I can show you some embedded examples through skype if you want to.
Hope this has helped.

WP7 - selling extensions

I'm trying to create some application for Windows Phone >= 7.1
During plannin my work and specyfiong technical requirements I've come across one problem.
I wan't to have free application with basic functionality. And then it should be extendable with some non-free extensions (dlls?, databases?, SaaS?)
Is it possible at the moment to use some MS api/app/etc. to be able to publish such extensions and sell them? What is the best way to do this if there is more than one solution?
Thank you for any help.
As of right now (June 2012), in-app purchases are not supported. Your only choices, then are being a paid app and supporting trial mode.
The only way you can do this at present is to handle the additional purchases yourself.
You'd have to set up a website which customers could create an account on and purchase extensions through, then have them also log into your app with those account details to determine what additional data to download or functions to enable.
You could be smart and include the website functionality into your app with a browser control. Take a look at the Amazon Kindle app for an example of how they accomplish it.

magento osl license allowances

Im interested in providing part of magento ecommerce as a SAAS solution. However, it would be great to get some clarity around the osl license.
I realise that distributing that actual software requires me to open the source. However, in a SAAS environment, surely I can charge for the software service? As long as I release all changes to the core code etc?
How about using the XML API to provide data - I guess thats ok too?
What about if I decide to let the user have the source code? what would I be obliged to do then? let them have it? release all changes?
Anyone have any experience with this? ps I realise you may not be a lawyer ;]
Cheers
Ke
What I would do is charge the user for the hosting. You can sell your customizations as you please as they technically are not subject to the Magento license.
I would stay away from making changes to the "core" code and instead build off of them. That way you are not selling modified versions of the core software (which would kill your ability to easily upgrade the system).
You are allowed to license your extensions however you please so you would not have to worry about the open source model.

Suggestions for technical approaches to Licensing a CRM4 (ISV) add-on

The team I'm working with have created a CRM4 add-on which encapsulates 'standard' CRM customisations (such as modifying existing entities, adding our own custom entities), reports, plug-ins, and our own web pages (in IFrames) and web services. All pretty typical stuff.
I'm writing all the requisite installation code to simplify / automate the install process so that our ISV add-on can downloaded and trialled by anyone, but have been asked to think of appropriate way restrict functionality - to encourage people to purchase a license.
I'm not that familiar with the concepts/best practices/pitfalls when it comes to the 'licensing' of .net apps (especially CRM4 add-ons) so am asking you if you have any suggestions. We're looking for something fairly simple, and should be reasonably 'crackable', since we believe that having to enter a license code is generally a PITA.
Does the CRM API have anything to offer the ISV developer? (I see that one is able to nterrogate the License entity, but I'm assuming that this is for the CRM license itself)
Are there any existing code samples / projects / frameworks that are appropriate to use or implement?
I'm tempted to create a Registry Key upon installation of the add-on which, if after a month the correct license key has not been entered, will restrict functionality. Is this the best way to do this? Have you seen any other add-ons do it differently / better?
In terms of restricting functionality, I'm thinking of throwing InvalidPluginExecutionExceptions. Surely there must be a more 'graceful' way to do this?
All thoughts and suggestions appreciated.
Regards,
Peter.
My thoughts:
Yes, you can query the License entity to get the number of licensed users, which is a common license type from what I've seen. Lots of 3rd party vendors charge by the number of licensed users, regardless of how many of those users actually use the customization. I try to stay away from these because the license costs are often prohibitive for enterprise deployments.
Not that I know of.
I like this option, and have seen at least one 3rd party tool use this method. They allow you to declare the license key in your .config file, and if their runtime doesn't find it there it checks a known registry key. The tool comes with an app that registers the license key in the registry for you. I'd be careful to test and make sure your custom code can read the registry in a least-privilege environment.
Definitely not graceful to throw exceptions, but it does prove your point. :) Other than that, just outright skipping your code is another possibility, although that could have data implications. If you must throw exceptions, I would suggest trying to run some javascript on form load of your entities that warns the user that their license is expired and a save will result in an error. Some more nefarious schemes could include Thread.Sleep, kinda like the old shareware nagscreens. :)
Another idea - can you set up an Enterprise IFD deployment so you can give customers remote access to your demo, including their own demo organization? This depends on your audience, but your customers may not have the luxury (time, dev environment) of downloading and installing your trial. They may just want to see it in action - once you qualify the sale maybe you offer free remote installation and not spend so much time on a flawless setup package? Again, depends on your audience and the volume of licenses you expect to sell. Technically, you could dynamically provision organizations using the SDK and make the online trial process completely automatic. Of course this is a big investment, but allows you to maintain absolute control over your demo/IP.
Hope that helps!

Resources