Here is a screen shot to show how it might look:
http://www.jsoftware.com/jwiki/DavidMitchell?action=AttachFile&do=view&target=jdemo9lab.png
--
On 1/16/2011 13:43, David Mitchell wrote:
> I think a link s a good alternative to opening a new tab or window.
>
> I must admit, I have found the current use of 'open' to open a new window a
> bit
> jarring and distracting in labs. And, I find the magically multiplying plot
> windows a bit of a pain.
>
> Is it worth considering a multiple frame window for concurrent text display as
> in jdemo9? I find myself using the Win7 50/50 screen split more and more
> often
> to show an active window and a context window.
>
> --
>
> On 1/16/2011 12:16, Eric Iverson wrote:
>> I was hoping to avoid this for the first release, but the use of open in
>> labs is going to be a nuisance.
>>
>> I have taken to heart (so far) the rule strongly favored by some web
>> programmers that opening windows/tabs with javascript is a bad bad thing.
>> That is, windows/tabs should only be opened by explicit user actions that
>> cause the browser to open a new window/tab. I have taken this to mean that
>> the user must click a link (with ctrl/shift as they wish). The use of open
>> is a bit contrary to this.
>>
>> I wonder if the following definition of open would be of interest:
>>
>> open_z_=: 3 : 0
>> t=. ('jijs?mid=open&path=',jpath y)jhref_jhs_ y
>> jhtml'<div contenteditable="false">',t,'</div>'
>> )
>>
>> Sentence
>> open'~temp/foo.ijs'
>> puts a link to open the file in the jijx window.
>>
>> Comments?
>>
>> On Sun, Jan 16, 2011 at 11:40 AM, David Mitchell<[email protected]>wrote:
>>
>>> I noticed that there are several labs that use 'open' to display source
>>> files.
>>>
>>> Is there any way that jhs can open a new browser (or tab) as a replacement
>>> for open?
>>> --
>>>
>>> On 1/16/2011 11:15, Eric Iverson wrote:
>>>> This probably won't be fixed in time for the release. Work on cleaning up
>>>> labs can be pursued seriously by several people after the release is out.
>>>>
>>>> For this lab what is required is that the dlltest.cpp file be changed to
>>> a
>>>> somewhat simpler .c file and that is handle 32/64 windows/linux
>>>> requirements. Then the lab needs edited to say the binary needs to be
>>> built
>>>> for the users platform and the rest of the lab should then run.
>>>>
>>>> On Sun, Jan 16, 2011 at 5:42 AM, David Mitchell<[email protected]
>>>> wrote:
>>>>
>>>>> Lab: DLL: Writing and Using a DLL
>>>>> ...
>>>>> ── (3 of 58) overview (ctd) ─────────────────────────────────
>>>>> The next step opens dlltest.cpp.
>>>>>
>>>>> Study it and position it so you can refer to it. Whenever a
>>>>> new procedure is mentioned, take a look at its definition.
>>>>> )
>>>>>
>>>>> ── (4 of 58) overview (ctd) ─────────────────────────────────
>>>>> )
>>>>> open '~system\examples\dllwrite\dlltest.cpp'
>>>>> |value error: open
>>>>> | open'~system\examples\dllwrite\dlltest.cpp'
>>>>> |[-0]
>>>>>
>>>>> ---
>>>>> JVERSION
>>>>> Engine: j701/2011-01-10/11:25
>>>>> Library: 7.01.034
>>>>> Platform: Win 64
>>>>> Installer: j701a_win64.exe
>>>>> InstallPath: c:/users/me/j64_j701b/j64-701
>>> ----------------------------------------------------------------------
>>> 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
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
