R.E.Boss' question and Eric's response made me wonder what other conveniences we might be losing by switching to a browser frontend for J development, and how we might compensate for them.
One big loss that springs to mind is wdclipcopy and wdclipread . J is my primary scripting language and general computer utility, so I use these verbs all the time, for ad hoc parsing of data (e.g. phone bills), quick calculations (e.g. expense report sanity checking), and more. Since the server's clipboard is obviously different from the client's, I'm worried that I'll lose these tools, and wondering how we can compensate [1], and generally what other tools we might be losing. Can anyone tell me what other habits I might have to change? Obviously, any broken tools would come at the boundary between J and the machine, because J's staying the same, "the machine" has a new definition. -Dan [1] Put a "paste here" frame in the UI?, have the 11!:0 callback ask Javascript for favors? ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
