Re: LiveCode server IDE

2020-10-13 Thread Keith Clarke via use-livecode
Hi Alex, Thanks for the description of your workflow, toolset and dev/test rig - an interesting direction of travel, especially as it extends to my current setup. I really like the division of labour between the LC IDE for LC and Coda for html, CSS and native sync to server. Nice too, the

Re: LiveCode server IDE

2020-10-12 Thread Alex Tweedly via use-livecode
Hi Keith, My workflow is not much different from Ralph's. Short answer:  - edit in IDE, test in IDE  - upload to server using Coda 2  (which I also use to edit non-lc files). Long answer:  - I don't use any of the LCserver specific features -  no entangled html, no includes, ... -

RE: LiveCode server IDE

2020-10-12 Thread Ralph DiMola via use-livecode
- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Keith Clarke via use-livecode Sent: Monday, October 12, 2020 10:49 AM To: use-livecode@lists.runrev.com Cc: Keith Clarke Subject: Re: LiveCode server IDE Thanks for the response, Ralph. I've struggled to retain/regain

Re: LiveCode server IDE

2020-10-12 Thread Keith Clarke via use-livecode
Thanks for the response, Ralph. I've struggled to retain/regain my old local Sites, web server and LC Server on my home Macs. So, I was thinking of embarking down the script-only stacks route, using an on-rev LC-Server instance to do any web-services heavy-lifting work server-to-server, on

RE: LiveCode server IDE

2020-10-12 Thread Ralph DiMola via use-livecode
Keith, As a follow up... If you have a web server with LC installed running on your local machine then just a ctrl S in the LC IDE will let you test your server script(stack) immediately in the currently open IDE instance. IDE alternatives to edit LC script only stacks are many. I use the Atom

RE: LiveCode server IDE

2020-10-12 Thread Ralph DiMola via use-livecode
I use the standard issue LC IDE to edit the server script, do a "Ctrl S" and use either a web disk or VPN to drag the saved file to the server. Then I test my web service in the currently opened IDE. Fast debug cycle. Easy-peezy... Ralph DiMola IT Director Evergreen Information Services

Re: LiveCode server IDE - the current state of the art?

2018-07-22 Thread Keith Clarke via use-livecode
t; >> I like the ‘work locally as usual, then upload’ approach - coupled with the >> essential 'Did everything synch?' check utility! :-) >> >> The lightweight LCS hub is very appealing (probably without RevIgniter to >> avoid any additional complexity) to get the basic

Re: LiveCode server IDE - the current state of the art?

2018-07-20 Thread Alex Tweedly via use-livecode
roach - coupled with the essential 'Did everything synch?' check utility! :-) The lightweight LCS hub is very appealing (probably without RevIgniter to avoid any additional complexity) to get the basic plumbing connected. Time to hit the LCS lessons to see if I can replicate what you're achieving

Re: LiveCode server IDE - the current state of the art?

2018-07-20 Thread Keith Clarke via use-livecode
plumbing connected. Time to hit the LCS lessons to see if I can replicate what you're achieving with 20-lines, methinks! :-) Best, Keith > From: Alex Tweedly > To: use-livecode@lists.runrev.com > Subject: Re: LiveCode server IDE - the current state of the art? > Message-ID: > Con

Re: LiveCode server IDE - the current state of the art?

2018-07-19 Thread Alex Tweedly via use-livecode
I have no idea if this is state of the art or not :-) - but here's what I do ... Short answer : the Livecode IDE plus an FTP client (Filezilla). Longer answer : 99% of what I write for the LC server is standard LC - scriptonly stacks, used as library stacks. I have about 20 lines of LCS -