> From: Dan Bron > > 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. >
As I see it we aren't "switching to a browser frontend". It seems to me that the browser frontend will become an additional option that will have advantages for some scenarios. For "traditional" J development, the proposed GTK front end should provide a similar (but improved and more portable?) environment to the current jwdw and jwdp. In addition it sounds as though the jwdw interface should continue to be available for some time to come. True, the base install won't include any of that functionality "out of the box" and the default GUI interface will be the browser in the interests of keeping the base small, however the other options will be available for download via Package Manager. I do think it is important that it is easy to move to the other available environments/front ends, see: http://www.jsoftware.com/pipermail/beta/2009-December/003615.html ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
