Re: Searching text external to Livecode

2016-08-19 Thread Ali Lloyd
If you have or could make a sample stack that demonstrates this slowdown, it would be useful for us to have a look at. On Fri, Aug 19, 2016 at 12:23 AM Peter Bogdanoff wrote: > >> Livecode’s find command in LC8 is really, REALLY slow when you're doing > multiple (thousands) of finds. > > >> use

Re: Searching text external to Livecode

2016-08-19 Thread James Hale
Richard asked > Maybe the simplest solution for somewhat large collections would be the > free-text indexing built into SQLite. Anyone here know if we have a > means of using that from within LC? Yes and no. The Full text search extension to SQLite is indeed in the current compilation and is

Re: Searching text external to Livecode

2016-08-18 Thread Peter Bogdanoff
>> Livecode’s find command in LC8 is really, REALLY slow when you're doing >> multiple (thousands) of finds. >> use-livecode mailing list > I am doing a find char, finding a single character, and putting a space before or after it. It’s a continuous script to find possibly 3 to 4 thousand oc

Re: Searching text external to Livecode

2016-08-18 Thread Peter Bogdanoff
> On Aug 18, 2016, at 2:52 PM, Richard Gaskin > wrote: > > Peter Bogdanoff wrote: > > > Does anyone know if there a solution that search indexes folders of > > HTML files that I can implement into Livecode? And also handles > > non-English text? > > I've written a few specialized search engin

Re: Searching text external to Livecode

2016-08-18 Thread Richard Gaskin
Peter Bogdanoff wrote: > Does anyone know if there a solution that search indexes folders of > HTML files that I can implement into Livecode? And also handles > non-English text? I've written a few specialized search engines and just started another one the other day for more general-purpose ne

Searching text external to Livecode

2016-08-18 Thread Peter Bogdanoff
Hi all, I’m building a text-heavy application that requires a good text search capability. I’ve been using Scott McDonald’s RRPsearch plugin for awhile now with good results. However: 1. It doesn’t seem to handle text that has extended characters next to words—like long dashes, curly quotes, e