On 27/10/15 04:07, Mark Wieder wrote:
Mark-
Well. *This* certainly seems to have hit a nerve.
I would be fine with having everything be "hilite". Or with everything
being "highlight". Or with everything being "blxxqvy". The point of
the original bug report was that there's no consistency in t
Well there’s two ways to look at this. Either we agree that hilite was a
mistake. Implement highlight everywhere then deprecate hilite. Or we agree that
highlight was a mistake and we deprecate the small number of uses of that. When
I say deprecate I just mean making a note in the dictionary at
Mark-
Well. *This* certainly seems to have hit a nerve.
I would be fine with having everything be "hilite". Or with everything
being "highlight". Or with everything being "blxxqvy". The point of the
original bug report was that there's no consistency in the language.
Sometimes you can use the
Looks like someone beat me to it.
http://www.socketlabs.com/smtp-server-connection-diagnostics-tool/
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
prefer
> On 27 Oct 2015, at 6:08 am, Mark Waddingham wrote:
>
>> repeat for each line L in someText with index i
>> apply myFunction to X until the value converges
>> apply (+1) to every item of myList where it mod 2 = 1
>> ...and many, many more.
>
> No - widgets is not what it has turned into. Widge
On 10/26/2015 3:50 AM, Tiemo Hollmann TB wrote:
if I have stacks, which are frequently shown, like dialog windows, what is
good practice. Open once and only show/hide, when using? Or should you close
those kind of stacks always and toplevel/modal them again every time when
needed? When I need to
On 10/26/2015 3:25 PM, Dr. Hawkins wrote:
There is a custom property (call it theProp) with a value like
"SELECT foo FROM " & tableName & " WHERE (bar > 7) AND (animal<>'cat');"
So those quotes and & are in the string to be evaluated.
My understanding of parsing is that the first piece shou
On Mon, Oct 26, 2015 at 9:49 AM, Bob Sneidar
wrote:
> Now I get "Abc"45"123(def)" in tTest. I'm not sure what you are expecting,
> but that is what is getting passed to value(). If you asked me to resolve
> that, I would probably toss a few errors, not to mention a few brews, back
> myself.
>
I
> On 27 Oct 2015, at 1:51 am, Rick Harrison wrote:
>
> A work around is to let all previous versions work, and put the final winning
> candidate into the dictionary, the others will no longer appear in the
> documentation. This solves the problem with the least disruption as it
> doesn’t break
On 2015-10-24 22:07, Geoff Canyon wrote:
This is the main thing I have been looking forward to for the past
several
years. The goal was to allow the addition of truly new syntax and
functionality to the language. I really wanted this, and widgets is
what it
has turned into. Not that widgets are
https://pixelbuddha.net/freebies/tag/ui-kits
look like fun.
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/mailma
On 26/10/15 20:55, J. Landman Gay wrote:
On 10/26/2015 1:30 PM, Richmond wrote:
Um: my endless thousands of numToChar statements in my Devawriter Pro
will have to
be rewritten should I decide to move my code-base from LC 4.5 to LC 7.*
or higher.
Not necessarily, numToChar and charToNum still w
On 10/26/2015 1:30 PM, Richmond wrote:
Um: my endless thousands of numToChar statements in my Devawriter Pro
will have to
be rewritten should I decide to move my code-base from LC 4.5 to LC 7.*
or higher.
Not necessarily, numToChar and charToNum still work. They are
discouraged now, but they s
On 2015-10-26 19:30, Richmond wrote:
Um: my endless thousands of numToChar statements in my Devawriter Pro
will have to
be rewritten should I decide to move my code-base from LC 4.5 to LC
7.* or higher.
I'm not sure that is necessarily true. I believe you use 'unicodeText'
in your code-base, a
On 26/10/15 19:17, Bob Sneidar wrote:
[FAIR WARNING: BLOVIATION TO FOLLOW]
Wow: never heard of 'Bloviation' before.
Mark Waddingham wrote:
Of course, whilst intellectually interesting, the reality is that
computers have gotten pretty darn good (and continue to get better) at
approximating t
On 26/10/15 16:51, Rick Harrison wrote:
Hi Mark,
Whenever one deprecates code, it destroys someone’s code somewhere.
Don’t do it.
I had a project I had worked on for 10 years of my life. It encompassed
over 70,000 lines of hard won hand-written code. One day the company
who was producing the
On 26/10/15 16:17, Roland Huettmann wrote:
Originally I had thought that "Open Language" means to allow LiveCode to
run other scripting languages within it's framework, for example using
Python, or somehow link such languages into LiveCode.
I started hating "machines" who started "understanding"
On 26/10/15 12:06, Mark Waddingham wrote:
On 2015-10-24 21:00, Richmond wrote:
Well, what to one person is 'natural language' may not be to another:
and a "10,000 different, often incompatible and sometimes confusing,
custom syntax options" does seem to sum that problem up fairly
effectively.
On 26/10/2015 18:08, Richmond wrote:
2. American English IS the dominant form of English in the world right
now (and probably for the forseeable future).
H ... true for now, but I wouldn't be surprised if Indian English
overtook it over the next 2 to 3 decades.
Already the present co
On 26/10/15 11:00, Mark Waddingham wrote:
On 2015-10-24 22:47, Mark Wieder wrote:
On 10/24/2015 12:21 PM, Peter TB Brett wrote:
* hilite -> highlight
Actually I filed a bug report on that six years ago.
http://quality.runrev.com/show_bug.cgi?id=8211
It got confirmed and ignored.
I just subm
Hi Mark,
I greatly appreciate your response to this topic.
> In terms of syntax / synonym related suggestions - then the situation is much
> easier. We might deprecate some, just to make it clear what the 'preferred'
> form is and to discourage further usage. We would never remove them until
>
[FAIR WARNING: BLOVIATION TO FOLLOW]
Mark Waddingham wrote:
> Of course, whilst intellectually interesting, the reality is that
> computers have gotten pretty darn good (and continue to get better) at
> approximating the outward effects of the human brain in every increasing
> areas; which means
Please ignore the last message - this seems to now be resolved. Not totally
sure why though…
Sorry for the disturbance… :-)
cheers
Alan
On 26 Oct 2015, at 5:09 pm, Alan Stenhouse wrote:
> After installing LC 6.7.8 RC1 and testing an app under it, I now find that
> opening the same app in LC
Mark Waddingham wrote:
On 2015-10-24 23:25, Richard Gaskin wrote:
I've worked with OS APIs in Pascal, C, and two xTalks, Tookbook's
OpenTalk scripting language which provides that built-in, and
CompileIt for HyperTalk.
This is true - they did. However, they come from a time when almost all
OS
Now I get "Abc"45"123(def)" in tTest. I'm not sure what you are expecting, but
that is what is getting passed to value(). If you asked me to resolve that, I
would probably toss a few errors, not to mention a few brews, back myself.
Bob S
> On Oct 26, 2015, at 08:48 , Dr. Hawkins wrote:
>
>
Mark Waddingham wrote:
Of course, whilst intellectually interesting, the reality is that
computers have gotten pretty darn good (and continue to get better) at
approximating the outward effects of the human brain in every increasing
areas; which means whether or not their computational models ar
The text I copied didn't have the quotes. I'll try again.
Bob S
On Oct 26, 2015, at 08:48 , Dr. Hawkins
mailto:doch...@gmail.com>> wrote:
put quote & "Abc" & quote & 45 & quote & "123(def)" & quote into tTest
___
use-livecode mailing list
use-livec
Mark Waddingham wrote:
> On 2015-10-24 18:53, Richard Gaskin wrote:
>> Two questions:
>>
>> 1. Do we have a projected timeline for that?
>
> LiveCode 9.
>
>> 2. Isn't the goal so that we can have 10,000 different, often
>> incompatible and sometimes confusing, custom syntax options for doing
>> b
I used to use this script editor full time back in the day. It is really nice
to see that you are keeping it going Mark. Thought I might give it a try again
and see how it goes.
I am getting an answer dialog with what appears to be executionContext values
after almost every action I do. I am us
After installing LC 6.7.8 RC1 and testing an app under it, I now find that
opening the same app in LC 6.7.6 and attempting to run it on the simulator 8.2
results in the error
“Unable to start simulation: The operation couldn’t be completed.
(LaunchServicesError error 0.)”
The app previously ra
On 2015-10-24 23:25, Richard Gaskin wrote:
I've worked with OS APIs in Pascal, C, and two xTalks, Tookbook's
OpenTalk scripting language which provides that built-in, and
CompileIt for HyperTalk.
This is true - they did. However, they come from a time when almost all
OS APIs were procedural, a
On Mon, Oct 26, 2015 at 8:29 AM, Bob Sneidar
wrote:
>
>
> on mouseUp
>put "Abc" & 45 & "123(def)" into tTest
>put value (tTest)
> end mouseUp
>
> tTest results in Abc45123(def) so you are trying to get the value of the
> result of a function called Abc45123() where you pass a value in a
On 2015-10-24 22:55, JB wrote:
If you do get Open Language what will it do to the
speed? They said LC8 would be good because it
will make it easier for developers to write code in
LC which needed to be and external before.
We're still working on the 'foreign function interface' in LCB, so it i
Actually, I was playing around with the Exchange connectors, and inadvertently
disable the default connector. DOH!
Bob S
> On Oct 25, 2015, at 19:19 , Mark Wieder wrote:
>
> On 10/25/2015 05:10 PM, Glen Bojsza wrote:
>> Hi Bob,
>>
>> I tried contacting via bobsnei...@iotecdigital.com but the
I did
on mouseUp
put "Abc" & 45 & "123(def)" into tTest
put value (tTest)
end mouseUp
tTest results in Abc45123(def) so you are trying to get the value of the result
of a function called Abc45123() where you pass a value in a variable called
def. At run time, do you have a function Abc45
We've seen this before...
https://sites.google.com/site/hoytssecretlair/resources/s-1
Walt
On Mon, Oct 26, 2015 at 10:51 AM, Rick Harrison
wrote:
> Hi Mark,
>
> Whenever one deprecates code, it destroys someone’s code somewhere.
> Don’t do it.
>
> I had a project I had worked on for 10 years o
On 2015-10-26 15:51, Rick Harrison wrote:
Whenever one deprecates code, it destroys someone’s code somewhere.
Don’t do it.
Indeed, we have tried and do continue to try our very best not to break
people's code as the platform evolves (even though this is a huge
constraint to put on a programmi
As always, put it into a variable, copy the contents of the variable to the
clipboard, either programmatically, or from the debugger, paste it into an SQL
editor, and it should show you where the error occurs.
Bob S
> On Oct 25, 2015, at 08:19 , Dr. Hawkins wrote:
>
> On Sat, Oct 24, 2015 a
I think the reply was to trap for suspendStack in your apps, save the current
selection and selectedObject, then trap for resumeStack and set it again. It's
the only way I've found to do it. It's a pain, but not difficult to implement.
I agree that the selection for a stack should not deselect w
A few notes about GLX2. There are no red dot breakpoints in GLX2 (unless I am
missing something).
So you might be tempted to turn on and off GLX2 as needed. Problem is, GLX2 has
it's own versioning system that allows you to go back x compiles to a prior
version. The built-in compiler does not
Hi Mark,
Whenever one deprecates code, it destroys someone’s code somewhere.
Don’t do it.
I had a project I had worked on for 10 years of my life. It encompassed
over 70,000 lines of hard won hand-written code. One day the company
who was producing the language decided to make some major change
Spookier that you happened to be reading that particular message from
2008 in 2015.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
ambassa...@fourthworld.com
I wrote something like this about a dozen years ago: a script pre-processor
that worked with the script editor to store the pre-processed script as a
custom property for use later.
I remember implementing default values for parameters like so:
on someHandler paramOne=27, paramTwo=13
Which wou
Originally I had thought that "Open Language" means to allow LiveCode to
run other scripting languages within it's framework, for example using
Python, or somehow link such languages into LiveCode.
I started hating "machines" who started "understanding" me and making
assumptions about what I want.
Don’t forget other possibilities of this future open language :
Allow scripts to be written in a non-english language - french in my case for
example - especially for kids and students from non english speaking developing
countries.
Different words and slightly different syntax.
These foreign sc
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #6 here: https://goo.gl/p5uWxk
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around t
On 2015-10-26 10:26, Monte Goulding wrote:
I agree with you. I hate synonyms. They should be replaced by
auto-completion.
How about 'spelling assist' too - referencing a dynamic dictionary based
on context.
Mark.
--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Ev
On 2015-10-24 21:00, Richmond wrote:
Well, what to one person is 'natural language' may not be to another:
and a "10,000 different, often incompatible and sometimes confusing,
custom syntax options" does seem to sum that problem up fairly
effectively.
Indeed - what is 'natural' to me is differ
Hello,
since LC 6.7.6 or 6.7.7 you can enable Hi-DPI scaling in the standalone
builder settings for windows.
I don't have a Hi-DPI monitor and didn't found anything in the forum about
it, so I am unsure what happens with my stack if I would enable this
setting? What exactly happens when it says "
I¹d be happy with auto-completion and fewer (or no) synonyms.
Terry...
On 26/10/2015 8:26 pm, "use-livecode on behalf of Monte Goulding"
wrote:
>I agree with you. I hate synonyms. They should be replaced by
>auto-completion.
>
>Sent from my iPhone
>
>> On 26 Oct 2015, at 8:00 pm, Mark Waddingha
I agree with you. I hate synonyms. They should be replaced by auto-completion.
Sent from my iPhone
> On 26 Oct 2015, at 8:00 pm, Mark Waddingham wrote:
>
> (One could also argue that the problem of synonyms and abbreviations is far
> better handled in the script-editing environment... Although
On 2015-10-24 18:53, Richard Gaskin wrote:
Two questions:
1. Do we have a projected timeline for that?
LiveCode 9.
2. Isn't the goal so that we can have 10,000 different, often
incompatible and sometimes confusing, custom syntax options for doing
basic things like setting the rect of a butto
On 2015-10-24 22:47, Mark Wieder wrote:
On 10/24/2015 12:21 PM, Peter TB Brett wrote:
* hilite -> highlight
Actually I filed a bug report on that six years ago.
http://quality.runrev.com/show_bug.cgi?id=8211
It got confirmed and ignored.
I just submitted a pull request.
Figured I might as we
Hello,
if I have stacks, which are frequently shown, like dialog windows, what is
good practice. Open once and only show/hide, when using? Or should you close
those kind of stacks always and toplevel/modal them again every time when
needed? When I need to change anything in those stacks on the fly
54 matches
Mail list logo
