jEdit

Good question. I believe that some plugins save their state and
re-open as previous, while other plugins do not. However, the
"Activator" plugin might be a logical plugin to extend to this end,=20
perhaps with a "plugin profile" where you define which plugins exist
in a list of plugins, and how they should be started (docked, or
floating). Then activator already has the routines for loading and
activating the plugins.



On 3/1/06, Brian Hawkins <brianhks@...> wrote:
> Is there any plugin or setting that will remember the plugins you have
> open?  I have several plugins that I open and keep floating, but every
> time I close jedit and restart it the plugins are closed and I have to
> reopen them.  Is there a way of telling jedit to remember the open
> plugins and reopen them when I start jedit?
>
> If not I guess I'll have to write a plugin to open my plugins :)
>
> Brian
>
>
>

Very nice - I just added it to my version. I shall commit it soon.

On 2/28/06, Dale Anson <danson@...> wrote:
> I run across this fairly often in html and jsp pages that have javascript
> in them, a line like this to end a block of javascript:
>
> //--></script>
>
> All syntax highlighting after this line is wrong because the mode parser
> missed the </script> tag since it is after the // comment tag.  One fix i=
s
> to do this:
>
> //-->
> </script>
>
> But a lot of the time, I'm browsing read-only code (code I haven't checke=
d
> out from source control), so that isn't an easy option.  Another option i=
s
> do edit the javascript.xml mode file, and add this line:
>
> <SEQ_REGEXP HASH_CHAR=3D"/" TYPE=3D"COMMENT2">//--&gt;</SEQ_REGEXP>
>
> just before this line:
>
> <EOL_SPAN TYPE=3D"COMMENT2">//</EOL_SPAN>
>
> Then syntax highlighting in the rest of the file looks good without
> actually having to edit the file.
>
> Dale
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> --
> -----------------------------------------------
> jEdit Users' List
> jEdit-users@...
> https://lists.sourceforge.net/lists/listinfo/jedit-users
>

Dale Anson wrote:
> I run across this fairly often in html and jsp pages that have 
> javascript in them, a line like this to end a block of javascript:
> 
> //--></script>
> 
> All syntax highlighting after this line is wrong because the mode parser 
> missed the </script> tag since it is after the // comment tag.  One fix 
> is to do this:
> 
> //-->
> </script>
> 
> But a lot of the time, I'm browsing read-only code (code I haven't 
> checked out from source control), so that isn't an easy option.  Another 
> option is do edit the javascript.xml mode file, and add this line:
> 
> <SEQ_REGEXP HASH_CHAR="/" TYPE="COMMENT2">//--&gt;</SEQ_REGEXP>
> 
> just before this line:
> 
> <EOL_SPAN TYPE="COMMENT2">//</EOL_SPAN>
> 
> Then syntax highlighting in the rest of the file looks good without 
> actually having to edit the file.

jEdit really needs something smarter than this, though, like a "mode 
close tag overrides line comment" flag.  In PHP, ?> closes PHP mode even 
if it's on the same line as // (the ?> contains an implied ";\n" before it).

-Chris

Hi Omar, thanks for your input!

On 2/24/06, Onur Turgay <onurturgay@...> wrote:
> Good news everyone!
>
> I have browsed the sourcecode of jEdit and figured out how to enable
> LCD Antialiasing in java 6 (mustang)
>
> Now step by step:
>
> 1- in java 6 there is a new AWT class called SplashScreen. this class
> conflicts with jEdit splash screen. Before compiling with java6 jdk
> you have to change these lines in order to sovle nameconflict:
>
> org/gjt/sp/jedit/GUIUtilities.java:

I will just get rid of all the import package.* imports
and replace them with more specific ones.



>
> line #1494:
> find:     splash =3D new SplashScreen();
> replace:  splash =3D new org.gjt.sp.jedit.gui.SplashScreen();
>
> line #1507:
> find:     private static SplashScreen splash;
> replace:  private static org.gjt.sp.jedit.gui.SplashScreen splash;
>
> (If someone has a better method please tell, this is my first java hackin=
g)
>
> 2- we have to explicitly tell jEdit to use LCD antialiasing. somehow
> using DEFAULT mode I couldnt tell the JeditTextArea to use LCD
> antialising. (this change will make Smooth Fonts option useless.)
>
> org/gjt/sp/jedit/textarea/TextAreaPainter.java:
>
> line #844-854: Comment out the following lines
>
> if(antiAlias)
>                {
>                        //hints.put(RenderingHints.KEY_RENDERING,
> RenderingHints.VALUE_RENDER_QUALITY);
>                        hints.put(RenderingHints.KEY_ANTIALIASING,
> RenderingHints.VALUE_ANTIALIAS_ON);
>                        hints.put(RenderingHints.KEY_TEXT_ANTIALIASING,
> RenderingHints.VALUE_TEXT_ANTIALIAS_ON);
>                }
>                else
>                {
>                        hints.put(RenderingHints.KEY_ANTIALIASING,
> RenderingHints.VALUE_ANTIALIAS_OFF);

I think we would need to have ANOTHER antialias mode for 1.6 so that
we do not break the 1.5 version - I'm using that one and it looks
great on linux, in both 1.5 and 1.6.

Are you saying that when you use antialiasing options on in 1.6 with
windows, that the RenderingHints.VALUE_ANTIALIAS_ON is ignored? If so,
that sounds more like a bug in the JDK to me.

If we put in a reference to a JDK 1.6 constant, jedit will only build
on 1.6, so putting this into the core is probably not going to happen.

I will ponder on how to make this an option in jedit - perhaps by
running a beanshell script or something.

no Alan its not ignored, but VALUE_ANTIALIAS_ON implies the classic
antialiasing method in Java. LCD mode must be explicitly specified
unless the operating system settings include ClearType (or any other
LCD antialiasing scheme). all Swing components in Jedit inherits LCD
antialiasing scheme from windows, except for JEditTextArea and Gutter.
I thought this was because of explicit setting og
VALUE_TEXT_ANTIALIAS_ON and OFF and replaced these with _DEFAULT but
that didnt work also (this can be due to a bug in 1.6 because font2d
didnt show antialiasing in DEFAULT also). So I had to specify LCD_HRGB
explicitly to make it work.

I think you can put a setting in options panel which shows a dropdown
box which allows choosing between normal and lcd antialiasing (if
jre=3D=3D1.6). If I have time I can create a patch for it but I am not
used to java a lot and sometimes I get confused in all these classes
:)

Thanks for the great editor. If I can be of any help please let me know.

Onur Turgay.

On 2/25/06, Alan Ezust <alan.ezust@...> wrote:
> Hi Omar, thanks for your input!
>
> On 2/24/06, Onur Turgay <onurturgay@...> wrote:
> > Good news everyone!
> >
> > I have browsed the sourcecode of jEdit and figured out how to enable
> > LCD Antialiasing in java 6 (mustang)
> >
> > Now step by step:
> >
> > 1- in java 6 there is a new AWT class called SplashScreen. this class
> > conflicts with jEdit splash screen. Before compiling with java6 jdk
> > you have to change these lines in order to sovle nameconflict:
> >
> > org/gjt/sp/jedit/GUIUtilities.java:
>
> I will just get rid of all the import package.* imports
> and replace them with more specific ones.
>
>
>
> >
> > line #1494:
> > find:     splash =3D new SplashScreen();
> > replace:  splash =3D new org.gjt.sp.jedit.gui.SplashScreen();
> >
> > line #1507:
> > find:     private static SplashScreen splash;
> > replace:  private static org.gjt.sp.jedit.gui.SplashScreen splash;
> >
> > (If someone has a better method please tell, this is my first java hack=
ing)
> >
> > 2- we have to explicitly tell jEdit to use LCD antialiasing. somehow
> > using DEFAULT mode I couldnt tell the JeditTextArea to use LCD
> > antialising. (this change will make Smooth Fonts option useless.)
> >
> > org/gjt/sp/jedit/textarea/TextAreaPainter.java:
> >
> > line #844-854: Comment out the following lines
> >
> > if(antiAlias)
> >                {
> >                        //hints.put(RenderingHints.KEY_RENDERING,
> > RenderingHints.VALUE_RENDER_QUALITY);
> >                        hints.put(RenderingHints.KEY_ANTIALIASING,
> > RenderingHints.VALUE_ANTIALIAS_ON);
> >                        hints.put(RenderingHints.KEY_TEXT_ANTIALIASING,
> > RenderingHints.VALUE_TEXT_ANTIALIAS_ON);
> >                }
> >                else
> >                {
> >                        hints.put(RenderingHints.KEY_ANTIALIASING,
> > RenderingHints.VALUE_ANTIALIAS_OFF);
>
> I think we would need to have ANOTHER antialias mode for 1.6 so that
> we do not break the 1.5 version - I'm using that one and it looks
> great on linux, in both 1.5 and 1.6.
>
> Are you saying that when you use antialiasing options on in 1.6 with
> windows, that the RenderingHints.VALUE_ANTIALIAS_ON is ignored? If so,
> that sounds more like a bug in the JDK to me.
>
> If we put in a reference to a JDK 1.6 constant, jedit will only build
> on 1.6, so putting this into the core is probably not going to happen.
>
> I will ponder on how to make this an option in jedit - perhaps by
> running a beanshell script or something.
>

> I will just get rid of all the import package.* imports
> and replace them with more specific ones.

Sounds good.
> I think we would need to have ANOTHER antialias mode for 1.6 so that
> we do not break the 1.5 version - I'm using that one and it looks
> great on linux, in both 1.5 and 1.6.

Add a combo box to Global Options->Text Area, labelled "Anti-aliasing  
mode", with possible values "Off", "Standard", "Sub-pixel (LCD)".

> If we put in a reference to a JDK 1.6 constant, jedit will only build
> on 1.6, so putting this into the core is probably not going to happen.

Just use reflection.

Slava

Done. Committed.

My eyes can't tell any difference between these two antialias modes,
so please try it out and let me know if you can tell.


On 2/24/06, Slava Pestov <slava@...> wrote:
> > I will just get rid of all the import package.* imports
> > and replace them with more specific ones.
>
> Sounds good.
> > I think we would need to have ANOTHER antialias mode for 1.6 so that
> > we do not break the 1.5 version - I'm using that one and it looks
> > great on linux, in both 1.5 and 1.6.
>
> Add a combo box to Global Options->Text Area, labelled "Anti-aliasing
> mode", with possible values "Off", "Standard", "Sub-pixel (LCD)".
>
> > If we put in a reference to a JDK 1.6 constant, jedit will only build
> > on 1.6, so putting this into the core is probably not going to happen.
>
> Just use reflection.

I will try thanks.

the best way to tell difference is that. in normal antialiasing mode
only shades of grey (for black-white setting) is used. in sub pixel
antialiasing different colors (blue green red) also used. u can  use a
magnifing glass utility to check.

I am downloading jar now. I'll let you know.



On 2/25/06, Alan Ezust <alan.ezust@...> wrote:
> Done. Committed.
>
> My eyes can't tell any difference between these two antialias modes,
> so please try it out and let me know if you can tell.
>
>
> On 2/24/06, Slava Pestov <slava@...> wrote:
> > > I will just get rid of all the import package.* imports
> > > and replace them with more specific ones.
> >
> > Sounds good.
> > > I think we would need to have ANOTHER antialias mode for 1.6 so that
> > > we do not break the 1.5 version - I'm using that one and it looks
> > > great on linux, in both 1.5 and 1.6.
> >
> > Add a combo box to Global Options->Text Area, labelled "Anti-aliasing
> > mode", with possible values "Off", "Standard", "Sub-pixel (LCD)".
> >
> > > If we put in a reference to a JDK 1.6 constant, jedit will only build
> > > on 1.6, so putting this into the core is probably not going to happen=
.
> >
> > Just use reflection.
>

thanks. I am also trying to figure out how to get antialiasing for the
other textareas (such as the file system browser, the structure
browser, etc). Do I need to modify each plugin individually, or is
there a way of setting it globally?



On 2/24/06, Onur Turgay <onurturgay@...> wrote:
> I will try thanks.
>
> the best way to tell difference is that. in normal antialiasing mode
> only shades of grey (for black-white setting) is used. in sub pixel
> antialiasing different colors (blue green red) also used. u can  use a
> magnifing glass utility to check.
>
> I am downloading jar now. I'll let you know.
>
>
>
> On 2/25/06, Alan Ezust <alan.ezust@...> wrote:
> > Done. Committed.
> >
> > My eyes can't tell any difference between these two antialias modes,
> > so please try it out and let me know if you can tell.
> >
> >
> > On 2/24/06, Slava Pestov <slava@...> wrote:
> > > > I will just get rid of all the import package.* imports
> > > > and replace them with more specific ones.
> > >
> > > Sounds good.
> > > > I think we would need to have ANOTHER antialias mode for 1.6 so tha=
t
> > > > we do not break the 1.5 version - I'm using that one and it looks
> > > > great on linux, in both 1.5 and 1.6.
> > >
> > > Add a combo box to Global Options->Text Area, labelled "Anti-aliasing
> > > mode", with possible values "Off", "Standard", "Sub-pixel (LCD)".
> > >
> > > > If we put in a reference to a JDK 1.6 constant, jedit will only bui=
ld
> > > > on 1.6, so putting this into the core is probably not going to happ=
en.
> > >
> > > Just use reflection.
> >
>

they inherit from operating system if cleartype (on windows) is enabled.

desktop properties -> appearance -> effects -> method to smooth fonts:
clear type

when I enable this setting all other swing components inherit LCD
antialiasing. just textarea wasn't. it was ebcause of TEXTALIAS_ON and
OFF properties set explicitly. I dont know the way to set all of them
to LCD antialiasing. it maY BE something like setlookandfeeld.

if you didnt do, can you put an option to use system default? most
swing progams inherit cleartype automagically.

btw I couldnt download jedit.jar. can you mail it to me?

I love open source, I love jEdit. keep up the great work.

Onur Turgay.

On 2/25/06, Alan Ezust <alan.ezust@...> wrote:
> thanks. I am also trying to figure out how to get antialiasing for the
> other textareas (such as the file system browser, the structure
> browser, etc). Do I need to modify each plugin individually, or is
> there a way of setting it globally?
>
>
>
> On 2/24/06, Onur Turgay <onurturgay@...> wrote:
> > I will try thanks.
> >
> > the best way to tell difference is that. in normal antialiasing mode
> > only shades of grey (for black-white setting) is used. in sub pixel
> > antialiasing different colors (blue green red) also used. u can  use a
> > magnifing glass utility to check.
> >
> > I am downloading jar now. I'll let you know.
> >
> >
> >
> > On 2/25/06, Alan Ezust <alan.ezust@...> wrote:
> > > Done. Committed.
> > >
> > > My eyes can't tell any difference between these two antialias modes,
> > > so please try it out and let me know if you can tell.
> > >
> > >
> > > On 2/24/06, Slava Pestov <slava@...> wrote:
> > > > > I will just get rid of all the import package.* imports
> > > > > and replace them with more specific ones.
> > > >
> > > > Sounds good.
> > > > > I think we would need to have ANOTHER antialias mode for 1.6 so t=
hat
> > > > > we do not break the 1.5 version - I'm using that one and it looks
> > > > > great on linux, in both 1.5 and 1.6.
> > > >
> > > > Add a combo box to Global Options->Text Area, labelled "Anti-aliasi=
ng
> > > > mode", with possible values "Off", "Standard", "Sub-pixel (LCD)".
> > > >
> > > > > If we put in a reference to a JDK 1.6 constant, jedit will only b=
uild
> > > > > on 1.6, so putting this into the core is probably not going to ha=
ppen.
> > > >
> > > > Just use reflection.
> > >
> >
>

On 2/25/06, Onur Turgay <onurturgay@...> wrote:
> they inherit from operating system if cleartype (on windows) is enabled.

True, in Windows it all looks great.

Actually, what I'm wondering about is for the other Text containing
widgets under Linux.

With linux, I see antialiased fonts on the buttons BUT NOT the menus.
For the tree views of all plugins, I see ugly non-antialiased fonts
too.

PS: I can't e-mail you a file that big. try this:
http://lazarus.oddiofile.com:81/workspace/jEdit/jedit.jar

hi alan,

It didn't work for me. it makes standart antialiasing. the trick is
when you want to make LCD antialiasing you musn't set
KEY_ANTIALIASING =3D VALUE_ANTIALIAS_ON alongside with
KEY_TEXT_ANTIALIASING =3D VALUE_TEXT_ANTIALIAS_LCD_HRGB ... just setting
KEY_TEXT_ANTIALIASING =3D VALUE_TEXT_ANTIALIAS_LCD_HRGB is enough. if
you set VALUE_ANTIALIAS_ON (warning: not TEXT_ANTIALIAS_ON) it
overrides lcd antialiasing with classic antialising. this may be a bug
or something I didnt look into javadoc.

On 2/25/06, Alan Ezust <alan.ezust@...> wrote:
> On 2/25/06, Onur Turgay <onurturgay@...> wrote:
> > they inherit from operating system if cleartype (on windows) is enabled=
.
>
> True, in Windows it all looks great.
>
> Actually, what I'm wondering about is for the other Text containing
> widgets under Linux.
>
> With linux, I see antialiased fonts on the buttons BUT NOT the menus.
> For the tree views of all plugins, I see ugly non-antialiased fonts
> too.
>
> PS: I can't e-mail you a file that big. try this:
> http://lazarus.oddiofile.com:81/workspace/jEdit/jedit.jar
>

I replaced JavaSideKick.jar in %HOMEPATH%\.jedit\jars with the download 
from the link you gave.

And now when I select the same menu item, I don't get the error dialog.  
Nothing seems to happen at all.  In the console window, I see:

[warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable

The same thing appears in the activity log.  Below are some of the lines 
leading up to it:

[debug] WorkThread: Work request thread starting [SideKick #1]
[debug] WorkThread: Running in work thread: [id=52,run=sidekick.SideKick$ParseRequest@...]
[debug] SideKick$ParseAWTRequest: ParseAWTRequest
[debug] SideKickParsedData: Setting parsed data of org.gjt.sp.jedit.View[active] to sidekick.java.JavaSideKickParsedData@...
[debug] EditBus: SideKickUpdate[source=null]
[warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable

Andy

Dale Anson wrote:

> I've posted an update on the community site that fixes this problem.
>
> http://community.jedit.org/?q=filestore/download/2576
>
> Dale
>
>
> On Fri, 24 Feb 2006, Michael Chisholm wrote:
>
>> I wanted to give JavaSideKick a try, but it doesn't seem to work.  I 
>> have jEdit 4.3pre3, XP SP2, jdk1.5.0_06.
>>
>> When I go to Plugins|JavaSideKick|"Go to structure browser", I get 
>> the following stacktrace in a "Beanshell Error" dialog:
>>
>> Error in method invocation: Static method gotoDockable( 
>> org.gjt.sp.jedit.View ) not found in 
>> class'sidekick.java.JavaSideKickPlugin' : at Line: 4 : in file: 
>> inline evaluation of: 
>> ``__internal_action_javasidekick_gotodockable(ns) { 
>> this.callstack.set(0,ns);               . . . '' : sidekick .java 
>> .JavaSideKickPlugin .gotoDockable ( view )
>>      at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:76)
>>      at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
>>      at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
>>      at bsh.BSHBlock.evalBlock(BSHBlock.java:130)
>>      at bsh.BSHBlock.eval(BSHBlock.java:80)
>>      at bsh.BshMethod.invokeImpl(BshMethod.java:349)
>>      at bsh.BshMethod.invoke(BshMethod.java:246)
>>      at bsh.BshMethod.invoke(BshMethod.java:171)
>>      at org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:507)
>>      at org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:76)
>>      at
>>      
>> org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:229)
>>      at org.gjt.sp.jedit.jEdit$3.invokeAction(jEdit.java:2902)
>>      at
>>      
>> org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:216)
>>      at
>>      
>> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
>>      at
>>      
>> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) 
>>
>>      at
>>      
>> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) 
>>
>>      at
>>      
>> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
>>      at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
>>      at
>>      
>> javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000) 
>>
>>      at
>>      
>> javax.swing.plaf.basic.BasicMenuItemUI$Handler.menuDragMouseReleased(BasicMenuItemUI.java:1104) 
>>
>>      at
>>      javax.swing.JMenuItem.fireMenuDragMouseReleased(JMenuItem.java:578)
>>      at
>>      javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:475)
>>      at javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:422)
>>      at
>>      
>> javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:283) 
>>
>>      at
>>      
>> javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:757) 
>>
>>      at
>>      
>> java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2206) 
>>
>>      at
>>      
>> java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2100) 
>>
>>      at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2058)
>>      at java.awt.Component.dispatchEventImpl(Component.java:3867)
>>      at java.awt.Container.dispatchEventImpl(Container.java:2024)
>>      at java.awt.Component.dispatchEvent(Component.java:3803)
>>      at
>>      
>> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
>>      at
>>      
>> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
>>      at 
>> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
>>      at java.awt.Container.dispatchEventImpl(Container.java:2010)
>>      at java.awt.Window.dispatchEventImpl(Window.java:1774)
>>      at java.awt.Component.dispatchEvent(Component.java:3803)
>>      at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
>>      at
>>      
>> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) 
>>
>>      at
>>      
>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) 
>>
>>      at
>>      
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>>      at
>>      
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>>      at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>>
>> Looks like the beanshell is trying to invoke a non-existant method in 
>> the JavaSideKick plugin...
>>
>> Andy
>>
>> Jeffrey Hoyt wrote:
>>
>>> Hello, all. I have a few new toys for you.  4 newly packaged plugins
>>> and a host of ones that were silently released over the last month or
>>> so.  Enjoy!
>>>
>>> Jeff
>>>
>>> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>>> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ New plugin releases:
>>>
>>> Two initial releases:
>>>
>>> TypoScript VFS 0.1.0 - The TypoScript plugin provides a VFS (Virtual
>>> FileSystem) module for loading and editing the "setup" and"constants"
>>> templates within the TYPO3 CMS. It requiresthe "jeditvfs" extension to
>>> be installed in TYPO3.
>>>
>>> Recent 0.1 - The recent plugin stores all edit actions in a table ina
>>> dockable window. It recordes actions which are invoked by plugin,
>>> macroor built-in actions. The user invokes an action by clicking it in
>>> a dockablewindow. Additionally, it provides a buffer history
>>>
>>> Two updates:
>>>
>>> JakartaCommon 0.4.4 - added xmlrpc-2.0.1.jar and its dependency,
>>> commons-codec-1.3.jar
>>>
>>> ShortcutDisplay 1.1 - Due to popular request (OK, Alan asked), now
>>> remembers window location.
>>>
>>> These may take a day or two to get through the mirrors.  If you have
>>> trouble downloading them through the Plugin Manager, either change
>>> your mirror, or download them directly from http://plugins.jedit.org
>>> or http://sourceforge.net/projects/jedit-plugins
>>>
>>> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>>> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ The following were 
>>> previously released, but not announced:
>>>
>>> Two new releases:
>>>
>>> P4Plugin 0.2.0 - P4Plugin provides an interface for the use of the
>>> Perforce Unix command-line utility "p4" from inside jEdit, using the
>>> ProjectViewer tree as the GUI for managing the files in the Perforce
>>> repository. Most common perforce commands like "edit", "revert",
>>> "change" and others are available as jEdit actions, allowing shortcuts
>>> to be assigned.
>>>
>>> JavaSideKick 2.0 - Initial release for this plugin. This is basically
>>> the parser for JBrowse 1.5 adapted to SideKick (hence the 2.0 version
>>> number). Error handling is greatly improved over JBrowse 1.5, so the
>>> tree will display regardless of the number of errors found during
>>> parsing.
>>>
>>>
>>> 7 updates:
>>>
>>> Templates 3.3.1 - Updated for jEdit 4.3pre3 refactoring
>>>
>>> Lazy Importer 1.0.8 - Updated for jEdit 4.3pre3 refactoring
>>>
>>> CodeBrowser 1.4.2 0 - Updated for jEdit 4.3pre3 refactoring
>>>
>>> CommonControls 0.9.0 - added kappalayout.jar
>>>
>>> LookAndFeel 1.1 - Added support for NimROD Look And Feel.
>>>
>>> ProjectViewer 2.1.2.0 - Bug fix release; lots of fixes to plugin
>>> extension support.
>>>
>>> TextFilter 0.1.2 - Uses the I/O threads provided by CommonControls for
>>> reduced resource usage.
>>>
>>> These have been released for a while and should offer no problems
>>> through the Plugin Manager.
>>>
>>> -- 
>>> They that give up essential liberty to obtain a little temporary
>>> safety deserve neither.
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>>> language
>>> that extends applications into web and mobile media. Attend the live 
>>> webcast
>>> and join the prime developer group breaking into this new coding 
>>> territory!
>>> http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
>>>
>>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>> language
>> that extends applications into web and mobile media. Attend the live 
>> webcast
>> and join the prime developer group breaking into this new coding 
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> -- 
>> -----------------------------------------------
>> jEdit Users' List
>> jEdit-users@...
>> https://lists.sourceforge.net/lists/listinfo/jedit-users
>>
>

Okay, I've whacked all my plugins and installed just the basic few that I 
actually use.  I can reproduce your problem.  The work-around (and the 
way it will work next release) is to not use the JavaSideKick menu, but 
use the SideKick menu.

I've uploaded the fix to the community site at:

http://community.jedit.org/?q=node/view/2576

This also includes some updates to code completion and I've bumped up the 
version number.

I want to do some more work on the code completion before I submit this 
plugin to plugin central, so I'd appreciate any feedback about the code 
completion.  I did see the comment about "System." not showing any 
completions, that is now working in the version I just posted.

Thanks,

Dale


On Fri, 24 Feb 2006, Michael Chisholm wrote:

> I replaced JavaSideKick.jar in %HOMEPATH%\.jedit\jars with the download from 
> the link you gave.
>
> And now when I select the same menu item, I don't get the error dialog. 
> Nothing seems to happen at all.  In the console window, I see:
>
> [warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable
>
> The same thing appears in the activity log.  Below are some of the lines 
> leading up to it:
>
> [debug] WorkThread: Work request thread starting [SideKick #1]
> [debug] WorkThread: Running in work thread: 
> [id=52,run=sidekick.SideKick$ParseRequest@...]
> [debug] SideKick$ParseAWTRequest: ParseAWTRequest
> [debug] SideKickParsedData: Setting parsed data of 
> org.gjt.sp.jedit.View[active] to sidekick.java.JavaSideKickParsedData@...
> [debug] EditBus: SideKickUpdate[source=null]
> [warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable
>
> Andy
>
> Dale Anson wrote:
>
>>  I've posted an update on the community site that fixes this problem.
>>
>>  http://community.jedit.org/?q=filestore/download/2576
>>
>>  Dale
>> 
>>
>>  On Fri, 24 Feb 2006, Michael Chisholm wrote:
>> 
>> >  I wanted to give JavaSideKick a try, but it doesn't seem to work.  I 
>> >  have jEdit 4.3pre3, XP SP2, jdk1.5.0_06.
>> > 
>> >  When I go to Plugins|JavaSideKick|"Go to structure browser", I get the 
>> >  following stacktrace in a "Beanshell Error" dialog:
>> > 
>> >  Error in method invocation: Static method gotoDockable( 
>> >  org.gjt.sp.jedit.View ) not found in 
>> >  class'sidekick.java.JavaSideKickPlugin' : at Line: 4 : in file: inline 
>> >  evaluation of: ``__internal_action_javasidekick_gotodockable(ns) { 
>> >  this.callstack.set(0,ns);               . . . '' : sidekick .java 
>> >  .JavaSideKickPlugin .gotoDockable ( view )
>> >       at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:76)
>> >       at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
>> >       at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
>> >       at bsh.BSHBlock.evalBlock(BSHBlock.java:130)
>> >       at bsh.BSHBlock.eval(BSHBlock.java:80)
>> >       at bsh.BshMethod.invokeImpl(BshMethod.java:349)
>> >       at bsh.BshMethod.invoke(BshMethod.java:246)
>> >       at bsh.BshMethod.invoke(BshMethod.java:171)
>> >       at org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:507)
>> >       at org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:76)
>> >       at
>> > 
>> >  org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:229)
>> >       at org.gjt.sp.jedit.jEdit$3.invokeAction(jEdit.java:2902)
>> >       at
>> > 
>> >  org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:216)
>> >       at
>> > 
>> >  javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
>> >       at
>> > 
>> >  javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) 
>> > 
>> >       at
>> > 
>> >  javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) 
>> > 
>> >       at
>> > 
>> >  javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
>> >       at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
>> >       at
>> > 
>> >  javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000) 
>> > 
>> >       at
>> > 
>> >  javax.swing.plaf.basic.BasicMenuItemUI$Handler.menuDragMouseReleased(BasicMenuItemUI.java:1104) 
>> > 
>> >       at
>> >       javax.swing.JMenuItem.fireMenuDragMouseReleased(JMenuItem.java:578)
>> >       at
>> >       javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:475)
>> >       at javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:422)
>> >       at
>> > 
>> >  javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:283) 
>> > 
>> >       at
>> > 
>> >  javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:757) 
>> > 
>> >       at
>> > 
>> >  java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2206) 
>> > 
>> >       at
>> > 
>> >  java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2100) 
>> > 
>> >       at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2058)
>> >       at java.awt.Component.dispatchEventImpl(Component.java:3867)
>> >       at java.awt.Container.dispatchEventImpl(Container.java:2024)
>> >       at java.awt.Component.dispatchEvent(Component.java:3803)
>> >       at
>> > 
>> >  java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
>> >       at
>> > 
>> >  java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
>> >       at 
>> >  java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
>> >       at java.awt.Container.dispatchEventImpl(Container.java:2010)
>> >       at java.awt.Window.dispatchEventImpl(Window.java:1774)
>> >       at java.awt.Component.dispatchEvent(Component.java:3803)
>> >       at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
>> >       at
>> > 
>> >  java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) 
>> > 
>> >       at
>> > 
>> >  java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) 
>> > 
>> >       at
>> > 
>> >  java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>> >       at
>> > 
>> >  java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>> >       at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>> > 
>> >  Looks like the beanshell is trying to invoke a non-existant method in 
>> >  the JavaSideKick plugin...
>> > 
>> >  Andy
>> > 
>> >  Jeffrey Hoyt wrote:
>> > 
>> > >  Hello, all. I have a few new toys for you.  4 newly packaged plugins
>> > >  and a host of ones that were silently released over the last month or
>> > >  so.  Enjoy!
>> > > 
>> > >  Jeff
>> > > 
>> > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>> > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~  New plugin releases:
>> > > 
>> > >  Two initial releases:
>> > > 
>> > >  TypoScript VFS 0.1.0 - The TypoScript plugin provides a VFS (Virtual
>> > >  FileSystem) module for loading and editing the "setup" and"constants"
>> > >  templates within the TYPO3 CMS. It requiresthe "jeditvfs" extension to
>> > >  be installed in TYPO3.
>> > > 
>> > >  Recent 0.1 - The recent plugin stores all edit actions in a table ina
>> > >  dockable window. It recordes actions which are invoked by plugin,
>> > >  macroor built-in actions. The user invokes an action by clicking it in
>> > >  a dockablewindow. Additionally, it provides a buffer history
>> > > 
>> > >  Two updates:
>> > > 
>> > >  JakartaCommon 0.4.4 - added xmlrpc-2.0.1.jar and its dependency,
>> > >  commons-codec-1.3.jar
>> > > 
>> > >  ShortcutDisplay 1.1 - Due to popular request (OK, Alan asked), now
>> > >  remembers window location.
>> > > 
>> > >  These may take a day or two to get through the mirrors.  If you have
>> > >  trouble downloading them through the Plugin Manager, either change
>> > >  your mirror, or download them directly from http://plugins.jedit.org
>> > >  or http://sourceforge.net/projects/jedit-plugins
>> > > 
>> > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>> > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~  The following were 
>> > >  previously released, but not announced:
>> > > 
>> > >  Two new releases:
>> > > 
>> > >  P4Plugin 0.2.0 - P4Plugin provides an interface for the use of the
>> > >  Perforce Unix command-line utility "p4" from inside jEdit, using the
>> > >  ProjectViewer tree as the GUI for managing the files in the Perforce
>> > >  repository. Most common perforce commands like "edit", "revert",
>> > >  "change" and others are available as jEdit actions, allowing shortcuts
>> > >  to be assigned.
>> > > 
>> > >  JavaSideKick 2.0 - Initial release for this plugin. This is basically
>> > >  the parser for JBrowse 1.5 adapted to SideKick (hence the 2.0 version
>> > >  number). Error handling is greatly improved over JBrowse 1.5, so the
>> > >  tree will display regardless of the number of errors found during
>> > >  parsing.
>> > > 
>> > > 
>> > >  7 updates:
>> > > 
>> > >  Templates 3.3.1 - Updated for jEdit 4.3pre3 refactoring
>> > > 
>> > >  Lazy Importer 1.0.8 - Updated for jEdit 4.3pre3 refactoring
>> > > 
>> > >  CodeBrowser 1.4.2 0 - Updated for jEdit 4.3pre3 refactoring
>> > > 
>> > >  CommonControls 0.9.0 - added kappalayout.jar
>> > > 
>> > >  LookAndFeel 1.1 - Added support for NimROD Look And Feel.
>> > > 
>> > >  ProjectViewer 2.1.2.0 - Bug fix release; lots of fixes to plugin
>> > >  extension support.
>> > > 
>> > >  TextFilter 0.1.2 - Uses the I/O threads provided by CommonControls for
>> > >  reduced resource usage.
>> > > 
>> > >  These have been released for a while and should offer no problems
>> > >  through the Plugin Manager.
>> > > 
>> > >  -- 
>> > >  They that give up essential liberty to obtain a little temporary
>> > >  safety deserve neither.
>> > > 
>> > > 
>> > >  -------------------------------------------------------
>> > >  This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>> > >  language
>> > >  that extends applications into web and mobile media. Attend the live 
>> > >  webcast
>> > >  and join the prime developer group breaking into this new coding 
>> > >  territory!
>> > >  http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
>> > > 
>> > > 
>> > 
>> > 
>> > 
>> > 
>> >  -------------------------------------------------------
>> >  This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>> >  language
>> >  that extends applications into web and mobile media. Attend the live 
>> >  webcast
>> >  and join the prime developer group breaking into this new coding 
>> >  territory!
>> >  http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> >  -- 
>> >  -----------------------------------------------
>> >  jEdit Users' List
>> >  jEdit-users@...
>> >  https://lists.sourceforge.net/lists/listinfo/jedit-users
>> > 
>> 
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> -- 
> -----------------------------------------------
> jEdit Users' List
> jEdit-users@...
> https://lists.sourceforge.net/lists/listinfo/jedit-users
>

Well, that problem has disappeared... :)

Now, the JavaSideKick menu item doesn't seem to show up in the Plugins 
menu at all.  Just in case it was really there but forgot to insert 
itself into the menus, I checked the Docking section of Global Options, 
and there was something named "JBrowse2" listed there.  I assume that's 
another name for JavaSideKick?  I set it to dock at the right, and a 
button for it showed up.  I clicked the button, and got the stack trace 
below.

Btw, I tried to see if any code-completion would happen, and typing 
"System." did cause a popup to appear with what appeared to be valid 
methods from the System class, but clicking anywhere inside the popup 
(whether on a list item, scrollbar, etc) just made it disappear, with no 
effect.  There didn't appear to be any stacktraces or errors as a result 
of this either.

[error] AWT-EventQueue-0: Exception in thread "AWT-EventQueue-0"
[error] AWT-EventQueue-0: java.lang.ClassCastException: sidekick.java.JavaParser
[error] AWT-EventQueue-0:  at org.gjt.sp.jedit.gui.DockableWindowFactory$Window.createDockableWindow(DockableWindowFactory.java:458)
[error] AWT-EventQueue-0:  at org.gjt.sp.jedit.gui.DockableWindowManager.showDockableWindow(DockableWindowManager.java:261)
[error] AWT-EventQueue-0:  at org.gjt.sp.jedit.gui.PanelWindowContainer$ActionHandler.actionPerformed(PanelWindowContainer.java:420)
[error] AWT-EventQueue-0:  at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
[error] AWT-EventQueue-0:  at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
[error] AWT-EventQueue-0:  at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
[error] AWT-EventQueue-0:  at javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:269)
[error] AWT-EventQueue-0:  at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
[error] AWT-EventQueue-0:  at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
[error] AWT-EventQueue-0:  at java.awt.Component.processMouseEvent(Component.java:5488)
[error] AWT-EventQueue-0:  at javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
[error] AWT-EventQueue-0:  at java.awt.Component.processEvent(Component.java:5253)
[error] AWT-EventQueue-0:  at java.awt.Container.processEvent(Container.java:1966)
[error] AWT-EventQueue-0:  at java.awt.Component.dispatchEventImpl(Component.java:3955)
[error] AWT-EventQueue-0:  at java.awt.Container.dispatchEventImpl(Container.java:2024)
[error] AWT-EventQueue-0:  at java.awt.Component.dispatchEvent(Component.java:3803)
[error] AWT-EventQueue-0:  at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
[error] AWT-EventQueue-0:  at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
[error] AWT-EventQueue-0:  at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
[error] AWT-EventQueue-0:  at java.awt.Container.dispatchEventImpl(Container.java:2010)
[error] AWT-EventQueue-0:  at java.awt.Window.dispatchEventImpl(Window.java:1774)
[error] AWT-EventQueue-0:  at java.awt.Component.dispatchEvent(Component.java:3803)
[error] AWT-EventQueue-0:  at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
[error] AWT-EventQueue-0:  at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
[error] AWT-EventQueue-0:  at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
[error] AWT-EventQueue-0:  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
[error] AWT-EventQueue-0:  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
[error] AWT-EventQueue-0:  at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

Andy

Dale Anson wrote:

> Okay, I've whacked all my plugins and installed just the basic few 
> that I actually use.  I can reproduce your problem.  The work-around 
> (and the way it will work next release) is to not use the JavaSideKick 
> menu, but use the SideKick menu.
>
> I've uploaded the fix to the community site at:
>
> http://community.jedit.org/?q=node/view/2576
>
> This also includes some updates to code completion and I've bumped up 
> the version number.
>
> I want to do some more work on the code completion before I submit 
> this plugin to plugin central, so I'd appreciate any feedback about 
> the code completion.  I did see the comment about "System." not 
> showing any completions, that is now working in the version I just 
> posted.
>
> Thanks,
>
> Dale
>
>
> On Fri, 24 Feb 2006, Michael Chisholm wrote:
>
>> I replaced JavaSideKick.jar in %HOMEPATH%\.jedit\jars with the 
>> download from the link you gave.
>>
>> And now when I select the same menu item, I don't get the error 
>> dialog. Nothing seems to happen at all.  In the console window, I see:
>>
>> [warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable
>>
>> The same thing appears in the activity log.  Below are some of the 
>> lines leading up to it:
>>
>> [debug] WorkThread: Work request thread starting [SideKick #1]
>> [debug] WorkThread: Running in work thread: 
>> [id=52,run=sidekick.SideKick$ParseRequest@...]
>> [debug] SideKick$ParseAWTRequest: ParseAWTRequest
>> [debug] SideKickParsedData: Setting parsed data of 
>> org.gjt.sp.jedit.View[active] to 
>> sidekick.java.JavaSideKickParsedData@...
>> [debug] EditBus: SideKickUpdate[source=null]
>> [warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable
>>
>> Andy
>>
>> Dale Anson wrote:
>>
>>>  I've posted an update on the community site that fixes this problem.
>>>
>>>  http://community.jedit.org/?q=filestore/download/2576
>>>
>>>  Dale
>>>
>>>
>>>  On Fri, 24 Feb 2006, Michael Chisholm wrote:
>>>
>>> >  I wanted to give JavaSideKick a try, but it doesn't seem to 
>>> work.  I >  have jEdit 4.3pre3, XP SP2, jdk1.5.0_06.
>>> > >  When I go to Plugins|JavaSideKick|"Go to structure browser", I 
>>> get the >  following stacktrace in a "Beanshell Error" dialog:
>>> > >  Error in method invocation: Static method gotoDockable( >  
>>> org.gjt.sp.jedit.View ) not found in >  
>>> class'sidekick.java.JavaSideKickPlugin' : at Line: 4 : in file: 
>>> inline >  evaluation of: 
>>> ``__internal_action_javasidekick_gotodockable(ns) { >  
>>> this.callstack.set(0,ns);               . . . '' : sidekick .java >  
>>> .JavaSideKickPlugin .gotoDockable ( view )
>>> >       at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:76)
>>> >       at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
>>> >       at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
>>> >       at bsh.BSHBlock.evalBlock(BSHBlock.java:130)
>>> >       at bsh.BSHBlock.eval(BSHBlock.java:80)
>>> >       at bsh.BshMethod.invokeImpl(BshMethod.java:349)
>>> >       at bsh.BshMethod.invoke(BshMethod.java:246)
>>> >       at bsh.BshMethod.invoke(BshMethod.java:171)
>>> >       at 
>>> org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:507)
>>> >       at 
>>> org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:76)
>>> >       at
>>> > >  
>>> org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:229)
>>> >       at org.gjt.sp.jedit.jEdit$3.invokeAction(jEdit.java:2902)
>>> >       at
>>> > >  
>>> org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:216) 
>>>
>>> >       at
>>> > >  
>>> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849) 
>>>
>>> >       at
>>> > >  
>>> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) 
>>> > >       at
>>> > >  
>>> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) 
>>> > >       at
>>> > >  
>>> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
>>> >       at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
>>> >       at
>>> > >  
>>> javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000) 
>>> > >       at
>>> > >  
>>> javax.swing.plaf.basic.BasicMenuItemUI$Handler.menuDragMouseReleased(BasicMenuItemUI.java:1104) 
>>> > >       at
>>> >       
>>> javax.swing.JMenuItem.fireMenuDragMouseReleased(JMenuItem.java:578)
>>> >       at
>>> >       
>>> javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:475)
>>> >       at javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:422)
>>> >       at
>>> > >  
>>> javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:283) 
>>> > >       at
>>> > >  
>>> javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:757) 
>>> > >       at
>>> > >  
>>> java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2206) 
>>> > >       at
>>> > >  
>>> java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2100) 
>>> > >       at 
>>> java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2058)
>>> >       at java.awt.Component.dispatchEventImpl(Component.java:3867)
>>> >       at java.awt.Container.dispatchEventImpl(Container.java:2024)
>>> >       at java.awt.Component.dispatchEvent(Component.java:3803)
>>> >       at
>>> > >  
>>> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
>>> >       at
>>> > >  
>>> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
>>> >       at >  
>>> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
>>> >       at java.awt.Container.dispatchEventImpl(Container.java:2010)
>>> >       at java.awt.Window.dispatchEventImpl(Window.java:1774)
>>> >       at java.awt.Component.dispatchEvent(Component.java:3803)
>>> >       at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
>>> >       at
>>> > >  
>>> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) 
>>> > >       at
>>> > >  
>>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) 
>>> > >       at
>>> > >  
>>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>>> >       at
>>> > >  
>>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>>> >       at 
>>> java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>>> > >  Looks like the beanshell is trying to invoke a non-existant 
>>> method in >  the JavaSideKick plugin...
>>> > >  Andy
>>> > >  Jeffrey Hoyt wrote:
>>> > > >  Hello, all. I have a few new toys for you.  4 newly packaged 
>>> plugins
>>> > >  and a host of ones that were silently released over the last 
>>> month or
>>> > >  so.  Enjoy!
>>> > > > >  Jeff
>>> > > > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>>> ~ ~ ~ ~ > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~  New plugin 
>>> releases:
>>> > > > >  Two initial releases:
>>> > > > >  TypoScript VFS 0.1.0 - The TypoScript plugin provides a VFS 
>>> (Virtual
>>> > >  FileSystem) module for loading and editing the "setup" 
>>> and"constants"
>>> > >  templates within the TYPO3 CMS. It requiresthe "jeditvfs" 
>>> extension to
>>> > >  be installed in TYPO3.
>>> > > > >  Recent 0.1 - The recent plugin stores all edit actions in a 
>>> table ina
>>> > >  dockable window. It recordes actions which are invoked by plugin,
>>> > >  macroor built-in actions. The user invokes an action by 
>>> clicking it in
>>> > >  a dockablewindow. Additionally, it provides a buffer history
>>> > > > >  Two updates:
>>> > > > >  JakartaCommon 0.4.4 - added xmlrpc-2.0.1.jar and its 
>>> dependency,
>>> > >  commons-codec-1.3.jar
>>> > > > >  ShortcutDisplay 1.1 - Due to popular request (OK, Alan 
>>> asked), now
>>> > >  remembers window location.
>>> > > > >  These may take a day or two to get through the mirrors.  If 
>>> you have
>>> > >  trouble downloading them through the Plugin Manager, either change
>>> > >  your mirror, or download them directly from 
>>> http://plugins.jedit.org
>>> > >  or http://sourceforge.net/projects/jedit-plugins
>>> > > > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>>> ~ ~ ~ ~ > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~  The following 
>>> were > >  previously released, but not announced:
>>> > > > >  Two new releases:
>>> > > > >  P4Plugin 0.2.0 - P4Plugin provides an interface for the use 
>>> of the
>>> > >  Perforce Unix command-line utility "p4" from inside jEdit, 
>>> using the
>>> > >  ProjectViewer tree as the GUI for managing the files in the 
>>> Perforce
>>> > >  repository. Most common perforce commands like "edit", "revert",
>>> > >  "change" and others are available as jEdit actions, allowing 
>>> shortcuts
>>> > >  to be assigned.
>>> > > > >  JavaSideKick 2.0 - Initial release for this plugin. This is 
>>> basically
>>> > >  the parser for JBrowse 1.5 adapted to SideKick (hence the 2.0 
>>> version
>>> > >  number). Error handling is greatly improved over JBrowse 1.5, 
>>> so the
>>> > >  tree will display regardless of the number of errors found during
>>> > >  parsing.
>>> > > > > > >  7 updates:
>>> > > > >  Templates 3.3.1 - Updated for jEdit 4.3pre3 refactoring
>>> > > > >  Lazy Importer 1.0.8 - Updated for jEdit 4.3pre3 refactoring
>>> > > > >  CodeBrowser 1.4.2 0 - Updated for jEdit 4.3pre3 refactoring
>>> > > > >  CommonControls 0.9.0 - added kappalayout.jar
>>> > > > >  LookAndFeel 1.1 - Added support for NimROD Look And Feel.
>>> > > > >  ProjectViewer 2.1.2.0 - Bug fix release; lots of fixes to 
>>> plugin
>>> > >  extension support.
>>> > > > >  TextFilter 0.1.2 - Uses the I/O threads provided by 
>>> CommonControls for
>>> > >  reduced resource usage.
>>> > > > >  These have been released for a while and should offer no 
>>> problems
>>> > >  through the Plugin Manager.
>>> > > > >  -- > >  They that give up essential liberty to obtain a 
>>> little temporary
>>> > >  safety deserve neither.
>>> > > > > > >  -------------------------------------------------------
>>> > >  This SF.Net email is sponsored by xPML, a groundbreaking 
>>> scripting > >  language
>>> > >  that extends applications into web and mobile media. Attend the 
>>> live > >  webcast
>>> > >  and join the prime developer group breaking into this new 
>>> coding > >  territory!
>>> > >  http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
>>> > > > > > > > > >  
>>> -------------------------------------------------------
>>> >  This SF.Net email is sponsored by xPML, a groundbreaking 
>>> scripting >  language
>>> >  that extends applications into web and mobile media. Attend the 
>>> live >  webcast
>>> >  and join the prime developer group breaking into this new coding 
>>> >  territory!
>>> >  
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 
>>>
>>> >  -- >  -----------------------------------------------
>>> >  jEdit Users' List
>>> >  jEdit-users@...
>>> >  https://lists.sourceforge.net/lists/listinfo/jedit-users
>>> >
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>> language
>> that extends applications into web and mobile media. Attend the live 
>> webcast
>> and join the prime developer group breaking into this new coding 
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> -- 
>> -----------------------------------------------
>> jEdit Users' List
>> jEdit-users@...
>> https://lists.sourceforge.net/lists/listinfo/jedit-users
>>
>

Let's start at the beginning...

1. you downloaded the new file I posted.
2. you copied that file to your .jedit/jars diretory
3. you restarted jEdit

You should not see a JavaSideKick menu item.
You should see a SideKick menu item.

So far so good?

Now do this:
Open a java source file.
Click Plugins -> SideKick -> Structure Browser
You should see the tree in SideKick representing the java source file.

JavaSideKick grew out of JBrowse, so the JBrowse2 name your seeing is in 
fact JavaSideKick.  I'll change that so it is less confusing, thanks for 
pointing that out.  In fact I found a couple of other references to 
JBrowse to change.  I'll remove the dockable settings also, JavaSideKick 
itself doesn't dock, SideKick does.  So if you want to dock it, dock 
SideKick, it is named "Structure Browser" in the docking settings.

And like I mentioned earlier, I'm still working on the code completion.  I 
thought I had the "System." thing working though... :(

I'll try to get another update posted today.

Thanks,

Dale


On Fri, 24 Feb 2006, Michael Chisholm wrote:

> Well, that problem has disappeared... :)
>
> Now, the JavaSideKick menu item doesn't seem to show up in the Plugins menu 
> at all.  Just in case it was really there but forgot to insert itself into 
> the menus, I checked the Docking section of Global Options, and there was 
> something named "JBrowse2" listed there.  I assume that's another name for 
> JavaSideKick?  I set it to dock at the right, and a button for it showed up. 
> I clicked the button, and got the stack trace below.
>
> Btw, I tried to see if any code-completion would happen, and typing "System." 
> did cause a popup to appear with what appeared to be valid methods from the 
> System class, but clicking anywhere inside the popup (whether on a list item, 
> scrollbar, etc) just made it disappear, with no effect.  There didn't appear 
> to be any stacktraces or errors as a result of this either.
>
> [error] AWT-EventQueue-0: Exception in thread "AWT-EventQueue-0"
> [error] AWT-EventQueue-0: java.lang.ClassCastException: 
> sidekick.java.JavaParser
> [error] AWT-EventQueue-0:  at 
> org.gjt.sp.jedit.gui.DockableWindowFactory$Window.createDockableWindow(DockableWindowFactory.java:458)
> [error] AWT-EventQueue-0:  at 
> org.gjt.sp.jedit.gui.DockableWindowManager.showDockableWindow(DockableWindowManager.java:261)
> [error] AWT-EventQueue-0:  at 
> org.gjt.sp.jedit.gui.PanelWindowContainer$ActionHandler.actionPerformed(PanelWindowContainer.java:420)
> [error] AWT-EventQueue-0:  at 
> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
> [error] AWT-EventQueue-0:  at 
> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
> [error] AWT-EventQueue-0:  at 
> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
> [error] AWT-EventQueue-0:  at 
> javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:269)
> [error] AWT-EventQueue-0:  at 
> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
> [error] AWT-EventQueue-0:  at 
> java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
> [error] AWT-EventQueue-0:  at 
> java.awt.Component.processMouseEvent(Component.java:5488)
> [error] AWT-EventQueue-0:  at 
> javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
> [error] AWT-EventQueue-0:  at 
> java.awt.Component.processEvent(Component.java:5253)
> [error] AWT-EventQueue-0:  at 
> java.awt.Container.processEvent(Container.java:1966)
> [error] AWT-EventQueue-0:  at 
> java.awt.Component.dispatchEventImpl(Component.java:3955)
> [error] AWT-EventQueue-0:  at 
> java.awt.Container.dispatchEventImpl(Container.java:2024)
> [error] AWT-EventQueue-0:  at 
> java.awt.Component.dispatchEvent(Component.java:3803)
> [error] AWT-EventQueue-0:  at 
> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
> [error] AWT-EventQueue-0:  at 
> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
> [error] AWT-EventQueue-0:  at 
> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
> [error] AWT-EventQueue-0:  at 
> java.awt.Container.dispatchEventImpl(Container.java:2010)
> [error] AWT-EventQueue-0:  at 
> java.awt.Window.dispatchEventImpl(Window.java:1774)
> [error] AWT-EventQueue-0:  at 
> java.awt.Component.dispatchEvent(Component.java:3803)
> [error] AWT-EventQueue-0:  at 
> java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
> [error] AWT-EventQueue-0:  at 
> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
> [error] AWT-EventQueue-0:  at 
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
> [error] AWT-EventQueue-0:  at 
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
> [error] AWT-EventQueue-0:  at 
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
> [error] AWT-EventQueue-0:  at 
> java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>
> Andy
>
> Dale Anson wrote:
>
>>  Okay, I've whacked all my plugins and installed just the basic few that I
>>  actually use.  I can reproduce your problem.  The work-around (and the way
>>  it will work next release) is to not use the JavaSideKick menu, but use
>>  the SideKick menu.
>>
>>  I've uploaded the fix to the community site at:
>>
>>  http://community.jedit.org/?q=node/view/2576
>>
>>  This also includes some updates to code completion and I've bumped up the
>>  version number.
>>
>>  I want to do some more work on the code completion before I submit this
>>  plugin to plugin central, so I'd appreciate any feedback about the code
>>  completion.  I did see the comment about "System." not showing any
>>  completions, that is now working in the version I just posted.
>>
>>  Thanks,
>>
>>  Dale
>> 
>>
>>  On Fri, 24 Feb 2006, Michael Chisholm wrote:
>> 
>> >  I replaced JavaSideKick.jar in %HOMEPATH%\.jedit\jars with the download 
>> >  from the link you gave.
>> > 
>> >  And now when I select the same menu item, I don't get the error dialog. 
>> >  Nothing seems to happen at all.  In the console window, I see:
>> > 
>> >  [warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable
>> > 
>> >  The same thing appears in the activity log.  Below are some of the lines 
>> >  leading up to it:
>> > 
>> >  [debug] WorkThread: Work request thread starting [SideKick #1]
>> >  [debug] WorkThread: Running in work thread: 
>> >  [id=52,run=sidekick.SideKick$ParseRequest@...]
>> >  [debug] SideKick$ParseAWTRequest: ParseAWTRequest
>> >  [debug] SideKickParsedData: Setting parsed data of 
>> >  org.gjt.sp.jedit.View[active] to 
>> >  sidekick.java.JavaSideKickParsedData@...
>> >  [debug] EditBus: SideKickUpdate[source=null]
>> >  [warning] EditAction$Wrapper: Unknown action: javasidekick-gotodockable
>> > 
>> >  Andy
>> > 
>> >  Dale Anson wrote:
>> > 
>> > >   I've posted an update on the community site that fixes this problem.
>> > > 
>> > >   http://community.jedit.org/?q=filestore/download/2576
>> > > 
>> > >   Dale
>> > > 
>> > > 
>> > >   On Fri, 24 Feb 2006, Michael Chisholm wrote:
>> > > 
>> > > >   I wanted to give JavaSideKick a try, but it doesn't seem to 
>> > >  work.  I >  have jEdit 4.3pre3, XP SP2, jdk1.5.0_06.
>> > > > >   When I go to Plugins|JavaSideKick|"Go to structure browser", I 
>> > >  get the >  following stacktrace in a "Beanshell Error" dialog:
>> > > > >   Error in method invocation: Static method gotoDockable( > 
>> > >  org.gjt.sp.jedit.View ) not found in > 
>> > >  class'sidekick.java.JavaSideKickPlugin' : at Line: 4 : in file: inline 
>> > >  >  evaluation of: ``__internal_action_javasidekick_gotodockable(ns) { 
>> > >  >  this.callstack.set(0,ns);               . . . '' : sidekick .java > 
>> > >  .JavaSideKickPlugin .gotoDockable ( view )
>> > > >        at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:76)
>> > > >        at 
>> > > >        bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
>> > > >        at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
>> > > >        at bsh.BSHBlock.evalBlock(BSHBlock.java:130)
>> > > >        at bsh.BSHBlock.eval(BSHBlock.java:80)
>> > > >        at bsh.BshMethod.invokeImpl(BshMethod.java:349)
>> > > >        at bsh.BshMethod.invoke(BshMethod.java:246)
>> > > >        at bsh.BshMethod.invoke(BshMethod.java:171)
>> > > >        at 
>> > >  org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:507)
>> > > >        at 
>> > >  org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:76)
>> > > >        at
>> > > > > 
>> > >  org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:229)
>> > > >        at org.gjt.sp.jedit.jEdit$3.invokeAction(jEdit.java:2902)
>> > > >        at
>> > > > > 
>> > >  org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:216) 
>> > > 
>> > > >        at
>> > > > > 
>> > >  javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849) 
>> > > 
>> > > >        at
>> > > > > 
>> > >  javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) 
>> > > > >        at
>> > > > > 
>> > >  javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) 
>> > > > >        at
>> > > > > 
>> > >  javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
>> > > >        at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
>> > > >        at
>> > > > > 
>> > >  javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000) 
>> > > > >        at
>> > > > > 
>> > >  javax.swing.plaf.basic.BasicMenuItemUI$Handler.menuDragMouseReleased(BasicMenuItemUI.java:1104) 
>> > > > >        at
>> > > > 
>> > >  javax.swing.JMenuItem.fireMenuDragMouseReleased(JMenuItem.java:578)
>> > > >        at
>> > > > 
>> > >  javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:475)
>> > > >        at javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:422)
>> > > >        at
>> > > > > 
>> > >  javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:283) 
>> > > > >        at
>> > > > > 
>> > >  javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:757) 
>> > > > >        at
>> > > > > 
>> > >  java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2206) 
>> > > > >        at
>> > > > > 
>> > >  java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2100) 
>> > > > >        at 
>> > >  java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2058)
>> > > >        at java.awt.Component.dispatchEventImpl(Component.java:3867)
>> > > >        at java.awt.Container.dispatchEventImpl(Container.java:2024)
>> > > >        at java.awt.Component.dispatchEvent(Component.java:3803)
>> > > >        at
>> > > > > 
>> > >  java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
>> > > >        at
>> > > > > 
>> > >  java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
>> > > > at > 
>> > >  java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
>> > > >        at java.awt.Container.dispatchEventImpl(Container.java:2010)
>> > > >        at java.awt.Window.dispatchEventImpl(Window.java:1774)
>> > > >        at java.awt.Component.dispatchEvent(Component.java:3803)
>> > > >        at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
>> > > >        at
>> > > > > 
>> > >  java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) 
>> > > > >        at
>> > > > > 
>> > >  java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) 
>> > > > >        at
>> > > > > 
>> > >  java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>> > > >        at
>> > > > > 
>> > >  java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>> > > >        at 
>> > >  java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>> > > > >   Looks like the beanshell is trying to invoke a non-existant 
>> > >  method in >  the JavaSideKick plugin...
>> > > > >   Andy
>> > > > >   Jeffrey Hoyt wrote:
>> > > > > >   Hello, all. I have a few new toys for you.  4 newly packaged 
>> > >  plugins
>> > > > >   and a host of ones that were silently released over the last 
>> > >  month or
>> > > > >   so.  Enjoy!
>> > > > > > >   Jeff
>> > > > > > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>> > > ~ ~ ~ ~ > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~   New plugin 
>> > >  releases:
>> > > > > > >   Two initial releases:
>> > > > > > >   TypoScript VFS 0.1.0 - The TypoScript plugin provides a VFS 
>> > >  (Virtual
>> > > > >   FileSystem) module for loading and editing the "setup" 
>> > >  and"constants"
>> > > > >   templates within the TYPO3 CMS. It requiresthe "jeditvfs" 
>> > >  extension to
>> > > > >   be installed in TYPO3.
>> > > > > > >   Recent 0.1 - The recent plugin stores all edit actions in a 
>> > >  table ina
>> > > > >   dockable window. It recordes actions which are invoked by plugin,
>> > > > >   macroor built-in actions. The user invokes an action by 
>> > >  clicking it in
>> > > > >   a dockablewindow. Additionally, it provides a buffer history
>> > > > > > >   Two updates:
>> > > > > > >   JakartaCommon 0.4.4 - added xmlrpc-2.0.1.jar and its 
>> > >  dependency,
>> > > > >   commons-codec-1.3.jar
>> > > > > > >   ShortcutDisplay 1.1 - Due to popular request (OK, Alan 
>> > >  asked), now
>> > > > >   remembers window location.
>> > > > > > >   These may take a day or two to get through the mirrors.  If 
>> > >  you have
>> > > > >   trouble downloading them through the Plugin Manager, either 
>> > > > >   change
>> > > > >   your mirror, or download them directly from 
>> > >  http://plugins.jedit.org
>> > > > >   or http://sourceforge.net/projects/jedit-plugins
>> > > > > > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>> > > ~ ~ ~ ~ > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~   The following 
>> > > were > >   previously released, but not announced:
>> > > > > > >   Two new releases:
>> > > > > > >   P4Plugin 0.2.0 - P4Plugin provides an interface for the use 
>> > >  of the
>> > > > >   Perforce Unix command-line utility "p4" from inside jEdit, 
>> > >  using the
>> > > > >   ProjectViewer tree as the GUI for managing the files in the 
>> > >  Perforce
>> > > > >   repository. Most common perforce commands like "edit", "revert",
>> > > > >   "change" and others are available as jEdit actions, allowing 
>> > >  shortcuts
>> > > > >   to be assigned.
>> > > > > > >   JavaSideKick 2.0 - Initial release for this plugin. This is 
>> > >  basically
>> > > > >   the parser for JBrowse 1.5 adapted to SideKick (hence the 2.0 
>> > >  version
>> > > > >   number). Error handling is greatly improved over JBrowse 1.5, 
>> > >  so the
>> > > > >   tree will display regardless of the number of errors found during
>> > > > >   parsing.
>> > > > > > > > >   7 updates:
>> > > > > > >   Templates 3.3.1 - Updated for jEdit 4.3pre3 refactoring
>> > > > > > >   Lazy Importer 1.0.8 - Updated for jEdit 4.3pre3 refactoring
>> > > > > > >   CodeBrowser 1.4.2 0 - Updated for jEdit 4.3pre3 refactoring
>> > > > > > >   CommonControls 0.9.0 - added kappalayout.jar
>> > > > > > >   LookAndFeel 1.1 - Added support for NimROD Look And Feel.
>> > > > > > >   ProjectViewer 2.1.2.0 - Bug fix release; lots of fixes to 
>> > >  plugin
>> > > > >   extension support.
>> > > > > > >   TextFilter 0.1.2 - Uses the I/O threads provided by 
>> > >  CommonControls for
>> > > > >   reduced resource usage.
>> > > > > > >   These have been released for a while and should offer no 
>> > >  problems
>> > > > >   through the Plugin Manager.
>> > > > > > >   -- > >  They that give up essential liberty to obtain a 
>> > >  little temporary
>> > > > >   safety deserve neither.
>> > > > > > > > >   -------------------------------------------------------
>> > > > >   This SF.Net email is sponsored by xPML, a groundbreaking 
>> > > scripting > >   language
>> > > > >   that extends applications into web and mobile media. Attend the 
>> > > live > >   webcast
>> > > > >   and join the prime developer group breaking into this new 
>> > > coding > >   territory!
>> > > > >   http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
>> > > > > > > > > > > > 
>> > >  -------------------------------------------------------
>> > > >   This SF.Net email is sponsored by xPML, a groundbreaking 
>> > > scripting >   language
>> > > >   that extends applications into web and mobile media. Attend the 
>> > > live >   webcast
>> > > >   and join the prime developer group breaking into this new coding 
>> > > >   territory!
>> > > > 
>> > >  http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 
>> > > 
>> > > >   -- >  -----------------------------------------------
>> > > >   jEdit Users' List
>> > > >   jEdit-users@...
>> > > >   https://lists.sourceforge.net/lists/listinfo/jedit-users
>> > > > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> >  -------------------------------------------------------
>> >  This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>> >  language
>> >  that extends applications into web and mobile media. Attend the live 
>> >  webcast
>> >  and join the prime developer group breaking into this new coding 
>> >  territory!
>> >  http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> >  -- 
>> >  -----------------------------------------------
>> >  jEdit Users' List
>> >  jEdit-users@...
>> >  https://lists.sourceforge.net/lists/listinfo/jedit-users
>> > 
>> 
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> -- 
> -----------------------------------------------
> jEdit Users' List
> jEdit-users@...
> https://lists.sourceforge.net/lists/listinfo/jedit-users
>
>

Oh ok... the UI change caught me by surprise.  Yes, I now have the 
structure browser showing, like you said.  Now it's looking like JBrowse 
again! :)

Thanks,
Andy

Dale Anson wrote:

> Let's start at the beginning...
>
> 1. you downloaded the new file I posted.
> 2. you copied that file to your .jedit/jars diretory
> 3. you restarted jEdit
>
> You should not see a JavaSideKick menu item.
> You should see a SideKick menu item.
>
> So far so good?
>
> Now do this:
> Open a java source file.
> Click Plugins -> SideKick -> Structure Browser
> You should see the tree in SideKick representing the java source file.
>
> JavaSideKick grew out of JBrowse, so the JBrowse2 name your seeing is 
> in fact JavaSideKick.  I'll change that so it is less confusing, 
> thanks for pointing that out.  In fact I found a couple of other 
> references to JBrowse to change.  I'll remove the dockable settings 
> also, JavaSideKick itself doesn't dock, SideKick does.  So if you want 
> to dock it, dock SideKick, it is named "Structure Browser" in the 
> docking settings.
>
> And like I mentioned earlier, I'm still working on the code 
> completion.  I thought I had the "System." thing working though... :(
>
> I'll try to get another update posted today.
>
> Thanks,
>
> Dale
>
>
> On Fri, 24 Feb 2006, Michael Chisholm wrote:
>
>> Well, that problem has disappeared... :)
>>
>> Now, the JavaSideKick menu item doesn't seem to show up in the 
>> Plugins menu at all.  Just in case it was really there but forgot to 
>> insert itself into the menus, I checked the Docking section of Global 
>> Options, and there was something named "JBrowse2" listed there.  I 
>> assume that's another name for JavaSideKick?  I set it to dock at the 
>> right, and a button for it showed up. I clicked the button, and got 
>> the stack trace below.
>>
>> Btw, I tried to see if any code-completion would happen, and typing 
>> "System." did cause a popup to appear with what appeared to be valid 
>> methods from the System class, but clicking anywhere inside the popup 
>> (whether on a list item, scrollbar, etc) just made it disappear, with 
>> no effect.  There didn't appear to be any stacktraces or errors as a 
>> result of this either.
>>
>> [error] AWT-EventQueue-0: Exception in thread "AWT-EventQueue-0"
>> [error] AWT-EventQueue-0: java.lang.ClassCastException: 
>> sidekick.java.JavaParser
>> [error] AWT-EventQueue-0:  at 
>> org.gjt.sp.jedit.gui.DockableWindowFactory$Window.createDockableWindow(DockableWindowFactory.java:458) 
>>
>> [error] AWT-EventQueue-0:  at 
>> org.gjt.sp.jedit.gui.DockableWindowManager.showDockableWindow(DockableWindowManager.java:261) 
>>
>> [error] AWT-EventQueue-0:  at 
>> org.gjt.sp.jedit.gui.PanelWindowContainer$ActionHandler.actionPerformed(PanelWindowContainer.java:420) 
>>
>> [error] AWT-EventQueue-0:  at 
>> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
>> [error] AWT-EventQueue-0:  at 
>> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) 
>>
>> [error] AWT-EventQueue-0:  at 
>> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) 
>>
>> [error] AWT-EventQueue-0:  at 
>> javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:269) 
>>
>> [error] AWT-EventQueue-0:  at 
>> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234) 
>>
>> [error] AWT-EventQueue-0:  at 
>> java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Component.processMouseEvent(Component.java:5488)
>> [error] AWT-EventQueue-0:  at 
>> javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Component.processEvent(Component.java:5253)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Container.processEvent(Container.java:1966)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Component.dispatchEventImpl(Component.java:3955)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Container.dispatchEventImpl(Container.java:2024)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Component.dispatchEvent(Component.java:3803)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Container.dispatchEventImpl(Container.java:2010)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Window.dispatchEventImpl(Window.java:1774)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.Component.dispatchEvent(Component.java:3803)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) 
>>
>> [error] AWT-EventQueue-0:  at 
>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) 
>>
>> [error] AWT-EventQueue-0:  at 
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>> [error] AWT-EventQueue-0:  at 
>> java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>>
>> Andy
>>
>> Dale Anson wrote:
>>
>>>  Okay, I've whacked all my plugins and installed just the basic few 
>>> that I
>>>  actually use.  I can reproduce your problem.  The work-around (and 
>>> the way
>>>  it will work next release) is to not use the JavaSideKick menu, but 
>>> use
>>>  the SideKick menu.
>>>
>>>  I've uploaded the fix to the community site at:
>>>
>>>  http://community.jedit.org/?q=node/view/2576
>>>
>>>  This also includes some updates to code completion and I've bumped 
>>> up the
>>>  version number.
>>>
>>>  I want to do some more work on the code completion before I submit 
>>> this
>>>  plugin to plugin central, so I'd appreciate any feedback about the 
>>> code
>>>  completion.  I did see the comment about "System." not showing any
>>>  completions, that is now working in the version I just posted.
>>>
>>>  Thanks,
>>>
>>>  Dale
>>>
>>>
>>>  On Fri, 24 Feb 2006, Michael Chisholm wrote:
>>>
>>> >  I replaced JavaSideKick.jar in %HOMEPATH%\.jedit\jars with the 
>>> download >  from the link you gave.
>>> > >  And now when I select the same menu item, I don't get the error 
>>> dialog. >  Nothing seems to happen at all.  In the console window, I 
>>> see:
>>> > >  [warning] EditAction$Wrapper: Unknown action: 
>>> javasidekick-gotodockable
>>> > >  The same thing appears in the activity log.  Below are some of 
>>> the lines >  leading up to it:
>>> > >  [debug] WorkThread: Work request thread starting [SideKick #1]
>>> >  [debug] WorkThread: Running in work thread: >  
>>> [id=52,run=sidekick.SideKick$ParseRequest@...]
>>> >  [debug] SideKick$ParseAWTRequest: ParseAWTRequest
>>> >  [debug] SideKickParsedData: Setting parsed data of >  
>>> org.gjt.sp.jedit.View[active] to >  
>>> sidekick.java.JavaSideKickParsedData@...
>>> >  [debug] EditBus: SideKickUpdate[source=null]
>>> >  [warning] EditAction$Wrapper: Unknown action: 
>>> javasidekick-gotodockable
>>> > >  Andy
>>> > >  Dale Anson wrote:
>>> > > >   I've posted an update on the community site that fixes this 
>>> problem.
>>> > > > >   http://community.jedit.org/?q=filestore/download/2576
>>> > > > >   Dale
>>> > > > > > >   On Fri, 24 Feb 2006, Michael Chisholm wrote:
>>> > > > > >   I wanted to give JavaSideKick a try, but it doesn't seem 
>>> to > >  work.  I >  have jEdit 4.3pre3, XP SP2, jdk1.5.0_06.
>>> > > > >   When I go to Plugins|JavaSideKick|"Go to structure 
>>> browser", I > >  get the >  following stacktrace in a "Beanshell 
>>> Error" dialog:
>>> > > > >   Error in method invocation: Static method gotoDockable( > 
>>> > >  org.gjt.sp.jedit.View ) not found in > > >  
>>> class'sidekick.java.JavaSideKickPlugin' : at Line: 4 : in file: 
>>> inline > >  >  evaluation of: 
>>> ``__internal_action_javasidekick_gotodockable(ns) { > >  >  
>>> this.callstack.set(0,ns);               . . . '' : sidekick .java > 
>>> > >  .JavaSideKickPlugin .gotoDockable ( view )
>>> > > >        at 
>>> bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:76)
>>> > > >        at > > >        
>>> bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
>>> > > >        at 
>>> bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
>>> > > >        at bsh.BSHBlock.evalBlock(BSHBlock.java:130)
>>> > > >        at bsh.BSHBlock.eval(BSHBlock.java:80)
>>> > > >        at bsh.BshMethod.invokeImpl(BshMethod.java:349)
>>> > > >        at bsh.BshMethod.invoke(BshMethod.java:246)
>>> > > >        at bsh.BshMethod.invoke(BshMethod.java:171)
>>> > > >        at > >  
>>> org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:507)
>>> > > >        at > >  
>>> org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:76)
>>> > > >        at
>>> > > > > > >  
>>> org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:229)
>>> > > >        at org.gjt.sp.jedit.jEdit$3.invokeAction(jEdit.java:2902)
>>> > > >        at
>>> > > > > > >  
>>> org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:216) 
>>> > > > > >        at
>>> > > > > > >  
>>> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849) 
>>> > > > > >        at
>>> > > > > > >  
>>> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169) 
>>> > > > >        at
>>> > > > > > >  
>>> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) 
>>> > > > >        at
>>> > > > > > >  
>>> javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
>>> > > >        at 
>>> javax.swing.AbstractButton.doClick(AbstractButton.java:302)
>>> > > >        at
>>> > > > > > >  
>>> javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000) 
>>> > > > >        at
>>> > > > > > >  
>>> javax.swing.plaf.basic.BasicMenuItemUI$Handler.menuDragMouseReleased(BasicMenuItemUI.java:1104) 
>>> > > > >        at
>>> > > > > >  
>>> javax.swing.JMenuItem.fireMenuDragMouseReleased(JMenuItem.java:578)
>>> > > >        at
>>> > > > > >  
>>> javax.swing.JMenuItem.processMenuDragMouseEvent(JMenuItem.java:475)
>>> > > >        at 
>>> javax.swing.JMenuItem.processMouseEvent(JMenuItem.java:422)
>>> > > >        at
>>> > > > > > >  
>>> javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:283) 
>>> > > > >        at
>>> > > > > > >  
>>> javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:757) 
>>> > > > >        at
>>> > > > > > >  
>>> java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2206) 
>>> > > > >        at
>>> > > > > > >  
>>> java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2100) 
>>> > > > >        at > >  
>>> java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2058)
>>> > > >        at 
>>> java.awt.Component.dispatchEventImpl(Component.java:3867)
>>> > > >        at 
>>> java.awt.Container.dispatchEventImpl(Container.java:2024)
>>> > > >        at java.awt.Component.dispatchEvent(Component.java:3803)
>>> > > >        at
>>> > > > > > >  
>>> java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
>>> > > >        at
>>> > > > > > >  
>>> java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
>>> > > > at > > >  
>>> java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
>>> > > >        at 
>>> java.awt.Container.dispatchEventImpl(Container.java:2010)
>>> > > >        at java.awt.Window.dispatchEventImpl(Window.java:1774)
>>> > > >        at java.awt.Component.dispatchEvent(Component.java:3803)
>>> > > >        at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
>>> > > >        at
>>> > > > > > >  
>>> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) 
>>> > > > >        at
>>> > > > > > >  
>>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) 
>>> > > > >        at
>>> > > > > > >  
>>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>>> > > >        at
>>> > > > > > >  
>>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>>> > > >        at > >  
>>> java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>>> > > > >   Looks like the beanshell is trying to invoke a 
>>> non-existant > >  method in >  the JavaSideKick plugin...
>>> > > > >   Andy
>>> > > > >   Jeffrey Hoyt wrote:
>>> > > > > >   Hello, all. I have a few new toys for you.  4 newly 
>>> packaged > >  plugins
>>> > > > >   and a host of ones that were silently released over the 
>>> last > >  month or
>>> > > > >   so.  Enjoy!
>>> > > > > > >   Jeff
>>> > > > > > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>>> ~ ~ > > ~ ~ ~ ~ > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~   New 
>>> plugin > >  releases:
>>> > > > > > >   Two initial releases:
>>> > > > > > >   TypoScript VFS 0.1.0 - The TypoScript plugin provides 
>>> a VFS > >  (Virtual
>>> > > > >   FileSystem) module for loading and editing the "setup" > 
>>> >  and"constants"
>>> > > > >   templates within the TYPO3 CMS. It requiresthe "jeditvfs" 
>>> > >  extension to
>>> > > > >   be installed in TYPO3.
>>> > > > > > >   Recent 0.1 - The recent plugin stores all edit actions 
>>> in a > >  table ina
>>> > > > >   dockable window. It recordes actions which are invoked by 
>>> plugin,
>>> > > > >   macroor built-in actions. The user invokes an action by > 
>>> >  clicking it in
>>> > > > >   a dockablewindow. Additionally, it provides a buffer history
>>> > > > > > >   Two updates:
>>> > > > > > >   JakartaCommon 0.4.4 - added xmlrpc-2.0.1.jar and its > 
>>> >  dependency,
>>> > > > >   commons-codec-1.3.jar
>>> > > > > > >   ShortcutDisplay 1.1 - Due to popular request (OK, Alan 
>>> > >  asked), now
>>> > > > >   remembers window location.
>>> > > > > > >   These may take a day or two to get through the 
>>> mirrors.  If > >  you have
>>> > > > >   trouble downloading them through the Plugin Manager, 
>>> either > > > >   change
>>> > > > >   your mirror, or download them directly from > >  
>>> http://plugins.jedit.org
>>> > > > >   or http://sourceforge.net/projects/jedit-plugins
>>> > > > > > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 
>>> ~ ~ > > ~ ~ ~ ~ > > ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~   The 
>>> following > > were > >   previously released, but not announced:
>>> > > > > > >   Two new releases:
>>> > > > > > >   P4Plugin 0.2.0 - P4Plugin provides an interface for 
>>> the use > >  of the
>>> > > > >   Perforce Unix command-line utility "p4" from inside jEdit, 
>>> > >  using the
>>> > > > >   ProjectViewer tree as the GUI for managing the files in 
>>> the > >  Perforce
>>> > > > >   repository. Most common perforce commands like "edit", 
>>> "revert",
>>> > > > >   "change" and others are available as jEdit actions, 
>>> allowing > >  shortcuts
>>> > > > >   to be assigned.
>>> > > > > > >   JavaSideKick 2.0 - Initial release for this plugin. 
>>> This is > >  basically
>>> > > > >   the parser for JBrowse 1.5 adapted to SideKick (hence the 
>>> 2.0 > >  version
>>> > > > >   number). Error handling is greatly improved over JBrowse 
>>> 1.5, > >  so the
>>> > > > >   tree will display regardless of the number of errors found 
>>> during
>>> > > > >   parsing.
>>> > > > > > > > >   7 updates:
>>> > > > > > >   Templates 3.3.1 - Updated for jEdit 4.3pre3 refactoring
>>> > > > > > >   Lazy Importer 1.0.8 - Updated for jEdit 4.3pre3 
>>> refactoring
>>> > > > > > >   CodeBrowser 1.4.2 0 - Updated for jEdit 4.3pre3 
>>> refactoring
>>> > > > > > >   CommonControls 0.9.0 - added kappalayout.jar
>>> > > > > > >   LookAndFeel 1.1 - Added support for NimROD Look And Feel.
>>> > > > > > >   ProjectViewer 2.1.2.0 - Bug fix release; lots of fixes 
>>> to > >  plugin
>>> > > > >   extension support.
>>> > > > > > >   TextFilter 0.1.2 - Uses the I/O threads provided by > 
>>> >  CommonControls for
>>> > > > >   reduced resource usage.
>>> > > > > > >   These have been released for a while and should offer 
>>> no > >  problems
>>> > > > >   through the Plugin Manager.
>>> > > > > > >   -- > >  They that give up essential liberty to obtain 
>>> a > >  little temporary
>>> > > > >   safety deserve neither.
>>> > > > > > > > >   
>>> -------------------------------------------------------
>>> > > > >   This SF.Net email is sponsored by xPML, a groundbreaking > 
>>> > scripting > >   language
>>> > > > >   that extends applications into web and mobile media. 
>>> Attend the > > live > >   webcast
>>> > > > >   and join the prime developer group breaking into this new 
>>> > > coding > >   territory!
>>> > > > >   
>>> http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
>>> > > > > > > > > > > > > >  
>>> -------------------------------------------------------
>>> > > >   This SF.Net email is sponsored by xPML, a groundbreaking > > 
>>> scripting >   language
>>> > > >   that extends applications into web and mobile media. Attend 
>>> the > > live >   webcast
>>> > > >   and join the prime developer group breaking into this new 
>>> coding > > >   territory!
>>> > > > > >  
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 
>>> > > > > >   -- >  -----------------------------------------------
>>> > > >   jEdit Users' List
>>> > > >   jEdit-users@...
>>> > > >   https://lists.sourceforge.net/lists/listinfo/jedit-users
>>> > > > > > > > > >  
>>> -------------------------------------------------------
>>> >  This SF.Net email is sponsored by xPML, a groundbreaking 
>>> scripting >  language
>>> >  that extends applications into web and mobile media. Attend the 
>>> live >  webcast
>>> >  and join the prime developer group breaking into this new coding 
>>> >  territory!
>>> >  
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 
>>>
>>> >  -- >  -----------------------------------------------
>>> >  jEdit Users' List
>>> >  jEdit-users@...
>>> >  https://lists.sourceforge.net/lists/listinfo/jedit-users
>>> >
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>> language
>> that extends applications into web and mobile media. Attend the live 
>> webcast
>> and join the prime developer group breaking into this new coding 
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> -- 
>> -----------------------------------------------
>> jEdit Users' List
>> jEdit-users@...
>> https://lists.sourceforge.net/lists/listinfo/jedit-users
>>
>>
>

On 24-Feb-06, at 10:01 AM, Onur Turgay wrote:
> I have read somewhere that sun is incorporating lcd-antialias (like
> windows cleartype) into swing in java6 and this option will be on if
> your computer has cleartype: on by default. So I rushed to
> dev.java.org and downloaded java6 and voila! everything in jEdit is
> cleartype-esque antialiased.... except for textarea :( holycow. is
> there anyhow a way to textarea inherit antialiasing behaviour from
> other swing components (not overriding it). if it can be done in code
> level I can happily submit a bug report, but I dont know java a lot (I
> use ruby/php)

Check that "Smooth Text" is enabled under Utilities->Global 
Options->Text Area. I believe this enables anti-aliasing for the text 
area.

Steve Jakob