Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Curry Kenworthy via use-livecode
Richard: > Curry Kenworthy wrote: >> What people need most in the Script Editor is to view and edit the >> code itself smoothly, without jitters or delays > Not hard to make one. A frontScript trapping the editScript message > lets you do whatever you want. It's interesting when we take a

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Bob Sneidar via use-livecode
+1 for Sublime. I do not code in it much, but there are plugins like for comparing two scripts to see differences. If I ever get around to converting my main app to Levure, I would probably use it more. Bob S > On Jan 23, 2019, at 10:52 , Trevor DeVore via use-livecode > wrote: > > On

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Richard Gaskin via use-livecode
Trevor DeVore wrote: > On Wed, Jan 23, 2019 at 12:39 PM Richard Gaskin wrote: >> >> And then there are the countless third-party text editors, some of >> which have LC-specific add-ons crafted by our community for them, >> like Trevor's plugin for Atom. I've been using Atom enough in web >>

Re: Thoughts on Livecode Server

2019-01-23 Thread Richard Gaskin via use-livecode
David Bovill wrote: > Does anyone have any thoughts on where Livecode server should go / is > going? So far it goes wherever I take it, so I haven't given much thought beyond one enhancement request for init optimization (useful for CGI, will make no difference for any use as a persistent

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Trevor DeVore via use-livecode
On Wed, Jan 23, 2019 at 12:39 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > > And then there are the countless third-party text editors, some of which > have LC-specific add-ons crafted by our community for them, like > Trevor's plugin for Atom. I've been using

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Richard Gaskin via use-livecode
Curry Kenworthy wrote: > What people need most in the Script Editor is to view and edit the > code itself smoothly, without jitters or delays Not hard to make one. A frontScript trapping the editScript message lets you do whatever you want. You can make a stack with a field and a Save

Re: Displaying or identifying emoji

2019-01-23 Thread David V Glasgow via use-livecode
> On 23 Jan 2019, at 2:15 pm, Stephen MacLean via use-livecode > wrote: > > You say you are importing them? From where? A text file or DB? Basically, Stephen, I take what I am given. Could be plain text, Word, HTML , even spreadsheetn- and often I don’t know any intermediate steps

Re: global is empty

2019-01-23 Thread JJS via use-livecode
i had to put the global behind global. i was a mistake i looked over. so no bug. Op 23-1-2019 om 04:51 schreef Tom Glod via use-livecode: has this been resolved? when you moved the global declaration to the top it worked? I keep an eye on reports like this because they are the most worrisome

Re: global is empty

2019-01-23 Thread JJS via use-livecode
i had to put the global behind global, not behind local. it was a mistake i looked over. so no bug. Op 23-1-2019 om 04:51 schreef Tom Glod via use-livecode: has this been resolved? when you moved the global declaration to the top it worked? I keep an eye on reports like this because they are

Re: Displaying or identifying emoji

2019-01-23 Thread scott--- via use-livecode
Please post. I would find this very useful. Scott Morrow Elementary Software (Now with 20% less chalk dust!) web http://elementarysoftware.com/ email sc...@elementarysoftware.com booth 1-800-615-0867 -- > On Jan 23, 2019, at 7:13

Re: Displaying or identifying emoji

2019-01-23 Thread Stephen MacLean via use-livecode
In my testing so far, word works while trueWord doesn’t, although that testing is still preliminary... In my case, I need to strip them out. Single codepoint ones like the smiley are easy, they are one codepoint and 1 word. The ones, like red haired man, are tougher because they are multple

RE: Displaying or identifying emoji

2019-01-23 Thread Ralph DiMola via use-livecode
"Also, depending on the emoji, it may be 1 codepoint or many. Use the keyword “word” when finding, etc." Word or "true word"? Does it matter? Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode

Re: Displaying or identifying emoji

2019-01-23 Thread Stephen MacLean via use-livecode
Hi David, Looks like you are running into some of the same issues I had when learning to work with them… You say you are importing them? From where? A text file or DB? Make sure that the encoding is set to UTF-8 or higher when you import. Next, you need to textDecode() them, again making sure

Displaying or identifying emoji

2019-01-23 Thread David V Glasgow via use-livecode
Hello folks, I am working on imported text messages from various sources, and which have been through various (unknown) processes/displays before I get them. Some retain emoji intact, but others render them as an odd series of characters (presumably having been substituted when stored in a

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Richmond via use-livecode
Oh, let's get campy. In a perfect world there should not really be a need for "us" and "them" camps with LiveCode, it should cater to all people along a continuum stretching from "us" to "them". While LiveCode may be tending to introduce more "them" features (arguably because all "us"

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread Richmond via use-livecode
Well, Curry, at the risk of causing you terminal disappointment, I can do nothing but support your request for the thing to be a simple as possible. "my budget hardware" my "budgetist" hard ware is a Pentium 4 I picked up 12 years ago, second had, for $12 . . . It has "2000" written on the

Re: Us and them? [was Re: Livecode Dictionary]

2019-01-23 Thread David Bovill via use-livecode
Hi Richard - yes indeed Github and GIST integration is part of the mix. I have libraries for those and have been publishing directly from Livecode for a few years now so it works well. My thinking on it is to use Github as an option for offloading (large) data, and keeping the json as metadata -