The kickstarter thing and animationEngine

Hi peers, as I have been asked off list I might as well make a public statement here. If liveCode manages to become openSource, I will follow runrevs lead and make animationEngine available under a dual license. This will mean, you will get to see all the scripts I wrote for it over the past 7

1001 things to do with LiveCode - only 400 page views per day

The contributions to 1001 things to do with LiveCode have been fantastic. Thanks to everybody who has submitted their app. I feel we now have the start of a decent gallery for LiveCode. It certainly shows the range of uses of LiveCode. I'm hoping to have the time to keep the blog active even aft

Re: about the GPL version, and password protection...

Am I right that this also means that password protected plugins like, for example, the great tmControl from Scott Rossi will NOT work with the free version ? Cheers Rolf ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url t

Re: about the GPL version, and password protection...

I somehow feel that they would work, but, you wouldn't be able to ship an application that used them, unless you had the commercial license. Perhaps Scott will do what Malte is choosing to do? On Feb 18, 2013, at 9:06 AM, Rolf Kocherhans wrote: > Am I right that this also means that password

Re: Yet Another Kickstarter stack

On 02/18/2013 01:37 AM, Thierry Douez wrote: 2013/2/18 Warren Samples Hi Warren, But as I said previously, I did worked on it only a couple of hours, and had no time to make a universal tool, or test it broadly. This stack is free, open and bound to be modified by whoever... In this case,

Re: Yet Another Kickstarter stack

Hi Warren, 2013/2/18 Warren Samples > > Otherwise, except for the truncated text, does everything else works on >> Linux ? >> > > Thierry, > > Your stack seems to perform its functions perfectly well. Thanks. At least, now I know it works on linux :) > Here's an example of code along the l

Re: about the GPL version, and password protection...

Rolf Kocherhans wrote: Am I right that this also means that password protected plugins like, for example, the great tmControl from Scott Rossi will NOT work with the free version ? The GNU Public License is based on The Four Freedoms, as I outlined here on the 1st:

Re: Yet Another Kickstarter stack

On 02/18/2013 09:37 AM, Thierry Douez wrote: Hi Warren, You're talking of the bottom field, but what about the other labels, and the Finfos field where you get some datas in when moving the mouse over the graph? Are they all Ok? Well, personaly, I prefer changing the font (type or siz

Re: Yet Another Kickstarter stack

2013/2/18 Warren Samples > > The issue with the field "infos" is a result of putting multiple lines > into a fixed height which does not accommodate them on all platforms or all > users' machines. > New version online. Regards, Thierry ___ use-liveco

Re: Yet Another Kickstarter stack

Sorry, was too fast :) Only for the field "infos" (which is pretty useless in this demo) to be fully visible on Linux and some Windows. Otherwise, everything works as before. Not a big deal, but... 2013/2/18 Thierry Douez > > > New version online. > > Regards, > > Thierry > __

Re: Yet Another Kickstarter stack

On 02/18/2013 07:41 PM, Thierry Douez wrote: Sorry, was too fast :) Only for the field "infos" (which is pretty useless in this demo) to be fully visible on Linux and some Windows. Otherwise, everything works as before. Not a big deal, but... 2013/2/18 Thierry Douez New version online. R

Re: Yet Another Kickstarter stack

2013/2/18 Richmond > On 02/18/2013 07:41 PM, Thierry Douez wrote: > >> Sorry, was too fast :) >> >> Only for the field "infos" (which is pretty useless in this demo) to be >> fully visible on Linux and some Windows. >> >> Otherwise, everything works as before. >> >> Not a big deal, but... >> >>

Re: about the GPL version, and password protection...

Rolf Kocherhans wrote: Am I right that this also means that password protected plugins like, for example, the great tmControl from Scott Rossi will NOT work with the free version ? Correct. The free version will not contain any of the code that deciphers passwords, which means it cannot open

Re: about the GPL version, and password protection...

Is that true? Isn't the password protect to stop you from looking at the scripts? Most people won't want to look at the scripts. Any attempts to decode the password should fail silently. On Feb 18, 2013, at 2:18 PM, "J. Landman Gay" wrote: > >Correct. The free version will not contain any of t

Re: about the GPL version, and password protection...

No it's just password protected ones it can't run. The GPL version can't have the password protection code otherwise it would risk everyone's commercial code. Even the enterprise source version will not have that code open but as an object file/library. -- M E R Goulding Software development se

Re: about the GPL version, and password protection...

Colin Holgate wrote: > Isn't the password protect to stop you from looking at the scripts? Right, and the GPL requires sharing the source, so password protection isn't relevant in any work governed by the GPL. Those who want to protect their code can use the Commercial Edition. -- Richard Ga

Re: about the GPL version, and password protection...

As I mentioned, someone may be doing a personal project, and are not going to be releasing their app at all, should it then matter if it uses non-GPL code? Also, suppose someone makes a graphics utility plugin, that is solely used for creating graphics (non of its code will be in the final app),

Re: The kickstarter thing and animationEngine

That's great Malte. Th GPL version will have some great plugins available freely already between SQLYoga, AE, Jan's libraries and Andre's libraries. I'm still considering my position on this but it's likely I'd gradually move to dual licensing too. This GPL version really will be a massive boon

Re: about the GPL version, and password protection...

On Feb 18, 2013, at 11:33 AM, Colin Holgate wrote: > I'm arguing that protected plugins should function just fine in the GPL > version of LiveCode. The password protection routines won't be needed, > because the user won't be attempting to look at the scripts in the protected > plugin. The

Re: about the GPL version, and password protection...

On 19/02/2013, at 6:23 AM, Colin Holgate wrote: > Is that true? Isn't the password protect to stop you from looking at the > scripts? Most people won't want to look at the scripts. Any attempts to > decode the password should fail silently. The engine needs to decode the scripts to execute t

Re: about the GPL version, and password protection...

Well, there's your problem then! Hopefully there will be a way for plugin makers to create plugins that can work for the GPL version, if need be by using a different way to protect their code. On Feb 18, 2013, at 2:36 PM, Monte Goulding wrote: > > >The engine needs to decode the scripts to ex

Re: about the GPL version, and password protection...

On 19/02/2013, at 6:33 AM, Colin Holgate wrote: > As I mentioned, someone may be doing a personal project, and are not going to > be releasing their app at all, should it then matter if it uses non-GPL code? I don't believe the GPL applies until distribution. > > Also, suppose someone makes

Re: about the GPL version, and password protection...

On 19/02/2013, at 6:41 AM, Colin Holgate wrote: > Well, there's your problem then! Hopefully there will be a way for plugin > makers to create plugins that can work for the GPL version, if need be by > using a different way to protect their code. Ideally most will see the advantage of dual li

Re: What do you want to contribute?

it is, but I don't think we should settle for that, either. On Mon, Feb 18, 2013 at 1:13 AM, Geoff Canyon wrote: > Here's an interesting real(ish) world example: > http://www.leancrew.com/all-this/2011/12/more-shell-less-egg/ > > The goal is to find the ten most common words in a text file. > >

Re: What do you want to contribute?

and as long as I'm thinking about it, the possibility of (more readily) making english-like syntax more so makes open sourcing much more interesting - as long as I don't feel like I'm coding in COBOL when we're done. On Mon, Feb 18, 2013 at 3:04 PM, Mike Kerner wrote: > it is, but I don't think

Re: What do you want to contribute?

Hmm... I think your code using current syntax is actually clearer than the proposed syntax. I definitely don't like adding meaningful comma given the confusion with items... You could replace that with a semi-colon or new line though. -- M E R Goulding Software development services mergExt -

Re: What do you want to contribute?

OK... so Geoff I've put you down on the list ;-) Actually I think you and Alex T might get along with the "each in " syntax. Also Malte... I've added that your dual licensing AE. ENGINE - Mobile sockets - engine (Monte) - Nested behaviors so you can set the behavior of a behavior (Monte) - Get

Re: about the GPL version, and password protection...

Hi Monte, I'm still somewhat confused by GPS licensing for plugins, especially helpers like my lcStackbrowser. It's purely a dev tool, nothing to be included in a standalone. I'm under the impression I cannot charge for it under the GPS license. In the scenario where debs use the gel version and on

Re: about the GPL version, and password protection...

On 19/02/2013, at 12:03 PM, Peter Haworth wrote: > I'm still somewhat confused by GPS licensing for plugins, especially > helpers like my lcStackbrowser. It's purely a dev tool, nothing to be > included in a standalone. I'm under the impression I cannot charge for it > under the GPS license. In t

Re: about the GPL version, and password protection...

Peter Haworth wrote: I'm still somewhat confused by GPS licensing for plugins, especially helpers like my lcStackbrowser. It's purely a dev tool, nothing to be included in a standalone. I'm under the impression I cannot charge for it under the GPS license. The GPL does not place any restriction

Set default keyboard layout (for other language) for a field

I've just created a stack with fields that will contain text in Esperanto. I have a keyboard layout ("Esperanto-sc") installed on my Mac that allows me to type special accented Esperanto characters (eg, "ĉ", "ŭ"). If I click in a field and *then* change the keyboard layout from (the default) "Austr

Re: What do you want to contribute?

yeah, I wasn't happy with that syntax as I was typing it. Part of the beauty of being able to create/share syntax is that others can improve on what you come up with, and only the good syntax survives into general usage. Maybe this would be better: put file filePath with all non-alphabetic char

Re: Set default keyboard layout (for other language) for a field

Hi Jonathan, We did this for a client. We have a working Mac solution. Currently, the Windows solution works only in theory but I'd be happy to investigate further. Contact me off-list of you're interested. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering H

Re: What do you want to contribute?

Hmm... is w something more than a string... how could it have a count? SQL uses distinct... might be good to use that... commonest??? ;-) Also... why are we dropping repeat? Here's something nice: ordered repeats ;-) How about: put file filePath into fileString filter the characters of fileSt

Re: Set default keyboard layout (for other language) for a field

Saluton, Jonathan! On 19/02/2013, at 12:39 PM, Jonathan Cooper wrote: > I've just created a stack with fields that will contain text in Esperanto. > I have a keyboard layout ("Esperanto-sc") installed on my Mac that allows > me to type special accented Esperanto characters (eg, "ĉ", "ŭ"). I spe

Re: [OT] vote for my app...

A couple of you voted for my app, thanks. The top six in each category go through to the finals, and right now we're in seventh place, needing 10 notes to catch up with sixth place. The voting ends today! If you were thinking of voting, right now would be a very good time to do so! Thanks. Here

Re: Set default keyboard layout (for other language) for a field

An alternative: On 19/02/2013, at 12:39 PM, Jonathan Cooper wrote: > Or, failing that, to > have Livecode automatically set the keyboard layout as soon as the field is > opened? That may not be always reliable, as in some systems - like the Mac - the user has to explicitly 'enable' the keyboar

Re: What do you want to contribute?

w is a string, but I'm assuming that in context, syntax like "count of" would make sense syntactically, and that the language could make it work. yeah, commonest sucks, but I didn't want to push it by going with two words like "most common." Also, given how specific the use case is, it would likel

Re: Set default keyboard layout (for other language) for a field

Jonathan, I couldn't resist, and ended up trying this out myself: On 19/02/2013, at 3:42 PM, Igor de Oliveira Couto wrote: > For an more polished user experience, you can try developing a script that is > more forgiving when the user mixes upper- and lower-case 'x's, like "Cx" and > "cX". You

Re: Set default keyboard layout (for other language) for a field

> > From: Igor de Oliveira Couto > Date: Tue, 19 Feb 2013 14:18:17 +1100 > Saluton, Jonathan! > On 19/02/2013, at 12:39 PM, Jonathan Cooper wrote: > > I've just created a stack with fields that will contain text in > Esperanto. > > I have a keyboard layout ("Esperanto-sc") installed on my Mac