Re: valueDiff for arrays?

2018-08-05 Thread David Glasgow via use-livecode
Maybe 'strain' could be a culinary synonym?
;-)

Best wishes 

David Glasgow

Sent from my  iPad via iBrain & iFingers

LinkedIn

> On 5 Aug 2018, at 16:36, J. Landman Gay via use-livecode 
>  wrote:
> 
> This is getting pretty contorted and is becoming less like natural language. 
> For what it's worth, I have never been confused by the current use of filter. 
> I think of it as pouring soup through a wire strainer. Filtering "with" keeps 
> the solids. Filtering "without" dumps them and keeps the liquid.
> 
> Maybe I cook too much. In any case, the solids (what remains after filtering) 
> are the things you're either keeping or discarding.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
>> On August 5, 2018 9:38:45 AM Brian Milby via use-livecode 
>>  wrote:
>> 
>> Probably better:
>> 
>> 
>> filter [{lines | items | keys | elements} of] filterSource {keeping | 
>> discarding | with | without | [not] matching} {[{wildcard | regex} pattern] 
>> filterPattern | where filterExpression} [into targetContainer]
>> 
>> 
>> So Monte’s example would be:
>> filter keys of tFoo keeping where tFoo[each] is not tBar[each]
>> (And to get Richard’s result you would need to follow this by an intersect 
>> each way. The filter would replace the repeat loop in Mark’s solution)
>> 
>> 
>> Even though “with where” would be syntactically correct, the preferred usage 
>> would be “keeping where”.
>> 
>> Thanks,
>> Brian
>>> On Aug 5, 2018, 7:32 AM -0500, Mark Waddingham via use-livecode 
>>> , wrote:
>>> On 2018-08-05 07:31, Monte Goulding via use-livecode wrote:
>>> > Given I have been wanting to do ^ for a couple of years I decided to
>>> > just go ahead and do it… might be a while before we have time to
>>> > bikeshed the syntax though.
>>> >
>>> > https://github.com/livecode/livecode/pull/6626
>>> > 
>>> >
>>> > Examples:
>>> > local tFoo,tBar
>>> > put "foo" into tFoo[1]
>>> > put "bar" into tFoo[2]
>>> > put "baz" into tBar[1]
>>> > put "bar" into tBar[2]
>>> > filter keys of tFoo with expression tFoo[each] is tBar[each]
>>> > — tFoo now has one key 2 which is `bar`
>>> >
>>> > put “yes,foo” & return & “no,bar” into tFoo
>>> > filter lines of tFoo with expression item 1 of each is “yes”
>>> >
>>> > We could feasibly not use `with|without` for this forcing the
>>> > expression to return true to filter. If we went that way then perhaps
>>> > `where` would be nicest?
>>> >
>>> > filter lines of tFoo where item 1 of each is “yes”
>>> 
>>> Geez @Monte - you do like creating work for me don't you! ;)
>>> 
>>> In terms of syntax - definitely not 'with expression' - that's ghastly.
>>> It is a 'where' clause - in the same vein as SQL and other query
>>> languages - so no bike-shedding required there (also, pleasingly, all
>>> other 'filter' types become sugar for a where clause using operators
>>> which the language does not have yet - but obviously we have the code
>>> for...).
>>> 
>>> If we are going to bike-shed over syntax - can we do so over the use of
>>> 'filter' itself. I don't know why but I have a complete mental block
>>> about it - regardless of how many times I use it or read it - I always
>>> have to 'double-think' to work out what form to use - is that just me?
>>> 
>>> filter  of X with Y
>>> filter  of X without Y
>>> 
>>> I couldn't tell you just by looking *what* they actually do. I'm not
>>> sure why but I think the verb is actually wrong - in all cases you have
>>> a set of things and you are either keeping an element, or removing an
>>> element... So I wonder if:
>>> 
>>> keep  of X where Y
>>> discard  of X where Y
>>> 
>>> (I'm not particularly attached to keep/discard - but it does need to be
>>> a pair of 'true' antonyms which don't intersect with any other 'core'
>>> pairs of such things we have).
>>> 
>>> Might be more appropriate?
>>> 
>>> Of course, maybe it is just 'with' / 'without' are inappropriate, and
>>> 'where' might actually help me retrain my mind to see with/without as
>>> the sugar they truly are.
>>> 
>>> Anyway, thought it worth throwing out there to see what people think?
>>> 
>>> Warmest Regards,
>>> 
>>> Mark.
>>> 
>>> --
>>> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
>>> LiveCode: Everyone can create apps
>>> 
>>> ___
>>> 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
> 

Re: URGENT: MergGoogle no longer works on iOS: CLIENTS VERY UNHAPPY

2018-05-04 Thread David Glasgow via use-livecode
It was a single problem, but the poor fellow was in hock up to the ears and out 
of time. 

If there is anything positive here it is the response of the community. No 
lectures on what he should have done different, just genuine concern and an 
astonishingly quick fix. 

Best wishes 

David Glasgow

Sent from my  iPad via iBrain & iFingers

LinkedIn

> On 4 May 2018, at 11:07, Lagi Pittas via use-livecode 
>  wrote:
> 
> I still think for a  client to pull away like that with  a single problem
> that was not insurmountable
___
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


"Aphasia" (was Re: use-livecode Digest, Vol 171, Issue 44)

2017-12-28 Thread David Glasgow via use-livecode
Unfortunately, it is all rather more complicated than either Richmond or Peter 
suggest. There are many more contributing areas than Brocas, and what Peter 
describes doesn't appear to be aphasia at all, but rather a pathology of 
semantics or word finding. 

It's not possible to be more specific without more information, and my advice 
would be to speak with a neuropsychologist before coding. You could spend a lot 
of time comparing wavs and coming up with a solution to the wrong problem. 

Best wishes 

David Glasgow
Sent from my iBrain via iFingers & iPad


LinkedIn

> On 28 Dec 2017, at 08:26, Richmond Mathewson via use-livecode 
>  wrote:
> 
> If we start to unpack your post we can come to a slightly simpler conclusion 
> than what you set out as your goal initially.
> 
> 1. Is your main idea to have a program where the device can "do the talking" 
> for the patient?
> 
> 2. As the "owner" of a 94 year old Mother-in-law who suffers from some sort 
> of selective dementia I realise that
> pointing out to her that her hallucinations are hallucinations (rather than 
> reality) is both an uphill struggle
> and causes her a lot of distress: oddly enough she's far happier inside the 
> comfort zone of her hallucinations.
> 
> If "Granny" suffers from Aphasia she has permanent damage in the Broca's Area 
> of her brain, normally due to
> a stroke: this cannot be sorted out, unfortunately.
> 
> She could, also, suffer from a type of dementia that has similar symptoms to 
> aphasia.
> 
> Doesn't really matter which; the end result is just as bad and bl**dy awful 
> for all concerned.
> 
> If you are going for #1 then there is absolutely no need for any 
> speech-recognition stuff or comparison
> between recorded sounds and those on the device.
> 
> Richmond.
> 
>> On 28/12/17 2:26 am, Peter Reid via use-livecode wrote:
>> Hi Marc, Paul, Phil, Rick and Richmond
>> 
>> Thanks for your various thoughts.
>> 
>> To put a bit more flesh on this, here's what I'm developing and why...
>> 
>> In the first instance I'm doing this development for a friend who's 
>> grandmother suffers from aphasia (saying completely the wrong word).  The 
>> idea is that her family can put together sets of words where each word is 
>> spoken by the app whilst displaying a relevant picture and optionally a 
>> short video clip illustrating the correct mouth shape when saying the word.  
>> The app displays the word in a very large font with a picture, then the app 
>> says the word (with the option to see a mouth shape video clip).  The user 
>> responds by trying to say the same word and (the thing I can't do yet!) the 
>> app gives the user a percentage score that represents how closely the user 
>> matched the sample word. If the user's score is above a variable threshold, 
>> the user sees a smiley face, otherwise a sad face!
>> 
>> I tried contacting Mark Smith as suggested by Paul but his email address 
>> m...@maseurope.net no longer works.
>> 
>> So far I have everything working apart from the comparison of 2 WAV files, 
>> in particular the following is working:
>> 
>> - the app checks for the presence of a micro SD card as the source of a 
>> collection of word packs
>> - a word pack consists of a collection of words in sound (WAV) and picture 
>> (JPG) form, optionally with supporting video clips (MP4)
>> - the app lets the user select a word pack at start up and loads the pack 
>> into RW file space
>> - the user taps a large arrow icon to go forwards/backwards through the 
>> chosen list of words
>> - for each word, the word is displayed in a large font at the top of the 
>> landscape screen, with its associated picture occupying the lower half of 
>> the screen
>> - as the word is displayed, it is spoken
>> - the user can tap a microphone icon and record their attempt at the word
>> - currently I simulate the comparison of the 2 WAV files
>> - the app gives a percentage score and displays a smiley or sad face 
>> accordingly
>> 
>> To be honest, my main aim is to help a friend.  At this stage I'm not 
>> looking beyond this, so licensing, etc. is not on the horizon at the moment.
>> 
>> Thanks again
>> 
>> Peter
>> --
>> Peter Reid
>> Loughborough, UK
>> 
>> 
>> ___
>> 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: