Re: Set Image Reference to Relative Path

 Jacque wrote: It used to be that resources were copied into the same folder with the app executable. Then Apple changed the rules and disallowed resources like images and documents at that location. Instead, they had to go into  a "resources" folder, separate from the executable. -- So if I r

Re: Error: Unable to open the database file

Peter: Glad my stack was a help. Be careful with my mySQL php scripts. The examples are meant only as starting points. They allow for injection attacks if the inputs aren’t carefully filtered in Livecode before being formed into the query. You could modify the php so that each script does only a

Slash S in shortcut

Hello! I have a client who says they are getting a "the socket is closed" error when attempting to launch my LiveCode (7.0.1) EXE (which tries to download some files on launch). The EXE runs fine on some of their computers but not on others. I have many, many other clients that have no proble

Re: Error: Unable to open the database file

On 04/06/2016 02:12 PM, Peter Haworth wrote: I just can't be bothered replying to that... On Wed, Apr 6, 2016 at 1:55 PM Mark Wieder wrote: On 04/06/2016 01:03 PM, Peter Haworth wrote: I'm just as lazy as the next developer Oh, I could probably give you a run for your money in the lazy ra

Re: Error: Unable to open the database file

I just can't be bothered replying to that... On Wed, Apr 6, 2016 at 1:55 PM Mark Wieder wrote: > On 04/06/2016 01:03 PM, Peter Haworth wrote: > > > I'm just as lazy as the next developer > > Oh, I could probably give you a run for your money in the lazy race any > day. > > -- > Mark Wieder >

Re: Volunteer github guru for documentation submissions?

On 04/06/2016 01:49 PM, Peter TB Brett wrote: What happens when you type "how do I contribute to LiveCode documentation" into Google? The top hit is https://livecode.com/resources/guides/developers-guide/ and even though that's the wrong place to end up, it shouldn't be necessary to resort t

Re: Volunteer github guru for documentation submissions?

On 04/06/2016 01:44 PM, J. Landman Gay wrote: You know, even just linking to the blog post from github would have done the trick. We just need some kind of discoverable pathway over there. Nice idea. Seconded. -- Mark Wieder ahsoftw...@gmail.com ___

Re: Error: Unable to open the database file

On 04/06/2016 01:03 PM, Peter Haworth wrote: I'm just as lazy as the next developer Oh, I could probably give you a run for your money in the lazy race any day. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lis

Re: Volunteer github guru for documentation submissions?

On 06/04/2016 21:41, J. Landman Gay wrote: On 4/6/2016 3:17 PM, Ali Lloyd wrote: Jacque, you may want to read this blog post https://livecode.com/putting-the-you-in-documentation/ I did, back when you posted it, and that's what made me decide I should pitch in. But I no longer had the refere

Re: Volunteer github guru for documentation submissions?

On 06/04/2016 21:44, J. Landman Gay wrote: On 4/6/2016 3:17 PM, Ali Lloyd wrote: Jacque, you may want to read this blog post https://livecode.com/putting-the-you-in-documentation/ You know, even just linking to the blog post from github would have done the trick. We just need some kind of disc

Re: Volunteer github guru for documentation submissions?

On 4/6/2016 3:17 PM, Ali Lloyd wrote: Jacque, you may want to read this blog post https://livecode.com/putting-the-you-in-documentation/ You know, even just linking to the blog post from github would have done the trick. We just need some kind of discoverable pathway over there. -- Jacquelin

Re: Volunteer github guru for documentation submissions?

On 4/6/2016 3:17 PM, Ali Lloyd wrote: Jacque, you may want to read this blog post https://livecode.com/putting-the-you-in-documentation/ I did, back when you posted it, and that's what made me decide I should pitch in. But I no longer had the reference handy. I'd like to see an easy way to ge

Re: Volunteer github guru for documentation submissions?

Jacque, you may want to read this blog post https://livecode.com/putting-the-you-in-documentation/ On Wed, Apr 6, 2016 at 7:25 PM J. Landman Gay wrote: > On 4/6/2016 1:45 AM, Monte Goulding wrote: > > I hadn’t seen the contributing to the docs guide so even though I > > know my way around GitHub

Re: Error: Unable to open the database file

Hi Mark, Now you've got me worried! I had the impression that since the php scripts run on my server and access the mySQL database on the same server, there wouldn't be any sql injection issues, particularly since I never send any SQL statements from my client app to the server. I'm just as lazy

Re: Error: Unable to open the database file

This is where it gets interesting. My original plan was to directly connect to mySQL from Livecode using the variableslist parameter to the various Livecode db functions, which should protect against sql injection. To be honest, I don't recall why I went away from that plan in favor of middleware.

Re: Error: Unable to open the database file

On 04/06/2016 10:35 AM, Ray wrote: Yeah, my expectation is that we'll avoid injection issues using the PHP middleware. No, sql injection is avoided by proper coding and by paying attention. PHP as a platform is notoriously subject to sql injection errors mostly because its ease of use encour

Re: Error: Unable to open the database file

I do remember a post from you about not being able to send multiple statements to SQL in one Livecode call, and also I'm pretty sure it was confirmed. so that's probably what you're thinking of. On Wed, Apr 6, 2016 at 10:17 AM Dr. Hawkins wrote: > On Wed, Apr 6, 2016 at 9:42 AM, Peter Haworth

Re: Error: Unable to open the database file

Very interesting. I've looked a little into postgreSQL, not that much. I think we've pretty much decided to stick with mySQL for now, it should work for our purpose, but you've peaked my interest in postgreSQL. Many thanks for your input on this Richard! On 4/6/2016 3:13 PM, Dr. Hawkins wrot

Re: Error: Unable to open the database file

I'd actually be happy with emails if they included everything I need and excluded unnecessary stuff, but we've had a lot of problems in the past relying on general emails so we're going to try something which should help guide our users to writing good bug reports. On 4/6/2016 2:55 PM, EED-wp

Re: Error: Unable to open the database file

On Wed, Apr 6, 2016 at 10:38 AM, Ray wrote: > So Richard, what did you end up going with when neither sqLite nor mySQL > worked out for you? postgreSQL It's more mature in some ways than mySQL, but more importantly, I can give compound transaction (there's a 500+ statement query on client open

Re: Error: Unable to open the database file

Ray Good idea. I just get bug reports emailed to me. That's why I send the email by accessing a php mail system on my server. That way the user doesn't have to have email installed. William Prothero http://ed.earthednet.org > On Apr 6, 2016, at 8:32 AM, Ray wrote: > > Richard - thanks for th

Re: Volunteer github guru for documentation submissions?

On 4/6/2016 1:45 AM, Monte Goulding wrote: I hadn’t seen the contributing to the docs guide so even though I know my way around GitHub it was fresh eyes on finding the docs. Here’s what I did: - openhttps://github.com/livecode/livecode/ That was my first hurdle. You already knew to go to the l

Re: Error: Unable to open the database file

I haven't gotten that far into the database syntax and Livecode's handling of it yet so I couldn't say, yet. But I'm sure I'll figure out soon what, if any, Livecode's limitations are. So Richard, what did you end up going with when neither sqLite nor mySQL worked out for you? On 4/6/2016

Re: Error: Unable to open the database file

Yeah, my expectation is that we'll avoid injection issues using the PHP middleware. All in all, it seems like a pretty common need; to store on a server a database that multiple users are going to be updating. I wish there were some sort of a Livecode lesson which detailed several approaches

Re: "this me" vs "me"

Ah, very good. so this goes to the method of dynamically setting behaviros run time. "cool!" On April 5, 2016 at 5:49:23 PM, Scott Rossi (sc...@tactilemedia.com) wrote: Using "this me" gets you the long id of the object (button/stack) serving as a control's behav

Re: Error: Unable to open the database file

On Wed, Apr 6, 2016 at 9:42 AM, Peter Haworth wrote: > > mySQL does have transactions, as do all SQL implementations. They're part > of the SQL spec. postGresql may well have advantages over mySQL but that > isn't one of them. > Now I'm trying to remember: is it that livecdoe that can't succes

Re: Error: Unable to open the database file

On Wed, Apr 6, 2016 at 8:32 AM, Ray wrote: > Richard - thanks for this advice. It's really quite helpful. We've > abandoned the sqLite idea but I think mySQL should work fine. The purpose > of this database is to maintain an index of bug reports. The bug reports > themselves are actually Livec

Re: Error: Unable to open the database file

Hi Ray, Lots of things for you to think about! As someone else mentioned, I thought you were using a network file system rather than a web server. Just to set the record straight on a couple of things. mySQL does have transactions, as do all SQL implementations. They're part of the SQL spec. p

Re: Volunteer github guru for documentation submissions?

The guides are a long read. If I get up the motivation, I'm going to at least try to work on them so it doesn't feel so much like work. On Wed, Apr 6, 2016 at 11:10 AM, Devin Asay wrote: > > > On Apr 6, 2016, at 12:38 AM, J. Landman Gay > wrote: > > > > On 4/5/2016 10:26 AM, Mark Wieder wrote:

Re: Error: Unable to open the database file

Richard - thanks for this advice. It's really quite helpful. We've abandoned the sqLite idea but I think mySQL should work fine. The purpose of this database is to maintain an index of bug reports. The bug reports themselves are actually Livecode stacks. The database will serve as an index

Re: Error: Unable to open the database file

On Wed, Apr 6, 2016 at 6:05 AM, Ray wrote: > I thought of downloading it, updating it, and then putting it back on the > server but that wouldn't work if two users simultaneously did so. Since > I'll have many users using the database simultaneously everything has to be > done on the server. I

Re: Volunteer github guru for documentation submissions?

> On Apr 6, 2016, at 12:38 AM, J. Landman Gay wrote: > > On 4/5/2016 10:26 AM, Mark Wieder wrote: >> But I do want to say that there's fascinating reading in >> https://github.com/livecode/livecode/pull/3518#issuecomment-205199749 > > It's only fascinating if you understand all the jargon. I re

Re: Volunteer github guru for documentation submissions?

On Wed, Apr 6, 2016 at 2:38 PM, J. Landman Gay wrote: Monte's already pointed you to Ali's Web Interface Instructions. > Why are the doc files in the *engine* category? Wouldn't one logically > look in the IDE category? When you use the Web Interface the docs are logically located in the comm

Re: Error: Unable to open the database file

Bill thanks for sharing this with me. I've downloaded it and I'm looking into now. I'll let you know how it works out. On 4/6/2016 10:26 AM, Earthednet-wp wrote: Ray, I have a stack for MySQL implementation that might help you get started, since you are thinking of using php as middleware. I

Re: Error: Unable to open the database file

Ray, I have a stack for MySQL implementation that might help you get started, since you are thinking of using php as middleware. It's at http://es.earthednet.org/SoftwareForEducation Scroll to the bottom of the page. Good luck. Bill William Prothero http://es.earthednet.org > On Apr 6, 2016, at

Re: Error: Unable to open the database file

Thanks for your confirmation on this, Mike. We'll continue with the PHP middleware plan. It seems to be industry standard and it makes sense, especially from a security standpoint. On 4/6/2016 10:15 AM, Mike Bonner wrote: Actually, you CAN connect directly to to mysql server (its actually a

Re: Error: Unable to open the database file

Thanks Mike. I've used Andre's solutions a number of times and they've always worked really well. I wasn't aware of this one. On 4/6/2016 10:21 AM, Mike Bonner wrote: On an "LC server" side note, andre garzias dblib is really helpful. It might be possible to build up your query locally using

Re: Error: Unable to open the database file

On an "LC server" side note, andre garzias dblib is really helpful. It might be possible to build up your query locally using dblib, then send the resulting array to the server that also uses dblib, set the array there and execute the action. (dblib works great) I think it will work with either

Re: Error: Unable to open the database file

Actually, you CAN connect directly to to mysql server (its actually a server in its own right) if you set things up that way. You have to change where connections are allowed from but honestly, you're still better off using middleware. This way you can place any files with sensitive data (password

Re: Error: Unable to open the database file

Mike - thanks for your help here. You're absolutely right about the need for some kind of middleware and although I've never setup nor used Livecode Server I find the idea kind of intriguing. For now I've asked my son who I work with daily to write the middleware piece using PHP. This should

Re: Error: Unable to open the database file

I actually haven't created the database yet so I guess it makes sense to use mySQL from the beginning instead of sqLite, thus eliminating the need to import one into the other. Nonetheless, I'll still need middleware as I don't think Livecode can make direct calls to a mySQL database on a serv

RE: Error: Unable to open the database file

Ray, An http file reference is not a valid UNC for read/write file access. If you want to connect remote users to a DB then import the SQLite DB into a MySQL DB and have the users connect to the MySQL server and all the record locking would be in place. You could go LC server middleware but that w

Re: Error: Unable to open the database file

Mike Bonner wrote: > You can write your own middleware using LC server if you have it set > up on your remote. Does anyone here know of a good tutorial on using LC Server as DB middleware? This comes up a lot, and it would be great to have a URL to pass around. Related: anyone here using An

Re: Error: Unable to open the database file

You can write your own middleware using LC server if you have it set up on your remote. I'm afraid I don't know enough about sqlite concurrency issues and how to handle them, but since the server that has your sqlite is an http server (I think most of us had been thinking it was a local network sh

entitlement Mac OS

Hi all, My app for Mac was rejected for the second time. The message sais that I use to many entitlements. The only one I use is PRINTER. I am on Maverik (10.9.5), using LC 6.7.3. I use App Wrapper 3.5.2 from Ohanaware to sign and make PKG. The last time I submitted this app to Apps Store I cho

Re: Widgets' Use Cases and Bytes Added to App

On Apr 5, 2016, at 10:10 PM, Sannyasin Brahmanathaswami wrote: > Oh No! I think I just lit a fire that will put me yet another learning > curve. (smile) OH well... keeps the gray cells green! I have a bumper sticker on my car that reads "Oh, no, not another learning experience!" -- Peter Pet

Re: Error: Unable to open the database file

I thought of downloading it, updating it, and then putting it back on the server but that wouldn't work if two users simultaneously did so. Since I'll have many users using the database simultaneously everything has to be done on the server. I know only one user can write to an sqLite databas

LC8 odd window behavior in IDE on windows

Hello, developing on Windows 7 First time I am testing LC 8 a little more as the basics, I am struggling with the behavior of the IDE windows. The code editor window often minimizes to the task bar, especially when debugging. When clicking on the task bar icon it doesn't open again. You either

Re: Volunteer github guru for documentation submissions?

> On 6 Apr 2016, at 4:45 PM, Monte Goulding wrote: > >> Why are the doc files in the *engine* category? Wouldn't one logically look >> in the IDE category? I didn’t answer this bit. For the most part the documentation is not documenting the IDE so it makes more sense for it to be in the engin