Hi Mathias, No more than the ones that you will be able to use from within the standard iDE as long as you insert your own trace tags in your server’s stack code, mainly as « return it/the result » ones.
To the end, you will see how easy it’s to go and, more than that, if your server’s stacks use a MVC design and an SQL back-end for data storage. To the end, your server’s stacks are going to become so lightweight that there will no be place anymore for bugs ;D Note 1: on the yearly average time i spend in LC n-tier development tasks, 90% of the time is spent in client-side (web, mobile, desktop) modeling/coding and 10% in about server-side stacks and SQL modeling/coding. Note 2 : any server’s stack intended to serve web apps will never being best build than in using the fantastic Ralf Bitter's Revigniter port of the PHP’s CodeIgniter framework. What else : if i right remember, you use extensively PostgreSQL as your preferred SQL back-ends, is’t ? ;D Best, Pierre Début du message réexpédié : > De: Matthias Rebbe | M-R-D <matthias_livecode_150...@m-r-d.de> > Objet: Rép : on-rev Client > Date: 14 octobre 2014 20:25:06 UTC+2 > À: How to use LiveCode <use-livecode@lists.runrev.com> > Répondre à: How to use LiveCode <use-livecode@lists.runrev.com> > > > I, for one, will give that a try. > > But there is one thing i am really missing. On-Rev client had a really useful > debug function. > Saved me lot of time back then. > > Matthias > > Am 14.10.2014 um 20:16 schrieb Pierre Sahores <s...@sahores-conseil.com>: > >> Hi All, >> >> The on-rev client used to be a good intention and tool but, with the time, >> it began to appears to me as an complex alternative to a lots more easy way >> to go. Here is the one i use instead to stay more comfortable with all the >> lc-server development tasks : >> >> 1.- web, mobile or desktop client-side apps intended to send http POST (to >> be preferred in about security tasks) or GET requests to lc-server have to >> be set to send them to a « gateway.lc » script of the following format : >> >>> <?lc >>> >>> try >>> >>> start using stack "yourappserverstack.livecode" >>> get yourappserverstackglobalsinitializationprocedure() >>> get yourappserverstackglobalsinitializationcontroler() >>> >>> catch tErr >>> try >>> >>> start using stack "yourappserverstackclone.livecode" >>> get yourappserverstackglobalsinitializationprocedure() >>> get yourappserverstackglobalsinitializationcontroler() >>> >>> catch tErr >>> put "Maintenance at work. Thanks to wait some minutes before >>> renewing your response..." >>> >>> end try >>> >>> end try >>> >>> ?> >> >> Where stack « yourappserverstackclone.livecode" is the copy of the main >> server’s stack intended to respond instead of it in one case only : because >> the just updated "yourappserverstack.livecode » is, for some seconds, >> unavailable because in the process to be erased/uploaded on the server. >> >> It’s always a good security related measure to choose to install both « >> gateway.lc » script, « yourappserverstack.livecode » and « >> yourappserverstackclone.livecode » the cgi-bin directory of your app’s >> domain main directory. >> >> ... >> >> At this point, all the « hard work » is over ;D >> >> The next step is to open your preferred FTP client app (Transmit or >> Cyberduck on mac, Cyberduck or FileZilla on PC, etc…) and to right-clic « >> yourappserverstack.livecode » to open it in your preferred LC Desktop IDE >> version as long as it is >= LC 6.0 (or perhaps 5.02 or 5.5, i can’t remember >> the right back-compatibility to apply there) to avoid legacy file-fomat >> possible troubles at the time you wants to save your server’s stack >> modifications as soon as the job is done. >> >> ... >> >> It’s not the first time i expose this way to go and Andre Garcia reported, >> on its own, the same way to go. It just works perfectly for years and, >> because, list archive are not always consulted as they should, i wanted to >> refresh this ;D >> >> Best, >> >> Pierre >> >> >> >> Le 14 oct. 2014 à 18:05, Jim Lambert <j...@netrin.com> a écrit : >> >>> on-rev client has also stopped working for me when going to Tio. >>> >>> Jim Lambert >>> >>> _______________________________________________ >>> 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 >> >> -- >> Pierre Sahores >> mobile : 06 03 95 77 70 >> www.sahores-conseil.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 > > > _______________________________________________ > 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 -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.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
