@Raul,

Refresh: 3

…works a treat. Besides giving a conspicuous indication in the Safari
toolbar that the "animated" window is alive and kicking.
All no doubt horribly inefficient. But good enough in the short term for my
experiments.

Mac:Activity Monitor does show the resource usage of both processes:
jconsole and Safari to rise steadily, however. (In the case of jconsole,
might this be due to a memory leak?)

> I probably need to upgrade my jhs implementation before your code would
work for me.

I doubt it. My message.ijs example is an undocumented hack of j805 JHS – it
doesn't use any recently introduced features. But the trouble with
undocumented hacks is that they may break in future JHS releases.

So when I come to write this up, I'll probably plump for the <meta…>
technique (thanks Stefano, and others), let JHS monopolize the construction
of hrtemplate, which it owns anyway, and instead rebuild HBS out of
MESSAGE__ before calling jhr_jhs_ in the conventional way.

@Devon – thanks for that. Now why didn't I think of consulting
stackoverflow.com?

On Tue, Sep 5, 2017 at 1:54 PM, Raul Miller <rauldmil...@gmail.com> wrote:

> That's pretty much it. The browser is in control here, and jijx is
> only indirectly in control as a result.
>
> Probably the simplest would be to put something like Refresh: 3 in the
> http headers in your MYTEMPLATE (before the first blank line). But I
> haven't tested that - I probably need to upgrade my jhs implementation
> before your code would work for me.
>
> Thanks,
>
> --
> Raul
>
>
> On Tue, Sep 5, 2017 at 8:27 AM, Ian Clark <earthspo...@gmail.com> wrote:
> > Currently I'm hacking it by using Keyboard Maestro to execute a timer
> which
> > reloads the message URL every 3 seconds.
> >
> > I guess much the same thing could be done using Javascript embedded in
> > message.ijs? – if I knew any Javascript.
> >
> > Another expedient is to write out the message display to a textfile
> > (~/message.txt) and open it using TextWrangler. This (unlike TextEdit)
> > refreshes its display window whenever message.txt is rewritten.
> >
> > But these expedients are inelegant. I guess web browsers were not
> designed
> > to do this sort of thing. (Or designed not to do this sort of thing?)
> >
> > On Tue, Sep 5, 2017 at 2:59 AM, Ian Clark <earthspo...@gmail.com> wrote:
> >
> >> Suppose I am a JHS coder, working with the J session (the jijx page),
> and
> >> have written an app called "message" (say). This generates a page of
> data
> >> in response to the URL:
> >>
> >> http://localhost:65001/message
> >>
> >> which I choose to display in a separate browser window. Let's call it
> the
> >> message window.
> >>
> >> If I execute some phrase in jijx which changes the content of the
> message
> >> window, then in the normal course of things I would need to manually
> reload
> >> the page in order to see the altered data. For example (in Safari) by
> >> activating the message window and clicking the symbol: "Reload this
> page".
> >>
> >> How can I write a verb (to be executed in jijx) which refreshes the
> >> message window without having to do that?
> >>
> >>
> > ----------------------------------------------------------------------
> > 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

Reply via email to