Hmm... This is an interesting point of view - it essentially treats the things which trigger event handlers like any interactive input.
And that makes a certain amount of sense. But... the architectural implications are rather steep, though I suppose they should be thought of as a resource limitation. (At some point you start running into conflicts between models of what is supposed to happen, as well as limitations of external frameworks.) Thanks, -- Raul On Sat, Nov 15, 2014 at 9:57 AM, Henry Rich <[email protected]> wrote: > I thought about that, but if the 'routines' are all called from the same > event, there would not be a prompt in between, since the prompt would be > emitted only at the end of the event handler. > > If the routines are different invocations of event handlers, there would be > prompts in between - good or bad depending on your taste, I think. > > If you wanted to suppress the prompt after the event handler (which I > personally think is a bad idea, since the user is used to seeing the 3 > spaces), you could just make sure that there is an empty line below the last > typed line. The user could then cursor to that line and use it as an input > area, though it wouldn't have the ' ' prompt. > > One recurring issue on console output is how to handle the old-fashioned > prompt where the machine types 'Enter name: ' and the user types on the same > line. I don't know how we do this now: is it 1!:2 to write the prompt, then > 1!:1 to read the reply? If so, this would not be a return to immediate mode > and should not emit a ' ' prompt. > > Henry Rich > > On 11/15/2014 1:26 AM, Raul Miller wrote: >> >> I can think of a case where it makes sense to leave the term window >> "without an input prompt": >> >> When you want to use smoutput several times in a row (perhaps from >> inside several different routines). >> >> That said, if there were some way for J to send an incomplete line to >> the console, you could re-issue the prompt that was hidden by your >> output. >> >> Thanks, >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
