ECB + JDE window focus bug - suggestion for solution (was: RE: ECB + JDE window focus bug)
Hi Klaus, Wouldn't a simpler solution be for efc to define either a variable whose value is a window for displaying the dialog or a function that returns a window for displaying the dialog. For example, efc-dialog-window If efc-dialog-window is nonnil, efc would display the dialog buffer in the specified window and then restore the buffer that it was originally displaying. Otherwise, efc would create a temporary window and delete the temporary window after the user dismisses the dialog buffer. Fixed layout tools like ECB could set this variable to the window in which they would like the dialog to be displayed. Another or additional solution would be for the efc to define the following variable: efc-frame-dialog-p If this variable is nonnil, efc would display the dialog buffer in a separate frame centered on the user's screen. If this variable is nil, it would display the dialog buffer in the window specified by efc-dialog-window. Your thoughts? - Paul Berndl, Klaus writes: But i would vote for the following enhancement of efc.el: Offering 4 new hooks: A) ecb-show-dialog-before-hook B) ecb-show-diaolg-after-hook C) ecb-close-dialog-before-hook D) ecb-close-dialog-after-hook What would be the advantages of these hooks: A tool like ECB (which has such durable windows whcih prevent the efc-dialogs to work correct) could temporary delete its durable compile/etc/stuff-window temporary in the new hook ecb-show-dialog-before-hook so the efc-mechanismus described at beginning (point 1, 2) can work correct. And could also recreate its durable window after the efc-dialog has closed in the hook ecb-close-dialog-after-hook. You see really necessary are only hooks a) and D) but B) and C) could also be senseful (maybe)... Thoughts? IMHO it would not be a big deal for JDEE/efc but would offer big advantages for tools like ECB to work better with JDEE under all circumstances. In general such hooks would be good on every place JDEE creates and deletes windows. Please give me feedback! Ciao, klaus -Original Message- From: Le Wang [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 5:03 PM To: [EMAIL PROTECTED] Subject: ECB + JDE window focus bug. Hi, When I use 'jde-import-find-and-import' in ECB with a compile window, the prompt window that asks for clarification pops up in the compilation buffer. This is fine. But then, it doesn't have an idea where to put the import statement. Is there a setting in JDE/ECB that I can tweak to correct this? Recreate Problem: 1. emacs -q 2. setup loadpaths 3. load jde, ecb 3. find asdf.java 4. customize ecb-layout to use a compilation window. 5. ecb-activate. 6. With adsf.java in edit window, and focus in same window, do `jde-import-find-and-import' 7. Import ParseException class, choose any of the choices, click ok 8. Now the import statement is in my scratch buffer. Thanks. -- Le __ Post your free ad now! http://personals.yahoo.ca
Re: i'm sorry but a cannot install JDE yet ! (correct link to installation script)
Try Artur Hefczyc's fetch-and-install-jde script. It can be downloaded from: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/wttools/wttools/em it does it all, alone you just have to wait and see, :-) Please note that url to this script is very long so it is broken into 2 lines. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/wttools/wttools/em acs-stuff/install-jde.sh?rev=1.8content-type=application/x-sh I hadn't put it somewhere outside CVS repository because didn't know that it might be interesting for more people. I try to do during coming weekend, so url also be easier to use. Artur -- Artur Hefczyc http://wttools.sf.net/
Re: i'm sorry but a cannot install JDE yet ! (correct link to installation script)
Hi Artur, I plan to put the script on the JDEE website in the download section. It would be helpful if you could write a brief description of what the script does, what it requires, and how to run it so that it installs the JDEE in the location desired by the user. - Paul Artur Hefczyc writes: Try Artur Hefczyc's fetch-and-install-jde script. It can be downloaded from: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/wttools/wttools/em it does it all, alone you just have to wait and see, :-) Please note that url to this script is very long so it is broken into 2 lines. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/wttools/wttools/em acs-stuff/install-jde.sh?rev=1.8content-type=application/x-sh I hadn't put it somewhere outside CVS repository because didn't know that it might be interesting for more people. I try to do during coming weekend, so url also be easier to use. Artur -- Artur Hefczyc http://wttools.sf.net/
RE: ECB + JDE window focus bug - suggestion for solution (was: RE: ECB + JDE window focus bug)
FWIW I have an efc replacement for XEmacs that doesn't use buffers or windows at all. It would be nice if we could keep the level of abstraction up in efc so that platform specific hooks don't start creeping in. andy Wouldn't a simpler solution be for efc to define either a variable whose value is a window for displaying the dialog or a function that returns a window for displaying the dialog. For example,
tags?
Hi, Does anyone use tags with jdee? I fail to see the point of them. And it seems to add an extra layer of complexity, i.e. constantly updating the tags table. Or is it that I just don't get the tags concept? -- Le __ Post your free ad now! http://personals.yahoo.ca
Re: Jde and voice recognition
also scan the blind programming list: [EMAIL PROTECTED] and other disabled lists for some real pros on using emacs with assisted technologies. -- [EMAIL PROTECTED] On Tue, 2003-02-25 at 10:50, Jonathan Epstein wrote: Ben, See the JDE controlled by voice at: http://voicerecognition.org/developers/jepstein/pbvdemos/ specifically: http://voicerecognition.org/developers/jepstein/pbvdemos/javabyvoicereenactment/index.html An annotated version of the movies appears at: http://voicerecognition.org/developers/jepstein/pbvdemos/javabyvoicereenactment/annottest1.zip Among the other resources, check out the VoiceCoder mailing list: http://www.onelist.com/community/VoiceCoder Good luck, Jonathan At 01:17 PM 2/25/2003 -0500, you wrote: This is a search for kindred spirits, who might wish to share tips or techniques: I use the JDE because I need to write Java code in my profession, and because I need to use voice recognition due to a repetitive strain injury. By combining the JDE with the VR-mode program and Dragon System macros I can create a reasonably efficient programming environment and I never need to touch the keyboard. I know of no other IDE that offers the same capabilities, so for me the JDE has really been a godsend. Is there anybody out there in the same boat? Ben [EMAIL PROTECTED] -- Jeff Suttor[EMAIL PROTECTED]
RE: ECB + JDE window focus bug - suggestion for solution (was: RE: EC B + JDE window focus bug)
Hi Paul, yes, indeed, this sounds smarter then the hook-solution! But nevertheless IMHO a package can not have enough hooks where other packages can plugin - IMHO there is no disadvantage for efc.el offering such hooks. But back to your suggestions: Yes, a variable efc-dialog-window which can be set by other packages would be great. In this case efc must not delete this window but has to restore the original buffer (like you describe). A word to your other suggestion about using extra frames: Maybe we should go one step more forward and generalizing efc.el so it is independed from using buffer, windows, frames at all. Maybe efc.el should offer a well-defined interface for a) displaying all the stuff and an implementation has only to satisfy this interface but can display all the stuff in any arbitrary suitable manner - for exmaple XEmacs has a really powerful dialog-implementation (make-dialog) so for example real windows-dialogs could be used to display the efc-contents. b) hitting ok c) hitting cancel d) closing the display-medium (buffer, window, frame, OS-dialog, popup-menu etc...) efc.el itself could then offer standard-implementations of these interfaces which uses buffer/windows and buffers/frames for display. Hmm, maybe this is not easy but would be great... But for the beginning your suggested ecb-dialog-window would be great (maybe you could then also add some hooks - is not much effort :-)) Thanks, Klaus -Original Message- From: Paul Kinnucan [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 7:11 PM To: Berndl, Klaus Cc: 'Le Wang'; [EMAIL PROTECTED]; 'Paul Kinnucan' Subject: ECB + JDE window focus bug - suggestion for solution (was: RE: EC B + JDE window focus bug) Hi Klaus, Wouldn't a simpler solution be for efc to define either a variable whose value is a window for displaying the dialog or a function that returns a window for displaying the dialog. For example, efc-dialog-window If efc-dialog-window is nonnil, efc would display the dialog buffer in the specified window and then restore the buffer that it was originally displaying. Otherwise, efc would create a temporary window and delete the temporary window after the user dismisses the dialog buffer. Fixed layout tools like ECB could set this variable to the window in which they would like the dialog to be displayed. Another or additional solution would be for the efc to define the following variable: efc-frame-dialog-p If this variable is nonnil, efc would display the dialog buffer in a separate frame centered on the user's screen. If this variable is nil, it would display the dialog buffer in the window specified by efc-dialog-window. Your thoughts? - Paul Berndl, Klaus writes: But i would vote for the following enhancement of efc.el: Offering 4 new hooks: A) ecb-show-dialog-before-hook B) ecb-show-diaolg-after-hook C) ecb-close-dialog-before-hook D) ecb-close-dialog-after-hook What would be the advantages of these hooks: A tool like ECB (which has such durable windows whcih prevent the efc-dialogs to work correct) could temporary delete its durable compile/etc/stuff-window temporary in the new hook ecb-show-dialog-before-hook so the efc-mechanismus described at beginning (point 1, 2) can work correct. And could also recreate its durable window after the efc-dialog has closed in the hook ecb-close-dialog-after-hook. You see really necessary are only hooks a) and D) but B) and C) could also be senseful (maybe)... Thoughts? IMHO it would not be a big deal for JDEE/efc but would offer big advantages for tools like ECB to work better with JDEE under all circumstances. In general such hooks would be good on every place JDEE creates and deletes windows. Please give me feedback! Ciao, klaus -Original Message- From: Le Wang [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 5:03 PM To: [EMAIL PROTECTED] Subject: ECB + JDE window focus bug. Hi, When I use 'jde-import-find-and-import' in ECB with a compile window, the prompt window that asks for clarification pops up in the compilation buffer. This is fine. But then, it doesn't have an idea where to put the import statement. Is there a setting in JDE/ECB that I can tweak to correct this? Recreate Problem: 1. emacs -q 2. setup loadpaths 3. load jde, ecb 3. find asdf.java 4. customize ecb-layout to use a compilation window. 5. ecb-activate. 6. With adsf.java in edit window, and focus in same window, do `jde-import-find-and-import' 7. Import ParseException class, choose any of the choices, click ok 8. Now the import statement is in my scratch buffer. Thanks. -- Le __ Post your free ad now! http://personals.yahoo.ca
