1) An email with JLK.tar.gz as a MIME attachment. Unzipped, the JLK folder contains 2 versions of Licenser (source code), 3 versions of SampleApp (source code), 1 command-line utility (source code) which makes your series of license keys unique to your applications, and 1 folder with developer documentation in HTML format.

2) An email with your invoice in ASCII format or zipped PostScript format, for self-print-out. (Please specify.)

3) Unlimited email support.

[ Top ]   

How difficult is it to add the JLK to my app?

It ain't difficult at all. Copy a handful of .java files and .properties files from the SampleApp folder to your application's project folder, add a few calls to the JLK as shown in the SampleApp sources, add a "License..." menu item to your menubar, and rebuild your application. That's it. (The developer documentation contains detailed step-by-step instructions.)

[ Top ]   

Can I pack extra stuff into my license keys, like for instance a 'max number of open files'?

Yes, but you have to make room in the key for this extra stuff of yours. The JLK's core encoding/decoding mechanics are pretty much carved in stone, so 'making room' is best achieved by sacrificing (and reusing) an existing piece of data -- like, say, the 3rd exp date. Sacrificing an exp date means that you'll never assign any module's exp date index to that exp date in Licenser. This said and done, you can reuse that exp date at will. For the max number of open files example given, you can stuff that number into the exp date's 'day'. Hmm... 0..31 is not that much, so better treat it as an index into an int[32] array which might look like { 0, 1, 2, 5, 10, 20, 50, 100, 500, 1000, ... } -- you get the picture. When creating a license key, you store "2000 12 <max>" into the 3rd exp date. When evaluating it, you ask the JLK for the 3rd exp date, retrieve its 'day', and index your int[32] array to obtain your max number of open files. And best of all, you still have the 3rd exp date's 'month' (4 bits) and 'year' (5 bits) at your command, for future extra stuff to crank into your license keys!

[ Top ]   

Will users be able to register my app with SampleApp's demo keys?

No. Along with the JLK comes a special Java command-line utility. When run, this utility outputs a few code lines. You add these lines to both the source code of Licenser as well as of your application, recompile, and -- presto! -- your app from now on accepts but license keys generated with your own version of Licenser.

[ Top ]   

Am I allowed to change the looks of the JLK's dialog windows?

You are encouraged to do so. The dialog windows are intentionally kept rather plain, so you don't have to pay for fancy looks you don't want, or want to add/change on your own.

[ Top ]   

Can I tell the JLK to run silently, i.e. to not display any alerts or dialogs at all?

Yes. For whatever reason you want the JLK to operate completely GUI-free, just say so at app start-up, and no alert windows or dialog windows whatsoever will appear on-screen.

[ Top ]   

Can I create license keys without using Licenser? Perhaps with a command-line utility?

Of course you can. The Licenser app is just a cover around the key creation engine, supplying radio buttons and text fields for all settings which can be burnt into a license key. The developer documentation contains example code that shows how to encode given settings into a license key. This example code -- plus three .java files copied from the Licenser folder -- is all it takes to turn any app of yours into a key creation app, be it a huge on-line ordering system, or a tiny command-line utility to be called from your 'customers'-database.

[ Top ]   

We'd like to handle storage of the license key on our own, and hand the key over to the JLK at start-up. Is this possible?

Yes. Many of you prefer to store the license infos -- along with other app-specific settings -- in, for instance, a database table at the customer's site. At app start-up, go fetch the license key (and optionally the license owner name) from your database, and tell the JLK to use those infos. The JLK will then forget about fiddling with its default license folder, and instead will use right away your supplied license infos. Note that this will disable the JLK's Registration Dialog, so it's your duty to initially store (and eventually update) the license infos in, say, your database at the customer's. Further note that this will also disable the JLK's Automatic Copy Protection mechanism.

[ Top ]   

Can I view the DevDoc before I buy?

Yes. Please contact SSS to receive a disarmed version of the developer documentation via email.

[ Top ]   

Is there a money-back guarantee?

No. The JLK comes as source code, thus there is no way to prevent fraud. Please put the free SampleApp demo through its paces to determine whether the JLK will fit your requirements. Ask SSS via email where in doubt. Request a disarmed version of the DevDoc. Buy the JLK, and receive unlimited SSS email support. But don't ask: Huh, I think I somehow don't like it. I can give it back, can't I?

[ Top ]   

Java License Kit © 1999 - 2002 Stefan Schneider Software.  All trademarks mentioned belong to their respective owners.