From: Frank C. <fc...@pu...> - 2004-12-18 18:04:43
|
I received this bit of feedback on J from a TestMaker developer: > On a more positive note, I like the new screen layout. J seems to > be a good editor and well integrated. The only other problem I have > found is with the File->Open dropdown and Open button, they don't do > the expected operation of bringing up a file manager window, but > seem to rather try to open whatever is listed in the location bar. > Close, New and Save all seem to work as expected. Save As I would > have expected a File Manager type window though. What do you think about changing the File-Open menu to open a Standard File Selector? -Frank --- Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374 7426 Author of "Java Testing and Design: From Unit Tests to Automated Web Tests" from Prentice Hall, details at http://thebook.pushtotest.com |
From: Peter G. <pe...@ar...> - 2004-12-19 04:13:20
|
On Sat, 18 Dec 2004 at 10:04:41 -0800, Frank Cohen wrote: > I received this bit of feedback on J from a TestMaker developer: > > > On a more positive note, I like the new screen layout. J seems to > > be a good editor and well integrated. The only other problem I have > > found is with the File->Open dropdown and Open button, they don't do > > the expected operation of bringing up a file manager window, but > > seem to rather try to open whatever is listed in the location bar. > > Close, New and Save all seem to work as expected. Save As I would > > have expected a File Manager type window though. > > What do you think about changing the File-Open menu to open a Standard > File Selector? I've always tried to avoid that sort of thing. -Peter |
From: Frank C. <fc...@pu...> - 2004-12-19 05:34:22
|
I'm curious to learn why you avoid "that sort of thing"? -Frank On Dec 18, 2004, at 8:13 PM, Peter Graves wrote: > On Sat, 18 Dec 2004 at 10:04:41 -0800, Frank Cohen wrote: >> I received this bit of feedback on J from a TestMaker developer: >> >>> On a more positive note, I like the new screen layout. J seems to >>> be a good editor and well integrated. The only other problem I >>> have >>> found is with the File->Open dropdown and Open button, they don't >>> do >>> the expected operation of bringing up a file manager window, but >>> seem to rather try to open whatever is listed in the location bar. >>> Close, New and Save all seem to work as expected. Save As I would >>> have expected a File Manager type window though. >> >> What do you think about changing the File-Open menu to open a Standard >> File Selector? > > I've always tried to avoid that sort of thing. > > -Peter > > --- Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374 7426 Author of "Java Testing and Design: From Unit Tests to Automated Web Tests" from Prentice Hall, details at http://thebook.pushtotest.com |
From: Peter G. <pe...@ar...> - 2004-12-19 13:08:22
|
On Sat, 18 Dec 2004 at 21:34:17 -0800, Frank Cohen wrote: > I'm curious to learn why you avoid "that sort of thing"? For one thing, Ctrl O in j can be used to open things like FTP directories, web pages and IMAP folders, in addition to local files. For a quick example, try adding enableWeb = true enableExperimentalFeatures = true to ~/.j, and then do Ctrl O and enter "http://www.cnn.com/". The "Standard File Selector" provides no support for these non-standard features. In addition, j tries to avoid unnecessary dialogs. Ctrl O, Ctrl T and Alt X (and Ctrl F if useIncrementalFind is true) all follow this principle and try to use the location bar in a consistent way. If you load key-pressed.lisp in ~/.j/init.lisp, you can even do Ctrl O, then change your mind on the fly and do Alt X with focus still in the location bar. If you need the kind of functionality that the "Standard File Selector" provides, you can do Ctrl D to get a directory buffer, use the directory buffer to navigate to the file you're interested in, and then do Ctrl Enter to open that file and close the directory buffer in a single operation. I don't think directory buffers provide exactly the same functionality as the "Standard File Selector", but I'm pretty sure they could be extended to do so, if someone cared enough to do the work. -Peter |
From: Frank C. <fc...@pu...> - 2005-01-05 21:03:14
|
Hi Peter: Thanks for the reply. I'm glad you've given this so much thought. I've been using J for the past two months and I'm now really liking it. There is a bit of a learning curve to it because it doesn't use the standard file selector. After learning it I like your methods better. (Anything that is less modal is a plus in my book.) I just got TestMaker 4.3 out the door today so it will take a little while to dig into J's experimental features. I'm excited to see what you've included. -Frank On Dec 19, 2004, at 5:08 AM, Peter Graves wrote: > On Sat, 18 Dec 2004 at 21:34:17 -0800, Frank Cohen wrote: >> I'm curious to learn why you avoid "that sort of thing"? > > For one thing, Ctrl O in j can be used to open things like FTP > directories, web pages and IMAP folders, in addition to local files. > > For a quick example, try adding > > enableWeb = true > enableExperimentalFeatures = true > > to ~/.j, and then do Ctrl O and enter "http://www.cnn.com/". > > The "Standard File Selector" provides no support for these non-standard > features. > > In addition, j tries to avoid unnecessary dialogs. Ctrl O, Ctrl T and > Alt X (and Ctrl F if useIncrementalFind is true) all follow this > principle and try to use the location bar in a consistent way. > > If you load key-pressed.lisp in ~/.j/init.lisp, you can even do Ctrl O, > then change your mind on the fly and do Alt X with focus still in the > location bar. > > If you need the kind of functionality that the "Standard File Selector" > provides, you can do Ctrl D to get a directory buffer, use the > directory buffer to navigate to the file you're interested in, and then > do Ctrl Enter to open that file and close the directory buffer in a > single operation. > > I don't think directory buffers provide exactly the same functionality > as the "Standard File Selector", but I'm pretty sure they could be > extended to do so, if someone cared enough to do the work. > > -Peter > > --- Frank Cohen, PushToTest, http://www.PushToTest.com, phone: 408 374 7426 Author of "Java Testing and Design: From Unit Tests to Automated Web Tests" from Prentice Hall, details at http://thebook.pushtotest.com |