From: Kevin K. <kk...@us...> - 2009-05-06 19:59:59
|
Hi list, I'd like to see J continue since it is nice, small editor with many features. I've put together the most recent release as a first step, but now the question is 'what next?' I think at a minimum, J could use a little UI refresh -- those old gnome icons are looking a little stale. :) So, how do you use J and how often? What features of J are your favorite? What don't you use J for? How many J users are out there, anyway? Kevin |
From: Ludovico M. <lu...@qi...> - 2009-05-06 20:33:04
|
On Wed, May 6, 2009 at 9:42 PM, Kevin Krouse <kk...@us...> wrote: > > I'd like to see J continue since it is nice, small editor with many > features. I've put together the most recent release as a first step, > but now the question is 'what next?' First of all, thanks for the latest release. It really was a nice surprise. :) My personal "most wanted" list: * SQL syntax support * SVN (should be fairly easy hacking the existing CVS support) * faster multi-line regexps Nice but not really important features: * better ssh support (eg create new remote files) * cleaner icons/graphics in the class browser Features that might attract new users: * a way to use the HTML browser without resorting to a key combination * a graphical way to use code folding * better support for sessions > I think at a minimum, J could use a little UI refresh -- those old gnome > icons are looking a little stale. :) They are not splendid, but I have to say I'm used to them. > So, how do you use J and how often? What features of J are your > favorite? What don't you use J for? How many J users are out there, > anyway? I spend most of my coding time in J, as it's my primary and only editor. I also use it for quick format conversions/cleanup when I'm too lazy to open the Python console or write a script. My favourite features are its speed, unobtrusiveness, clean font support (I hate antialising), ease of installation (unpack, copy the .j folder, and start working), list searching, screen splitting, and a few others I don't remember right now. I wish I knew Java enough to help... L. ps - I can't remember if this address was the one subscribed to the list, I'm sending you a copy to be on the safe side. |
From: Kevin K. <kk...@us...> - 2009-05-08 03:39:41
|
Hi Ludovico, Thanks for all the good suggestions! Ludovico Magnocavallo wrote: > On Wed, May 6, 2009 at 9:42 PM, Kevin Krouse > <kk...@us...> wrote: >> I'd like to see J continue since it is nice, small editor with many >> features. I've put together the most recent release as a first step, >> but now the question is 'what next?' > > First of all, thanks for the latest release. It really was a nice surprise. :) Yeah, I was getting tired of waiting for a release.. :) > > My personal "most wanted" list: > > * SQL syntax support > > * SVN (should be fairly easy hacking the existing CVS support) I've started this to get my feet wet with the code. > > * faster multi-line regexps > > Nice but not really important features: > > * better ssh support (eg create new remote files) > > * cleaner icons/graphics in the class browser > > Features that might attract new users: > > * a way to use the HTML browser without resorting to a key combination Do you mean viewing html file you are currently editing with J's html viewer? That would be nice. > > * a graphical way to use code folding Yes, I've wanted this as well. > > * better support for sessions > Yes, the providing a menu of saved sessions would be nice. >> I think at a minimum, J could use a little UI refresh -- those old gnome >> icons are looking a little stale. :) > > They are not splendid, but I have to say I'm used to them. > >> So, how do you use J and how often? What features of J are your >> favorite? What don't you use J for? How many J users are out there, >> anyway? > > I spend most of my coding time in J, as it's my primary and only > editor. I also use it for quick format conversions/cleanup when I'm > too lazy to open the Python console or write a script. > > My favourite features are its speed, unobtrusiveness, clean font > support (I hate antialising), ease of installation (unpack, copy the > .j folder, and start working), list searching, screen splitting, and a > few others I don't remember right now. > > I wish I knew Java enough to help... The J code base is pretty easy to get around in. Give it a try! > > L. > > ps - I can't remember if this address was the one subscribed to the > list, I'm sending you a copy to be on the safe side. |
From: Jan-Wijbrand K. <jw...@n-...> - 2009-05-06 21:11:12
|
On May 6, 2009, at 9:42 PM, Kevin Krouse wrote: > > I'd like to see J continue since it is nice, small editor with many > features. I've put together the most recent release as a first step, > but now the question is 'what next?' > > I think at a minimum, J could use a little UI refresh -- those old > gnome > icons are looking a little stale. :) > > So, how do you use J and how often? What features of J are your > favorite? What don't you use J for? How many J users are out there, > anyway? A big thanks for putting effort in this! I'm using J as my main text editor for writing Python (including so called doctests), Javascript, Restructured Text, and XML-based languages on a day-to-day basis, at home and at work. Every now and then I try to switch to Emacs, which works reasonably well for me in case of Python and Javascript but *not at all* for XML based languages - the insert element and insert empty element functionality in XML mode is just to darn convenient in J :_) So after a little while - usually a matter of hours - I return to my beloved J... Features I like and use all the time and I cannot use to having implemented differently in other editors: * Find, Find-in-files - notice the autocompletion of words still works in the dialogs! * Replace, Replace-in-files * Window splitting * Listing occurences of whatever is selected (or the word just after the cursor) * Shift + Arrow Up|Down selects whole line * Intelligent indentation of XML and Python code * Directory buffer * The compile function, which basically is just passing the buffer to whatever command you specify, lovely! * The apply command on region function - I use it to pass larger blocks of comments to the fmt command or to pass complete XML trees to, for example, xmllint * The simple way of customizing the global and mode-specific keymaps * Insert element and insert empty element functions in XML mode - it is just lovely how you can type the attributes of elements right there in the dialog already, and after hitting Enter have the cursor there to continue editting the element. Never a saw a general purpose code editor do it that good. * The open file functionality * The open directory for the current file kb shortcut * There's probably lots of things I forgot... Things that I'd like improved: * A quick way (kb shortcut) to have a buffer similar to the directory buffer, listing all currently open files (I never use the sidebars) Typing out the "things I like" list makes me realize how much I got accustomed to J over the past eight, or is it nine(!) years. I wish I had a bit more time to freshen up my Java skills and help out... I should really try of course... I'll start by looking at the latest relaase. Thanks again! regards, jw -- Jan-Wijbrand Kolman jw...@n-... |
From: Kevin K. <kk...@us...> - 2009-05-08 04:04:30
|
Hi Jan-Wijbrand, Jan-Wijbrand Kolman wrote: > > On May 6, 2009, at 9:42 PM, Kevin Krouse wrote: >> >> I'd like to see J continue since it is nice, small editor with many >> features. I've put together the most recent release as a first step, >> but now the question is 'what next?' >> >> I think at a minimum, J could use a little UI refresh -- those old gnome >> icons are looking a little stale. :) >> >> So, how do you use J and how often? What features of J are your >> favorite? What don't you use J for? How many J users are out there, >> anyway? > > A big thanks for putting effort in this! > > I'm using J as my main text editor for writing Python (including so > called doctests), Javascript, Restructured Text, and XML-based languages > on a day-to-day basis, at home and at work. > > Every now and then I try to switch to Emacs, which works reasonably well > for me in case of Python and Javascript but *not at all* for XML based > languages - the insert element and insert empty element functionality in > XML mode is just to darn convenient in J :_) So after a little while - > usually a matter of hours - I return to my beloved J... I've tried to switch to emacs many times myself. :) > > > Features I like and use all the time and I cannot use to having > implemented differently in other editors: > > * Find, Find-in-files - notice the autocompletion of words still works > in the dialogs! > > * Replace, Replace-in-files > > * Window splitting > > * Listing occurences of whatever is selected (or the word just after the > cursor) > > * Shift + Arrow Up|Down selects whole line > > * Intelligent indentation of XML and Python code Ah, we've got a Python indentation bug on the bug tracker: http://sourceforge.net/tracker/?func=detail&aid=2712145&group_id=55057&atid=475785 We should probably see how other editors handle 'outdenting' after a Python class definition. > > * Directory buffer > > * The compile function, which basically is just passing the buffer to > whatever command you specify, lovely! > > * The apply command on region function - I use it to pass larger blocks > of comments to the fmt command or to pass complete XML trees to, for > example, xmllint > > * The simple way of customizing the global and mode-specific keymaps > > * Insert element and insert empty element functions in XML mode - it is > just lovely how you can type the attributes of elements right there in > the dialog already, and after hitting Enter have the cursor there to > continue editting the element. Never a saw a general purpose code editor > do it that good. > > * The open file functionality > > * The open directory for the current file kb shortcut > > * There's probably lots of things I forgot... > > Things that I'd like improved: > > * A quick way (kb shortcut) to have a buffer similar to the directory > buffer, listing all currently open files (I never use the sidebars) That's a cool idea. I like it! > > > Typing out the "things I like" list makes me realize how much I got > accustomed to J over the past eight, or is it nine(!) years. I wish I > had a bit more time to freshen up my Java skills and help out... I > should really try of course... I'll start by looking at the latest > relaase. Thanks again! > > > regards, > jw > > -- > Jan-Wijbrand Kolman > jw...@n-... > > > |