I'm not sure, but don't think the start is necessary. All it does is ensure
that stuff starts in another window and in already is going to do that in
this case. I don't think it changes the mapping of file to application to
launch. Is it possible that all that is needed is that all browser launches
use the code that is already in browser.ijs?
----- Original Message -----
From: "Sherlock, Ric" <[EMAIL PROTECTED]>
To: "Beta forum" <[email protected]>
Sent: Thursday, February 14, 2008 5:23 PM
Subject: RE: [Jbeta] Info Button on Package manager fails in j & k win32
builds
This works fine for me as long as a web browser is defined in
Edit|Configure|External Programs. If not, I also get the following
error.
------
error in: pmview_binfo_button
domain error: wd
wd'winexec *',cmd
------
I think this is because the command for calling the default browser
(browser_view and dfltbrowser_jbrowser_) currently resolves under win32
as:
wd 'winexec * "<url>"'
Which doesn't work. The following would:
wd 'winexec ',DEL,'cmd /C start "" "<url>"',DEL,'sw_hide'
To fix the problem I'd consider changing launch_jbrowser_ to work with
URLs as well as filenames and then use it rather than duplicating the
same mechanism in browser_view. I don't think this would be too hard.
For example ...
launch[6] from:
cmd=. 'cmd /C ',quoteit cmd
to:
cmd=. 'cmd /C start "" ',quoteit cmd
and a mechanism for recognizing a url rather than a filename in the
following else. block. Example ...
else.
browser=. quoteit browser
if. (# <: '://' i.&1@:E. ]) cmd do.
cmd=. '/' (I. cmd='\') } cmd
cmd=. 'file://',cmd
end.
cmd=. quoteit cmd
cmd=. browser,' ',cmd
show=.''
end.
browser_view in pacman.ijs could then be simplified to just:
browser_view=: 3 : 0
require '~system/extras/util/browser.ijs'
launch_jbrowser_ y
)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Baker
Sent: Friday, 15 February 2008 05:49
To: Beta forum
Subject: [Jbeta] Info Button on Package manager fails in j &
k win32 builds
Just a little ticky-boo problem I noticed today.
When you click the Info button for a particular addon in now throws a
domain error. Previously
it took you to the wiki page describing the addon. I noticed
this in the J
win32 build but it also
fails in the current k win32 beta.
jdb
----------------------------------------------------------------------
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
