Re: Licensing Problems

[sanke]

use-livecode-ow...@lists.runrev.com schrieb:

Your mail to 'use-livecode' with the subject

 Re: Licensing Problems

Is being held until the list moderator can review it for approval.

The reason it is being held:

 Message body is too big: 134636 bytes with a limit of 30 KB

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

 
http://lists.runrev.com/mailman/confirm/use-livecode/7d7bf0de10bb60c04b933bc0e31d3e589852cfc8



I have deleted the embedded image of my original post and resend the 
mail by including the text of the image instead of the graphic.


Here is my original post:

These licensing problems have been discussed and investigated on 
Bugzilla since December 16, 2015, or even earlier.


It would be a good idea for you to join the discussion about bugs 
16602 ()

and 16468 ()
to direct more attention to these licensing and re-licensing problems. 
At present only 2 or 5 Livecode users participate.


The problems IMHO are most likely caused by an inadequate code used to 
control the validity of licenses under the new subscription-based 
marketing model that prevents the building of closed-source 
applications once a license has expired.


I experienced different kinds of such licensing problems which I have 
described in my contributions to the bug reports.


Here is an example that I also discussed with Customer Support:

During the discussion about the two bugs I tried to get an 
offline-licensing file for LC 6.7.8 for testing purposes (I informed 
you about this.) and observed that my personal Livecode account had 
been tampered with - without any prior information - very much 
restricting the access to files under my Commercial license. You 
responded to my question with the rather "cryptic" information that 
my two licenses had been "merged", but never explaining explicitly 
why and how this could have been necessary and what consequences this 
would entail. You did also *not* respond to my request to correct the 
entries for my Commercial license (clearly still running until August 
15 this year), and there is also no correction from your side 
following a second and third request.


In January the countdown for my Commercial 6.7.8 licence began, which 
ended - see the image below - on Jan 28.


Text of the deleted image:
"LIVECODE License File Expiring
6.7.8
Your current license file is about to expire.
Please connect your computer to the internet to fetch a new license file.
0 days remaining"

Date of the snapshot: Jan 28, 2016.



This was strange as I have got a Commercial license still running 
until August 15, 2016, but according to Support my two licenses (Indy 
and Commercial) had been somehow "merged" - thereby restricting my 
access to Commercial licensing files to versions 6.1.3 and lower.


After several urgent requests to correct the data of my personal 
Livecode account the data have been finally corrected this week - 
after waiting for a month - with the interesting result that I have 
atually now got *two* Commercial licenses. I will not go into details 
about these 2 commercial licenses, but the background is like this:


Reacting to the intense "Indy-lock-in-the-price"-campaign by Kevin I 
subscribed to a new Indy license in July 2015.- I was in no need of 
special extra benefits at that time; as my present Commercial licence 
was still running for another year. My intention at that point was 
simply to support the maintenance, development, and improvement of 
LiveCode in the same way as before with my contributions to the 
Kickstarter campaign in 2013. My new Indy license would then be valid 
- after the expiration of my Commercial license on August 15, 2016 - 
from August 2016 to August 2018.


Apparently the fact of two consecutive licenses caused problems for 
Support, probably because the co-existing of two licenses could not be 
adequately reflected within the framework (layout and programming?) 
of  personal Livecode accounts. At least there was an indication of 
this sort of problems in a feedback from Support. Support then solved 
the problem by "merging" my two consecutive licenses, but causing at 
the same time the troubles I have reported above - and without 
explaining what this "merging" would entail and why this "merging" 
should be necessary.


Shortly before the data of my personal Livecode account had been 
corrected this week, I have now cancelled my new extra Indy license 
with the main intention to help "de-merge" the entangled Indy and 
Commercial licenses. Cleverbridge has meanwhile verified the 
cancellation of the Indy license, and Livecode is at present 
contemplating how (and if) they could refund the sum of € 534 which I 
paid for the Indy license running from August 2016 to August 2018.


After the 

Free BasicClock desktop clock for OSX

[Howard Bornstein]

So many clocks today still employ the flip-clock or 7-segment LED display
aesthetic that is at least 20 years old. Given that we now have high
resolution displays and very high-quality fonts available, I wanted to make
a simple clock that took advantage of these improvements as an alternative
to the “retro” clocks that are mostly available.

The clock itself is basic—just time, day, and date. It’s designed to sit in
the corner of your screen and float over everything else.

But you can modify the *look* of the clock in many ways, by using different
fonts and by modifying the clock and background colors. Other visual
options include adding a border, using rounded corners, drop shadows and
inner shadows.

The clock is also infinitely resizable so you can make it any size you need
to fit in your work area.

Because there can be so many visual options, there is also a mechanism to
save your favorites designs and call them up later.

You can see the features of BasicClock here: BasicClock Read Me.pdf


and download it here: BasicClock V2.04.zip


Note that you might have to “allow” this clock to run in the Security &
Privacy control panel if you have Gatekeeper running on your Mac.

BasicClock is free and currently runs only under OS X.

Enjoy.

(BasicClock was inspired by the Clearview desktop clock by Hugh Senior.)
-- 
Regards,

Howard Bornstein
---
www.designeq.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Licensing Problems

[David V Glasgow]

Couldn’t say if it is really exactly once a month, but it is something like 
that :((

> On 14 Feb 2016, at 1:24 pm, Charles Szasz  wrote:
> 
> David,
> 
> Thanks for your comments! Do you do a manual activation for each month for 
> licensing?
> 
> Sent from my iPad
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Cue sheet generator and livecode server

[Michael Doub]

Hello all.   For all of you cyclists out there that use RideWithGPS i 
have written a simple app that creates nicely formatted cue sheets.   
Help yourselves.  It can print directly, make a PDF or save a CSV file.


https://www.dropbox.com/s/13jc0tgynilonpt/ridewithgps_cuesheets.livecode?dl=0

But the real reason for my post is to ask some questions about livecode 
server.   I was thinking about how I might adapt this app to work from a 
web page.In my app, I have two substacks that are used to format the 
output of the PDF.   Am I correct to assume that I can have a livecode 
server script load a normal stack that includes substacks and produce a 
pdf file?


If this is doable, I have a web question.   How do you manage the pdf 
files?   Presumably each has a unique name that is passed to the browser 
so it can be downloaded, but how do you manage the cleanup so the pdfs 
are deleted?


This is first attempt at doing any on the web, so any coaching or best 
practice advice would be appreciated.


Regards,
  Mike


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Licensing Problems

[Peter Bogdanoff]

I've also had to do a periodic manual activation on one machine.

Peter Bogdanoff 

> On Feb 14, 2016, at 5:04 AM, David V Glasgow  wrote:
> 
> Charles,
> 
> I have had repeated problems with my Indy license expiring every month.  
> 
> http://quality.livecode.com/show_bug.cgi?id=16720 
> 
> 
> I have to download a new activation file for my specific version (7.1.0) each 
> month. 
> 
> This is  pain, but otherwise I find 7.1 to be pretty good.  I also had an odd 
> memory leak in 6.x but it isn’t evident in 7.1
> 
> Cheers,
> 
> David G
> 
> 
>> On 14 Feb 2016, at 12:54 pm, Charles Szasz  wrote:
>> 
>> Has anybody encountered Indy licensing problems?  My Indy license does not 
>> expire until July or August of 2017. I can no longer use LC 6.1.2 or 6.1.3 
>> due message that my license has expired! LiveCode has acknowledge there is a 
>> problem but has not yet fix this problem. 
>> 
>> I am reluctant to use higher LC versions based on my experience with LC 
>> 6.6.5, which was recommended by tech support as a stable version of LC. I 
>> found that 6.6.5 leaks memory, which makes it untenable for my projects. 
>> 
>> 
>> Sent from my iPad
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Licensing Problems

[Charles Szasz]

David,

Thanks for your comments! Do you do a manual activation for each month for 
licensing?

Sent from my iPad
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Licensing Problems

[David V Glasgow]

Charles,

I have had repeated problems with my Indy license expiring every month.  

http://quality.livecode.com/show_bug.cgi?id=16720 


I have to download a new activation file for my specific version (7.1.0) each 
month. 

This is  pain, but otherwise I find 7.1 to be pretty good.  I also had an odd 
memory leak in 6.x but it isn’t evident in 7.1

Cheers,

David G


> On 14 Feb 2016, at 12:54 pm, Charles Szasz  wrote:
> 
> Has anybody encountered Indy licensing problems?  My Indy license does not 
> expire until July or August of 2017. I can no longer use LC 6.1.2 or 6.1.3 
> due message that my license has expired! LiveCode has acknowledge there is a 
> problem but has not yet fix this problem. 
> 
> I am reluctant to use higher LC versions based on my experience with LC 
> 6.6.5, which was recommended by tech support as a stable version of LC. I 
> found that 6.6.5 leaks memory, which makes it untenable for my projects. 
> 
> 
> Sent from my iPad
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Licensing Problems

[Charles Szasz]

Has anybody encountered Indy licensing problems?  My Indy license does not 
expire until July or August of 2017. I can no longer use LC 6.1.2 or 6.1.3 due 
message that my license has expired! LiveCode has acknowledge there is a 
problem but has not yet fix this problem. 

I am reluctant to use higher LC versions based on my experience with LC 6.6.5, 
which was recommended by tech support as a stable version of LC. I found that 
6.6.5 leaks memory, which makes it untenable for my projects. 


Sent from my iPad
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Neglected graphic capabilities

[RM]

I attended the conference in Edinburgh when LiveCode 4.0 was launched, and
remember being wowed by the new graphic effects, which really are a 
great addition.


I do feel that these have, subsequently been overlooked; even to the 
extent that

people are asking questions of this sort:

http://forums.livecode.com/viewtopic.php?f=10&t=26546

I also wonder why more is not made of these very useful capabilities on the
LiveCode website and thereabouts?

Richmond.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode