Thanks for the details. I now see what is happening. JHS core.ijs doesn't load all the url app scripts. Instead creates stubs do the loads when required. In particular, when JHS starts and core.ijs is loaded it creates a stub for jev_get_jal_ that will load jal.ijs when required. But this means that getting the jal page from an old browser page doesn't get the script loaded and won't work.
I like that url app scripts aren't loaded until needed but this doesn't work with using old browser. I need to think about this a bit. Note that this is not the only problem with old browser pages. They can always represent a state that is no longer correct and what you have shown is just another, perhaps nastier, version of this. I may not have a nice fix for this in time for the release and at least for now am unlikely to go back on the decision to use stub to load to load pages as required. On Sat, Jan 15, 2011 at 11:43 AM, Raul Miller <[email protected]> wrote: > On Sat, Jan 15, 2011 at 11:13 AM, Eric Iverson <[email protected]> > wrote: > > jal 'not installed' works as expected for me in what I think are the > > circumstances you describe. Perhaps you could give more details. > > I just tried this again. > > I started jhs consol session > I opened browser jhs session > I upgraded jhs and base library in browser jhs session > I exited the jhs console session > I restarted jhs console session > I pressed "not installed" button in browser jhs session > nothing seemed to happen > > I switched to jijx window in browser jhs session, and saw: > |value error: jev_jal_ > | jev_jal_ 0 > *** response not sent for jal > *** html402 (leave page as is) sent > > I went to jal link again in browser jhs session > "not installed" button worked when I revisited the page > > > I prefer jal in the menu over pacman or other short phrases I can > > think of. None of them will make sense to someone who has > > no backbround. But in that case you should go go help and > > a quick browse will help. jal has the advantage of being the > > app (url) name as are all the other standard link items. > > Ok. > > But I was not suggesting that the menu entry get a > different name. I was suggesting that the menu entry > get a tooltip. > > In other words, change: > > <a href="jal" class="jhml" onclick="return jmenuhide();" > onblur="return jmenublur(event);" onfocus="return jmenufocus(event);" > onkeyup="return jmenukeyup(event);" onkeydown="return > jmenukeydown(event);" onkeypress="return > jmenukeypress(event);">jal</a> > > to something like > > <a href="jal" class="jhml" onclick="return jmenuhide();" > onblur="return jmenublur(event);" onfocus="return jmenufocus(event);" > onkeyup="return jmenukeyup(event);" onkeydown="return > jmenukeydown(event);" onkeypress="return jmenukeypress(event);" > title="J Application Library">jal</a> > > You could also change the href if it is purely decorative. > > FYI, > > -- > 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
