The jhs in the browser is still there even if the server goes away. Restarting J and jhs can then easily start again. On 23 Aug 2015 15:40, "Björn Helgason" <[email protected]> wrote:
> J on the android very often dies when not in use. > That does not mean I will stop using it. > The input log does not stay between sessions but I most often use scripts > anyway. > I do want to start jhs easily from J. > I do go between jhs and J terminal with the toggle. > I can then also share names between them. > J in the background sounds ok but doing it my way I like better. > On 23 Aug 2015 14:20, "bill lam" <[email protected]> wrote: > >> Yes, no doubt the jhs can start, but once you use a browser as the front >> end, j become an invisible activity, and then android os can kill it >> sooner >> or later. If j activity has been killed, the browser front end will also >> stop working. >> >> A more sophiscated solution is to run j as an invisible background service >> similar to the JKeyboard, but that will be another project. >> >> IMO a more practical method is to run jhs on a raspberry pi. It can run >> 24x7, energy saving and cheap. I did not use jhs but I ran a web server >> and >> a ssh server on it last year. >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
