best way to open a script-only library stack?

[Curtis Ford via use-livecode]

--When you start using a script-only stack, LC creates a temporary hidden
--stack in RAM and assigns the script to it. It's there but not visible.

Ah ha... now at least I don't feel silly for not finding it.

And it is in the Project Browser too – I may have opened it from there once 
actually, and was then puzzled why I got a conflict from opening the file 
another time.

Thanks Jacque! I'll owe you a coffee or beer or something in San Jose. :)

Curt

--
Sent from Postbox 


___
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

best way to open a script-only library stack?

[Curtis Ford via use-livecode]

I'm just getting started with the idea of a library stack for scripts, 
and have a dopey question: what's the best way to edit the library as I 
work on the project?


I've created a script-only stack and included

start using stack "myScriptStack.livecodescript"

in the preOpenStack handler of my main stack.

When I open the main stack, I don't see a way to get to the library 
stack. So I open the library stack through 'recent files' in Livecode, 
but then I see the message "A stack [library stack name] in file [path 
to the main stack file] is already in memory. The LiveCode UI does not 
distinguish stacks which have identical names, so editing these stack 
files while both are in memory could result in data loss."


If this is a real concern, how do I get back to work on the library 
stack? Any suggestions on best practices?


Curt

Sent from Postbox 


___
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

filename in standalones for Mac - changed recently?

[Curtis Ford via use-livecode]

I'll file this under "things I wish I'd known about a few years ago"...

put specialfolderpath("resources")&  "/media/" into gMediaPath


More elegant, change-proof, and works. Thanks Klaus! :)

-Curt
--
Sent from Postbox 


___
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

filename in standalones for Mac - changed recently?

[Curtis Ford via use-livecode]

The other day when firing up TextWrangler, I saw the message that Apple 
now shows once when opening a 32bit app – that it should be updated (for 
64bit). Which got me thinking about older Livecode projects.


A few years ago I did a series of modules for a client (using Livecode 
7) that included many mp3 files, in a folder named 'media' and accessed 
through a player. I had used this in the stack script:


on setgMediaPath
   global gMediaPath

//---SET THE MEDIA PATH; for some reason this MUST be in 
its own handler, not in openStack or preOpenStack

   set the itemDelimiter to slash
   put the effective fileName of this stack into gMediaPath
   delete the last item of gMediaPath
   put gMediaPath & slash & "media" & slash into gMediaPath

end setgMediaPath

Today I opened up a module in LiveCode 9, chose Mac OS X 64-bit, and 
made a standalone, but the sound files didn't play. After rummaging 
around in the package and some experimenting, it seems the module now 
wants sound files to be in


APPNAME/APPNAME.app/Contents/Resources/_MacOS/media/

The dictionary for 9.0 has this cryptic entry for 'filename':

"The use of was deprecated in version 8.1 of LiveCode with new defaults 
for and as true on all systems apart from pre OS X 10.8. The Windows 
build of LiveCode no longer supports any features and setting the and
will have no effect. Additionally does not include 64 bit support and 
therefore can not be supported on OS X 64 bit builds of LiveCode."


1) If the client wants to go ahead and update for 64bit compatibility at 
some point, will I need to go into each module and replace


   put gMediaPath & slash & "media" & slash into gMediaPath

with

put gMediaPath & slash & "Resources" & slash & "_MacOS" & slash & 
"media" & slash into gMediaPath



2) Any other issues to be aware of when managing this transition?

Thanks!

Curt
--
Sent from Postbox 


___
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

script/engine broken when moved to 64bit server at JaguarPC

[Curtis Ford via use-livecode]

I've received this from JaguarPC:


[Sun Sep 10 01:51:36.334093 2017] [cgid:error] [pid 22868:tid 
139689650484992] [client 69.73.180.11:50074] End of script output before 
headers: keygentest.cgi


That occurs when a script has insufficient permissions but I couldn't 
find any script having incorrect permissions in the account. Also we 
have checked there has been no dependency issue either.


You have SSH access enabled on your account so your developer should be 
able to login and investigate the cause of this issue through debugging 
on shell. If he finds anything wrong with the setup, he can update us 
regarding that.


We have now following Perl version installed on the new server, you 
might want to regenerate the executable lccgi to ensure it is compatible 
with following version:


==
[root@sagitarius cgi-bin]# perl -v

This is perl 5, version 16, subversion 3 (v5.16.3) built for 
x86_64-linux-thread-multi


(with 34 registered patches, see perl -V for more detail)

Besides that Bobsled server has similar setup so I am afraid, moving to 
that server will help actually.


We have now live chat support working which you can access through our 
official website. If you want to chat with us, you are most welcome.


Please let us know if we can be of further assistance.

Regards,
Bilal | L3 Support Representative
--

I don't have the skills to debug through shell (that's why I like to use 
a tool like Livecode!) and I can't regenerate the Livecode engine..!


Our script (which I haven't touched) and the engine both have 
permissions set to 755. Sagitarius (which they currently have us on) and 
bobsled (where Jacque has a setup that's working) are both 64bit servers 
running CentOS 7.


Curt

--
Sent from Postbox 


___
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: script/engine broken when moved to 64bit server at JaguarPC

[Curtis Ford via use-livecode]

JaguarPC hasn't answered the question about dependencies directly, 
though they did pass on this:



 /lib/ld-linux.so.2: bad ELF interpreter: No such file or 
directory


..which suggests a dependency issue, I guess?

But they've also said
Correct, the initial error was due to using a 32bit compiled static 
binary. The second issue is it's looking for a config file that isn't 
there. You would need to upload a working config file. Does this make 
better sense?
We've never had to deal with a config file before. Is this necessary for 
using the 64bit server?

--
Sent from Postbox 


___
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: script/engine broken when moved to 64bit server at JaguarPC

[Curtis Ford via use-livecode]

It's the 500 internal server error.

I'm pretty - er, very new to troubleshooting on a server. I don't have 
SSH access. Is there a way to get a list of the dependencies of the 
32bit and 64bit engines that I could forward to JaguarPC? I know someone 
else has the 32bit engine working on JaguarPC, though it may be on a 
different server.


How would I run the engine from the command line?

Thanks!

Curt
--
Sent from Postbox 


___
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

script/engine broken when moved to 64bit server at JaguarPC

[Curtis Ford via use-livecode]

For several years I've had a system on JaguarPC involving a simple 
script that calls Livecode server, with script and server engine in the 
cgi-bin folder. Last weekend we were moved to 'sagitarius,' a 64bit 
server, and our system has broken.


I tried uploading the 64bit version (from 
LiveCodeServer-8_1_6-Linux-x86_64.zip) and setting permissions to 755, 
but without success. JaguarPC isn't familiar with Livecode and hasn't 
been able to suggest anything; the older, 32bit server we were on, 
peach, has been retired and we can't go back to it.


Any ideas of what to try? Our system hasn't needed any of the drivers or 
externals that come with the livecode-server file.


Thanks!

Curt
--
Sent from Postbox 


___
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