Re: How to compile in earlier versions using new keywords?

[Monte Goulding]

The chained behavior solution needs any version specific code you want to be 
moved to a behavior for that version and uses the lack of script compilation as 
a feature. I prefer it to the string based solutions because the execution is 
faster.

Cheers

Monte

Sent from my iPhone

> On 10 Apr 2016, at 8:57 AM, -hh  wrote:
> 
> How does your "chained" solution translate to that situation?
> [Of course, the "string" solutions of Bill and Jaqueline work here.]

___
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: Standalone (and stack in IDE) getting larger on each launch

[jameshale]

setting the destroystack true or false had no effect.
I tried to create a test stack to replicate the issue but couldn't which
implies I guess that it is something in my stack doing it.
For now I have moved the sizing handler further up the start chain and at
least I have kept the increase constant. This could mean that somewhere
between the new sequence and the old the increase in stack size is taking
place.
In any case I will leave this for now and come back to it later.
Thanks for the suggestions.
If I do find out what it is I will post again.

James



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Standalone-and-stack-in-IDE-getting-larger-on-each-launch-tp4703211p4703282.html
Sent from the Revolution - User mailing list archive at Nabble.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: How to compile in earlier versions using new keywords?

[-hh]

What I had in mind with that is a script part of the following
form that should (but doesn't) compile in LC 6/7/8:

if char 1 of the version > 6 then
repeat for each trueword w in str
  ...
end repeat
else
repeat for each word w in str
  ...
end repeat
end if

How does your "chained" solution translate to that situation?
[Of course, the "string" solutions of Bill and Jaqueline work here.]



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270p4703281.html
Sent from the Revolution - User mailing list archive at Nabble.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: How to compile in earlier versions using new keywords?

[Monte Goulding]

One solution I have used for this is chained behaviors:

on mouseUp
   put GetWord(fld “IN”,1) into fld “OUT”
end mouseUp

— parent behavior won’t compile in LC 6
function GetWord pText, pWord
   return trueword pWord of pText
end GetWord

— grandparent behavior
function GetWord pText, pWord
   return word pWord of pText
end GetWord

> On 9 Apr 2016, at 11:11 PM, -hh  wrote:
> 
> Is there a way to *compile* the following script in LC versions before 7?
> 
> on mouseUp
>  if char 1 of the version > 6 then
> put trueword 1 of fld "IN" into fld "OUT"
>  else put word 1 of fld "IN" into fld "OUT"
> end mouseUp
> 
> The use of the try structure doesn't help, the script doesn't even
> *compile*. The same with "segment" and other new terms of LC 7/8.
> 
> More generaly, is there a way to "hide" some script blocks so that 
> the compilation in all earlier versions handles the block as comment? 
> 
> 
> 
> 
> --
> View this message in context: 
> http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270.html
> Sent from the Revolution - User mailing list archive at Nabble.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


___
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

POLL: LiveCode Server use

[Richard Gaskin]

I have a poll in the forums to learn more about how people use LiveCode 
Server.  Even if you don't use it, that's useful to know and there are 
options for that too.


Please consider taking a moment to participate in the poll:


The results may be of general interest, and in my case I have some tools 
I'm building to help manage LC on my servers and this will help me 
better anticipate if it's worthwhile generalizing some of them for 
others to use.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.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: How to compile in earlier versions using new keywords?

[-hh]

For a while, LC 7 and 8 where linked in the sense, that, besides
widget syntax, new keywords/functions/properties of LC Script
were added to both.
Actually they are already unlinked (in this sense), for example
by the new "replace styled" function. This means we have the
same problem as described in the first post of this thread if we
wish to use one script for both LC 7 and LC 8, and we may have
already to write three versions if we wish to use it for LC 6/7/8.
>From my point of view this is necessary if new features of LC 7
and or LC 8 can compensate a little bit their 'loss of speed'
compared to LC 6. My meanwhile more exact question is
whether there are (more) *easy* ways for that.


Richard Gaskin wrote
> -hh wrote:
> 
>   @William
>  > A nifty workaround. But this means, that we have to make two
>  > script versions, and even three versions as soon as LC 8 is
>  > "unlinked" (wrt compatibility) from previous versions.
> 
> What does "unlinked" mean?
> 
> As with most well-designed software, the new version is designed
> to be a superset of features found in older versions.
> 
> If you find things that run in v7 but not v8 that would be a bug
> that the team would want to address ASAP.





--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270p4703278.html
Sent from the Revolution - User mailing list archive at Nabble.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: How to compile in earlier versions using new keywords?

[Mark Wieder]

On 04/09/2016 07:47 AM, -hh wrote:



I have an idea, that may be more comfortable:
If we could have a switch in LC 7+8 for parsing/compiling
that temporarily disables one of the commenting methods,
for example "//", we could use "version blocks" in new scripts:

// usual comment line for all versions
set slashCommentsOff to true
  // ... code for versions 7/8 only
  // ... code for versions 7/8 only
set slashCommentsOff to false
// usual comment line for all versions

This could analogously go on two times with switches
"hashCommentsOff" and "dashCommentsOff"
for later versions...

Just an idea.


Either #pragma or #if directives would solve the problem neatly, but the 
problem there is that we'd need to have them retroactively. And there's 
zero chance of getting anything into earlier parsers now that everything 
before LC8 is going to be end-of-lifed.


--
 Mark Wieder
 ahsoftw...@gmail.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: The TSA Android app

[Alejandro Tejada]

In a brighter note, now every CS Teacher have a new
Real World Case to entice their students:
"Look how easy you can earn 
your first million dollars..." :D

Al



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/The-TSA-Android-app-tp4703144p4703276.html
Sent from the Revolution - User mailing list archive at Nabble.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: How to compile in earlier versions using new keywords?

[Richard Gaskin]

-hh wrote:

 @William
> A nifty workaround. But this means, that we have to make two
> script versions, and even three versions as soon as LC 8 is
> "unlinked" (wrt compatibility) from previous versions.

What does "unlinked" mean?

As with most well-designed software, the new version is designed to be a 
superset of features found in older versions.


If you find things that run in v7 but not v8 that would be a bug that 
the team would want to address ASAP.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.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: How to compile in earlier versions using new keywords?

[-hh]

@William
A nifty workaround. But this means, that we have to make two
script versions, and even three versions as soon as LC 8 is
"unlinked" (wrt compatibility) from previous versions.

@Craig
I have some scripts where I use for example a switch for
the itemdelimiter.
if char 1 of the version < 7 then set itemdelimiter to CR
else set itemdelimiter to ("." & CR) 
This is especially useful for splitting to and combining from
arrays and makes sense for me.
Okay, itemdelimiter is not a keyword but a property, analogue.

@Jacqueline
Amazing!! As you say, the "do" compiles in LC 6:
on mouseUp 
  if char 1 of the version > 6 then 
do "put trueword 1 of fld 1 into fld 2" 
  else put word 1 of fld 1 into fld 2
end mouseUp 
But this means, that we have to put all code for LC 7/8 that
should compile also in LC 6 and earlier into strings and then do
these strings. 
For example a long "repeat for each trueword tw in X ...".
This is close to Bill's method (read from fields).

I have an idea, that may be more comfortable:
If we could have a switch in LC 7+8 for parsing/compiling
that temporarily disables one of the commenting methods,
for example "//", we could use "version blocks" in new scripts:

// usual comment line for all versions
set slashCommentsOff to true
 // ... code for versions 7/8 only
 // ... code for versions 7/8 only
set slashCommentsOff to false
// usual comment line for all versions

This could analogously go on two times with switches
"hashCommentsOff" and "dashCommentsOff"
for later versions...

Just an idea.



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270p4703274.html
Sent from the Revolution - User mailing list archive at Nabble.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: How to compile in earlier versions using new keywords?

[J. Landman Gay]

This is one of the few cases where you have to use "do" .

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



On April 9, 2016 8:45:18 AM -hh  wrote:


Is there a way to *compile* the following script in LC versions before 7?

on mouseUp
  if char 1 of the version > 6 then
 put trueword 1 of fld "IN" into fld "OUT"
  else put word 1 of fld "IN" into fld "OUT"
end mouseUp

The use of the try structure doesn't help, the script doesn't even
*compile*. The same with "segment" and other new terms of LC 7/8.

More generaly, is there a way to "hide" some script blocks so that
the compilation in all earlier versions handles the block as comment?




--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270.html

Sent from the Revolution - User mailing list archive at Nabble.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




___
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: How to compile in earlier versions using new keywords?

[dunbarx]

Hernann.


Maybe I do not understand. If a new native word is present in a certain 
version, it will not be recognized in an earlier one. There is no way to 
compile, it, any more than if you used any other extraneous word.


Craig



-Original Message-
From: Earthednet-wp 
To: How to use LiveCode 
Sent: Sat, Apr 9, 2016 9:51 am
Subject: Re: How to compile in earlier versions using new keywords?

Perhaps there is a way to have a text field that holds the appropriate script 
for the version, then you can set the script of btn xyz to fld "best script" on 
startup.
Bill

William Prothero
http://es.earthednet.org

> On Apr 9, 2016, at 6:11 AM, -hh  wrote:
> 
> Is there a way to *compile* the following script in LC versions before 7?
> 
> on mouseUp
>  if char 1 of the version > 6 then
> put trueword 1 of fld "IN" into fld "OUT"
>  else put word 1 of fld "IN" into fld "OUT"
> end mouseUp
> 
> The use of the try structure doesn't help, the script doesn't even
> *compile*. The same with "segment" and other new terms of LC 7/8.
> 
> More generaly, is there a way to "hide" some script blocks so that 
> the compilation in all earlier versions handles the block as comment? 
> 
> 
> 
> 
> --
> View this message in context: 
> http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270.html
> Sent from the Revolution - User mailing list archive at Nabble.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

___
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: How to compile in earlier versions using new keywords?

[Earthednet-wp]

Perhaps there is a way to have a text field that holds the appropriate script 
for the version, then you can set the script of btn xyz to fld "best script" on 
startup.
Bill

William Prothero
http://es.earthednet.org

> On Apr 9, 2016, at 6:11 AM, -hh  wrote:
> 
> Is there a way to *compile* the following script in LC versions before 7?
> 
> on mouseUp
>  if char 1 of the version > 6 then
> put trueword 1 of fld "IN" into fld "OUT"
>  else put word 1 of fld "IN" into fld "OUT"
> end mouseUp
> 
> The use of the try structure doesn't help, the script doesn't even
> *compile*. The same with "segment" and other new terms of LC 7/8.
> 
> More generaly, is there a way to "hide" some script blocks so that 
> the compilation in all earlier versions handles the block as comment? 
> 
> 
> 
> 
> --
> View this message in context: 
> http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270.html
> Sent from the Revolution - User mailing list archive at Nabble.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

___
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

How to compile in earlier versions using new keywords?

[-hh]

Is there a way to *compile* the following script in LC versions before 7?

on mouseUp
  if char 1 of the version > 6 then
 put trueword 1 of fld "IN" into fld "OUT"
  else put word 1 of fld "IN" into fld "OUT"
end mouseUp

The use of the try structure doesn't help, the script doesn't even
*compile*. The same with "segment" and other new terms of LC 7/8.

More generaly, is there a way to "hide" some script blocks so that 
the compilation in all earlier versions handles the block as comment? 




--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/How-to-compile-in-earlier-versions-using-new-keywords-tp4703270.html
Sent from the Revolution - User mailing list archive at Nabble.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