> From: Eric Iverson > > Thanks for the feedback. Your suggestions warrant investigation. The > key point is that with the power of html/css/javascript everything you > suggest (and too much more) is easy to do.
Agreed. > Although the eventual usability of jfile is very important, I suggest > that > we take it as a given that it can and will be done. For now it might be > better to focus on bigger issues. Is this a fruitful direction? Are > users going to cry over the fading of j.exe? Are J users going to > embrace enough html/css/javascript to make there own GUI > applications? Have browser standards converged enough that this > route provides very good portability. Etc. I was under the mistaken impression that the decision had already been made that the browser interface had merit. I certainly agree that for some usage cases a browser interface will be really powerful including for casual development. However I don't currently see it being *my* main interface to the J engine for development purposes. For that I'm looking forward to the proposed new Gtk-based front end. I imagine others will continue to use Emacs and the jconsole. For traditional GUI applications that I previously would have used j.exe to develop, I'm imagining that the new Gtk interface will provide more fully-featured GUI tools/events than are available currently using J.exe. My fear (hopefully unwarranted) is that it may not be so easy to use. I'm certainly hoping that J.exe will continue to run my existing apps in the meantime. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
