sqlYoga question

[Bob Sneidar via use-livecode]

Hi ll. 

I have a curious problem. I am trying to select only records with the highest 
value in an SQL table. I know the SQL to do it, but how to get sqlYoga to do it 
is a mystery to me. The actual SQL looks something like this:

select * from files t1 
   where custid = '289' and fileversion = (select max(fileversion) from files 
t2 where t2.filename = t1.filename)

I know I can do this in the native API, but the question is, how to do this in 
sqlYoga?? 

Bob S


___
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: Search for an app in Google Play Store

[Bob Sneidar via use-livecode]

That IS weird. 

Bob S


> On Jul 17, 2023, at 1:05 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> On 7/17/23 3:10 AM, Klaus major-k via use-livecode wrote:
>> Maybe I do not understand it correctly?
>> 
>> Hi Klaus,
>> Thanks for contacting Google Play Developer Support.
>> Google Play app search works across title, developer name, and app 
>> descriptions.
>> Your title should be unique and accessible, avoid common terms, and reinforce
>> what your app is about.
>> Using common or generic words like "Puzzle" or "Sports" can often increase 
>> the
>> total number of potential search results, thus making your app more 
>> difficult to find.
>> Using the search phrase Sehen-Hören-Merken forces our search engine to 
>> autocorrect
>> the search term and return results as if the search term were "Sehen - Hören 
>> - Merken" (in quotes).
> 
> Interesting. The app that couldn't be found for me had an "@" sign in the 
> name. So I agree that symbols or punctuation like hyphens may be the problem.
> 
> Since their algorithm converts the search term, you could try putting the 
> Google version in the description somewhere. You could put it way at the 
> bottom of the description, just for reference.
> 
> I very occasionally see titles like this:
> Sehen-Hören-Merken (Sehen - Hören - Merken)
> 
> I wondered why but now I think I know.
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.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: Search for an app in Google Play Store

[J. Landman Gay via use-livecode]

On 7/17/23 3:10 AM, Klaus major-k via use-livecode wrote:

Maybe I do not understand it correctly?

Hi Klaus,

Thanks for contacting Google Play Developer Support.

Google Play app search works across title, developer name, and app descriptions.
Your title should be unique and accessible, avoid common terms, and reinforce
what your app is about.

Using common or generic words like "Puzzle" or "Sports" can often increase the
total number of potential search results, thus making your app more difficult 
to find.
Using the search phrase Sehen-Hören-Merken forces our search engine to 
autocorrect
the search term and return results as if the search term were "Sehen - Hören - 
Merken" (in quotes).


Interesting. The app that couldn't be found for me had an "@" sign in the name. So I agree that 
symbols or punctuation like hyphens may be the problem.


Since their algorithm converts the search term, you could try putting the Google version in the 
description somewhere. You could put it way at the bottom of the description, just for reference.


I very occasionally see titles like this:
Sehen-Hören-Merken (Sehen - Hören - Merken)

I wondered why but now I think I know.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: Apple Notarization changes...

[Mark Smith via use-livecode]

Hi Paul, my sentiments exactly. I also shudder at having to change, modify or 
upgrade any aspect of the development environment because, like a set of 
dominoes, once you change one thing you are pretty much committed to having to 
upgrade and change everything else as well. Its an unfortunate aspect of 
developing in the modern computer age but tools like Matthias’s 
MrSignNotarizeHelperV4 makes it a LOT less bumpy.  I probably would have given 
up ages ago without it!!

Mark

> On 17 Jul 2023, at 6:11 pm, Paul Dupuis via use-livecode 
>  wrote:
> 
> Well, I'm glad the lesson and tool exists and thanks for the link.
> 
> On the negative side, I just found the Apple developer Xcode page that shows 
> that Xcode 13minimum OS version is  macOS Big Sur 11.3
> 
> So, no more Mojave. Huge bummer for me.
> 
> We have a macBook Air with Ventura (latest version), so I guess it is time to 
> set up and get used to Xcode 15. Ugh, I have when OS vendors change things. 
> We have enough changes we need to make in our own products we can't keep up 
> with :-(
> 
> 
> 
> On 7/17/2023 12:48 PM, matthias rebbe via use-livecode wrote:
>>> 2) Has Livecode (or anyone else) updated lessons. documentation, help apps, 
>>> etc, for using this new notarytool? If so, can anyone point me to it?
>>> 
>> see here
>> https://lessons.livecode.com/m/4071/l/1653720-code-signing-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore-with-xcode-13-and-up
>> 
>> 
>> 
>>> November 1 is still a ways off, but I find Apple Notarization so 
>>> incomprehensible that once I get a set of steps to work, I document them 
>>> and follow them verbatim and the thought of trying to figure out what this 
>>> change means is daunting!
>>> 
>>> 
>>> 
>>> ___
>>> 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


___
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: Apple Notarization changes...

[Mark Smith via use-livecode]

Matthias, thanks for upgrading your lesson plan to work with the new signing 
tool. It’s an invaluable asset and assistance to the community of mobile app 
developers. 

Mark

> On 17 Jul 2023, at 5:48 pm, matthias rebbe via use-livecode 
>  wrote:
> 
>> 
>> 2) Has Livecode (or anyone else) updated lessons. documentation, help apps, 
>> etc, for using this new notarytool? If so, can anyone point me to it?
>> 
> see here 
> https://lessons.livecode.com/m/4071/l/1653720-code-signing-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore-with-xcode-13-and-up
>  
> 
> 
> 
> 
>> November 1 is still a ways off, but I find Apple Notarization so 
>> incomprehensible that once I get a set of steps to work, I document them and 
>> follow them verbatim and the thought of trying to figure out what this 
>> change means is daunting!
>> 
>> 
>> 
>> ___
>> 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: Apple Notarization changes...

[J. Landman Gay via use-livecode]

@Paul : Matthias' helper stack is a great gift to the community. I think 
the LC team even uses it. You'll never have to use Terminal or Xcode again.


You can download the stack from the lesson he linked to, then scroll down 
to section 9 to see the setup.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On July 17, 2023 11:50:50 AM matthias rebbe via use-livecode 
 wrote:




2) Has Livecode (or anyone else) updated lessons. documentation, help apps, 
etc, for using this new notarytool? If so, can anyone point me to it?

see here
https://lessons.livecode.com/m/4071/l/1653720-code-signing-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore-with-xcode-13-and-up



November 1 is still a ways off, but I find Apple Notarization so 
incomprehensible that once I get a set of steps to work, I document them 
and follow them verbatim and the thought of trying to figure out what this 
change means is daunting!




___
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: Apple Notarization changes...

[Paul Dupuis via use-livecode]

Well, I'm glad the lesson and tool exists and thanks for the link.

On the negative side, I just found the Apple developer Xcode page that 
shows that Xcode 13minimum OS version is  macOS Big Sur 11.3


So, no more Mojave. Huge bummer for me.

We have a macBook Air with Ventura (latest version), so I guess it is 
time to set up and get used to Xcode 15. Ugh, I have when OS vendors 
change things. We have enough changes we need to make in our own 
products we can't keep up with :-(




On 7/17/2023 12:48 PM, matthias rebbe via use-livecode wrote:

2) Has Livecode (or anyone else) updated lessons. documentation, help apps, 
etc, for using this new notarytool? If so, can anyone point me to it?


see here
https://lessons.livecode.com/m/4071/l/1653720-code-signing-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore-with-xcode-13-and-up




November 1 is still a ways off, but I find Apple Notarization so 
incomprehensible that once I get a set of steps to work, I document them and 
follow them verbatim and the thought of trying to figure out what this change 
means is daunting!



___
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: Crazy question: is it possible/reasonable to use Python in LC?

[Ben Rubinstein via use-livecode]

"do ... as python" ??

On 13/07/2023 21:03, Geoff Canyon via use-livecode wrote:

I've been playing with Python, and it has a lot of nice qualities, but a
built-in GUI isn't one of them (no apologies to tkinter).

So it would be interesting/nice to be able to open LC, add a button to a
stack, and put some python into the script of that button and have it just
work, with access to the rest of the LC stack/controls as usual.

Obviously that's not possible, but how close can we come? I assume it would
be possible to write a shell command to trigger a python script, but that
seems complex and sub-optimal, especially when thinking about having to
bundle together all the bits and bobs from the LC UI to pass as arguments
to the Python script instead of having it able to just reference what it
needs on the fly.

Anyway, wondering if anyone else has thought about this.

gc
___
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: Apple Notarization changes...

[matthias rebbe via use-livecode]

> 
> 2) Has Livecode (or anyone else) updated lessons. documentation, help apps, 
> etc, for using this new notarytool? If so, can anyone point me to it?
> 
see here 
https://lessons.livecode.com/m/4071/l/1653720-code-signing-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore-with-xcode-13-and-up



> November 1 is still a ways off, but I find Apple Notarization so 
> incomprehensible that once I get a set of steps to work, I document them and 
> follow them verbatim and the thought of trying to figure out what this change 
> means is daunting!
> 
> 
> 
> ___
> 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

Apple Notarization changes...

[Paul Dupuis via use-livecode]

I got an email from Apple Developer date 13-Jun-2023 that:

"We’re reaching out because you recently used the altool command-line 
utility to notarize your macOS software with Apple. As announced last 
year at WWDC22, if you’re still using altool with the Apple notary 
service, you should transition to the notarytool command-line utility as 
soon as possible. Notarizing software with altool was deprecated in 
Xcode 13, and the Apple notary service will no longer accept uploads 
from altool as of November 1, 2023. Existing notarized software will 
continue to function properly. "


So, my questions for the Hivemind and/or the Mothership are:

1) I currently code sign and notarize using some version of Xcode under 
Mojave on a MacBook Pro. I do not really want to upgrade the OS from 
Mojave. The MacBook pro literal only function is macOS code signing and 
notarization. It sits off line and doesn't get any updates because I am 
terrified some update will break the code signing and notarization 
process. So, is there a version of Xcode that will run on Mojave and 
supports the new notarytool (vs attool as the terminal command - I have 
been using is "xcrun altool -type osx --notarize-app --primary-bundle-id 
... etc.")?

What is the minimum OS/Xcode combination that lets me use notarytool?

2) Has Livecode (or anyone else) updated lessons. documentation, help 
apps, etc, for using this new notarytool? If so, can anyone point me to it?


November 1 is still a ways off, but I find Apple Notarization so 
incomprehensible that once I get a set of steps to work, I document them 
and follow them verbatim and the thought of trying to figure out what 
this change means is daunting!




___
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: Shell + Python?

[Bob Sneidar via use-livecode]

OK mine are definitely different. So what changed? Virtually everything I used 
for shell in the past worked without a problem but at some point in the recent 
updates this changed. 

So then what is the solution? Obviously I am going to have to change the shell 
for LC, and not the one for Terminal. LC’s shellCommand is /bin/sh. The 
terminal is zsh so I set Livecode’s shellCommand to /bin/zsh. The path changed 
but is still different from what I grep in the terminal!! 

Shouldn’t there be a way to tell LC what the default shell is in the terminal?? 

Bob S


> On Jul 15, 2023, at 4:35 PM, Mark Wieder via use-livecode 
>  wrote:
> 
> On 7/15/23 10:05, Geoff Canyon via use-livecode wrote:
> 
>> So any idea why terminal can find python but LC's shell function can't?
> 
> Your user context is different from LC's shell context. Try
> 
> put shell("env | grep PATH") # in the message box
> 
> and
> 
> env | grep PATH  # in terminal
> 
> If you want to launch python from LC's shell you'll have to have it in LC's 
> path somewhere, or at least an alias to it in the path.
> 
> -- 
> 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: Search for an app in Google Play Store

[Klaus major-k via use-livecode]

Hi Bob,

> Am 17.07.2023 um 17:20 schrieb Bob Sneidar via use-livecode 
> :
> 
> I bet the dashes mean something in the search algorithm. 

well, maybe.

However that entering a misspelled app name will lead to a successfull find is 
really ridiculous!
sehen - hören - merkn -> App found (missing E renders this to a NON german 
word!) 
instead of
sehen - hören - merken -> no result 8-)

> Bob S
> 
>> On Jul 17, 2023, at 1:10 AM, Klaus major-k via use-livecode 
>>  wrote:
>> ...
>> just received a response from Google.
>> It is completely generic, does not make any sense to me, but it looks like 
>> they do NOT 
>> search for the correct and complete title of an app in their database. :-/
>> Maybe I do not understand it correctly?
>> 
>> Hi Klaus,
>> 
>> Thanks for contacting Google Play Developer Support.
>> 
>> Google Play app search works across title, developer name, and app 
>> descriptions. 
>> Your title should be unique and accessible, avoid common terms, and 
>> reinforce 
>> what your app is about.
>> 
>> Using common or generic words like "Puzzle" or "Sports" can often increase 
>> the 
>> total number of potential search results, thus making your app more 
>> difficult to find. 
>> Using the search phrase Sehen-Hören-Merken forces our search engine to 
>> autocorrect 
>> the search term and return results as if the search term were "Sehen - Hören 
>> - Merken" (in quotes).
>> 
>> For more information about Google Search Operators, please see this Google 
>> Search Help Center article.
>> ...
>> 

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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: Search for an app in Google Play Store

[Bob Sneidar via use-livecode]

I bet the dashes mean something in the search algorithm. 

Bob S


> On Jul 17, 2023, at 1:10 AM, Klaus major-k via use-livecode 
>  wrote:
> 
> Hi all,
> 
>> Am 14.07.2023 um 22:36 schrieb J. Landman Gay via use-livecode 
>> :
>> 
>> On 7/14/23 7:16 AM, Klaus major-k via use-livecode wrote:
>>> I am looking for a support email at GOOGLE Dev.
>>> My problem is the search engine of Google Play Store.
>>> Just like the subject says. ;-)
>> 
>> Oh right, I'm supposed to read the subject title. Oops. This is the closest 
>> thing I could find:
>> 
>> 
>> They don't make it easy.
> 
> just received a response from Google.
> 
> It is completely generic, does not make any sense to me, but it looks like 
> they do NOT 
> search for the correct and complete title of an app in their database. :-/
> 
> Maybe I do not understand it correctly?
> 
> Hi Klaus,
> 
> Thanks for contacting Google Play Developer Support.
> 
> Google Play app search works across title, developer name, and app 
> descriptions. 
> Your title should be unique and accessible, avoid common terms, and reinforce 
> what your app is about.
> 
> Using common or generic words like "Puzzle" or "Sports" can often increase 
> the 
> total number of potential search results, thus making your app more difficult 
> to find. 
> Using the search phrase Sehen-Hören-Merken forces our search engine to 
> autocorrect 
> the search term and return results as if the search term were "Sehen - Hören 
> - Merken" (in quotes).
> 
> For more information about Google Search Operators, please see this Google 
> Search Help Center article.
> ...
> 
> 
> Best
> 
> Klaus
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
> 
> 
> ___
> 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: Android and USB footswitch

[Klaus major-k via use-livecode]

Hi friends,

FYI: I solved the problem!

1. For testing I ordered the cheapest USB footswitch fom Mr. Pesos -> 15.99 Euro
2. Also ordered an USB-A to Micro-USB adapter
3. Downloaded the software for setting up the footswitch, there is even a Mac 
version!
4. Configured the footswitch to act as a mouseclick
5. Tested with a quick LC app on my Android tablet and...
... IT WORKS, hooray! :-)

The P.S. in my initial posting is still waiting for an answer. :-)

> Am 25.05.2023 um 17:22 schrieb Klaus major-k via use-livecode 
> :
> 
> Hi friends,
> 
> I'm still an active musician (bass guitar) and am currently playing in four 
> bands.
> 
> Nowadays bulky music stands on stage are OUT and tablets are IN!
> So I am considering to create a little app for myself to display PDF 
> leadsheets 
> (= lyrics and chord symbols) on an Andorid tablet, which I still have to buy. 
> :-)
> 
> There are some USB footswitches, and I would like to use one of them to 
> browse 
> through the (multipage) PDFs (next page, previous page).
> 
> Anyone knows if these switches will act like an "external keyboard", means if 
> they 
> will just send any RAWKEY that I could catch in LC? 
> Or will I need something created with LCB to do so?
> 
> Thanks for any hint!

P.S.
Since PDFs are not accessible via "mobilepickmedia" are there ANY other ways to 
add 
some PDFs later without having to download them from some URL?

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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: Search for an app in Google Play Store

[Klaus major-k via use-livecode]

Hi all,

> Am 14.07.2023 um 22:36 schrieb J. Landman Gay via use-livecode 
> :
> 
> On 7/14/23 7:16 AM, Klaus major-k via use-livecode wrote:
>> I am looking for a support email at GOOGLE Dev.
>> My problem is the search engine of Google Play Store.
>> Just like the subject says. ;-)
> 
> Oh right, I'm supposed to read the subject title. Oops. This is the closest 
> thing I could find:
> 
> 
> They don't make it easy.

just received a response from Google.

It is completely generic, does not make any sense to me, but it looks like they 
do NOT 
search for the correct and complete title of an app in their database. :-/

Maybe I do not understand it correctly?

Hi Klaus,

Thanks for contacting Google Play Developer Support.

Google Play app search works across title, developer name, and app 
descriptions. 
Your title should be unique and accessible, avoid common terms, and reinforce 
what your app is about.

Using common or generic words like "Puzzle" or "Sports" can often increase the 
total number of potential search results, thus making your app more difficult 
to find. 
Using the search phrase Sehen-Hören-Merken forces our search engine to 
autocorrect 
the search term and return results as if the search term were "Sehen - Hören - 
Merken" (in quotes).

For more information about Google Search Operators, please see this Google 
Search Help Center article.
...


Best

Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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