... but you are not me. Anyways, here is my point of view:
First, I am never going to use JHS from another machine, because JHS does not deal with network security issues. So I am only going to let it listen on localhost. Second, if I am starting jhs, any old jijx browser session is stale and will give me errors if I try to use it. Third, when I want to use J I do not want a laborious process before I can use my J sentences. -- Raul 2011/12/28 Björn Helgason <gos...@gmail.com>: > As far as I am concerned I do not see this as one event. > > You start the JHS server and it is not related to the event of opening a > gui or using services from the server. > The server is just there after you start it and is waiting for requests. > It may be on the same machine but it can also be on another machine. > You can open many sessions and ask for services from the server. > > When you open a browser you can have a tab or several tabs open with > different views and getting a tab with jal or help or demo or ijx or ijs > and so on so it is no natural start of the JHS server and then what tabs, > browsers or machines will use it. > > 2011/12/28 Raul Miller <rauldmil...@gmail.com> > >> I find myself not using jhs very often, mostly because of its >> multi-step startup. >> >> But that's relatively easy to fix, temporarily at least. I can edit >> j64-701/addons/ide/jhs/core.ijs and add a line at the bottom: >> >> browse_j_ 'http://127.0.0.1:65001/jijx' >> >> Except... this is not a very good approach. If nothing else, every >> time core.ijs gets updated, I lose the change. Also, I do not know >> how stable that port number is. >> >> So, taking a step back, I could change the jhs startup script, adding >> to the command line that starts J. >> >> Perhaps something like changing the tail >> >> ... -js " init_jhs_'' " >> >> to >> >> ... -js " browse_j_ URL_jhs_ [] init_jhs_'' " >> >> except that is not going to work either. One issue here is that >> URL_jhs_ is not a url. Why? I am not sure. >> >> But that's easy to fix -- I can just use the literal url, in its >> place... except that that's not working for me. I am not sure why. >> >> Perhaps the minds that think about the design of this part of the >> system could consider if there might be a nice way of approaching this >> issue? >> >> Thanks, >> >> -- >> Raul >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
