jedit-devel Mailing List for jEdit

Plugin Central Submission item #1440420, was opened at 2006-02-28 16:11
Message generated for change (Comment added) made by nigel_galloway
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nigel (nigel_galloway)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sceme4jEdit_1.0.0 initial release

Initial Comment:
Requirements:

jEdit 4.2pre8
OolongPlugin 1.0.0
Console 4.1.2

Announcement:
release 1.0.0

Source:

http://www.geocities.com/nigel_galloway/Scheme4jEdit_1.
0.0.zip

Short Description:
This plugin provides a Sceme interpreter integrated 
into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins
Long Description:

This plugin integrates the Sceme R4 implementation 
produced by J. Engel to demonstrate Oolong into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins


----------------------------------------------------------------------

>Comment By: Nigel (nigel_galloway)
Date: 2006-02-28 17:04

Message:
Logged In: YES 
user_id=1201057

Which still splits over two lines. SourceForge must get 
wider screens. Until they do please type ip on the end. 

----------------------------------------------------------------------

Comment By: Nigel (nigel_galloway)
Date: 2006-02-28 16:57

Message:
Logged In: YES 
user_id=1201057

The link is as above, I think the problem is that it is 
split over 2 lines. Try this:

http://www.geocities.com/nigel_galloway/Scheme4jEdit_1.0.0.z
ip

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2006-02-28 16:30

Message:
Logged In: YES 
user_id=935841

that link doesn't work.
Would you mind adding it to the jedit plugins CVS repo? Do
you have an account? If not, please post the link again.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Plugin Central Submission item #1440420, was opened at 2006-02-28 16:11
Message generated for change (Comment added) made by nigel_galloway
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nigel (nigel_galloway)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sceme4jEdit_1.0.0 initial release

Initial Comment:
Requirements:

jEdit 4.2pre8
OolongPlugin 1.0.0
Console 4.1.2

Announcement:
release 1.0.0

Source:

http://www.geocities.com/nigel_galloway/Scheme4jEdit_1.
0.0.zip

Short Description:
This plugin provides a Sceme interpreter integrated 
into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins
Long Description:

This plugin integrates the Sceme R4 implementation 
produced by J. Engel to demonstrate Oolong into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins


----------------------------------------------------------------------

>Comment By: Nigel (nigel_galloway)
Date: 2006-02-28 16:57

Message:
Logged In: YES 
user_id=1201057

The link is as above, I think the problem is that it is 
split over 2 lines. Try this:

http://www.geocities.com/nigel_galloway/Scheme4jEdit_1.0.0.z
ip

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2006-02-28 16:30

Message:
Logged In: YES 
user_id=935841

that link doesn't work.
Would you mind adding it to the jedit plugins CVS repo? Do
you have an account? If not, please post the link again.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Plugin Central Submission item #1440420, was opened at 2006-02-28 08:11
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nigel (nigel_galloway)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sceme4jEdit_1.0.0 initial release

Initial Comment:
Requirements:

jEdit 4.2pre8
OolongPlugin 1.0.0
Console 4.1.2

Announcement:
release 1.0.0

Source:

http://www.geocities.com/nigel_galloway/Scheme4jEdit_1.
0.0.zip

Short Description:
This plugin provides a Sceme interpreter integrated 
into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins
Long Description:

This plugin integrates the Sceme R4 implementation 
produced by J. Engel to demonstrate Oolong into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins


----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2006-02-28 08:30

Message:
Logged In: YES 
user_id=935841

that link doesn't work.
Would you mind adding it to the jedit plugins CVS repo? Do
you have an account? If not, please post the link again.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Plugin Central Submission item #1440420, was opened at 2006-02-28 16:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nigel (nigel_galloway)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sceme4jEdit_1.0.0 initial release

Initial Comment:
Requirements:

jEdit 4.2pre8
OolongPlugin 1.0.0
Console 4.1.2

Announcement:
release 1.0.0

Source:

http://www.geocities.com/nigel_galloway/Scheme4jEdit_1.
0.0.zip

Short Description:
This plugin provides a Sceme interpreter integrated 
into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins
Long Description:

This plugin integrates the Sceme R4 implementation 
produced by J. Engel to demonstrate Oolong into jEdit:-

    * Integrates the classloader with jEdit's 
JARClassLoader;
    * Integrate with Console to provide a Scheme 
Interpreter Shell;
    * Integrate with jEdit's PluginManager to enable 
Scheme Libraries to be distributed in Plugins


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1440420&group_id=588

Bugs item #1438827, was opened at 2006-02-25 19:38
Message generated for change (Comment added) made by elharo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438827&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: web site
Group: None
>Status: Open
Resolution: Fixed
Priority: 5
Submitted By: Elliotte Rusty Harold (elharo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect patch submission instructions

Initial Comment:
The jedit guidelines file at
http://cvs.sourceforge.net/viewcvs.py/jedit/guidelines/README.jEdit?rev=1.1&view=markup>
says to send patches to to the jEdit-devel mailing
list. My first patch got flagged by the mailing list
software as overly long. 

Alan Ezust suggests opening a bug report and attaching
a patch instead. Please either:

1. Chnage the guidelines to suggest doing this
(submitting via Sourceforge)

or

2. Enable longer attachments on the mailing list. (Mine
was about 29K.)

Thanks.  

----------------------------------------------------------------------

>Comment By: Elliotte Rusty Harold (elharo)
Date: 2006-02-28 06:15

Message:
Logged In: YES 
user_id=226817

Thansk for updating the web site. However the README.jEdit
file in CVS still has the old instructions and needs to be
fixed. 

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2006-02-28 02:57

Message:
Logged In: YES 
user_id=935841

I updated the website instructions.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438827&group_id=588

Bugs item #1438827, was opened at 2006-02-25 16:38
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438827&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: web site
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Elliotte Rusty Harold (elharo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect patch submission instructions

Initial Comment:
The jedit guidelines file at
http://cvs.sourceforge.net/viewcvs.py/jedit/guidelines/README.jEdit?rev=1.1&view=markup>
says to send patches to to the jEdit-devel mailing
list. My first patch got flagged by the mailing list
software as overly long. 

Alan Ezust suggests opening a bug report and attaching
a patch instead. Please either:

1. Chnage the guidelines to suggest doing this
(submitting via Sourceforge)

or

2. Enable longer attachments on the mailing list. (Mine
was about 29K.)

Thanks.  

----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2006-02-27 23:57

Message:
Logged In: YES 
user_id=935841

I updated the website instructions.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438827&group_id=588

Plugin Bugs item #1440041, was opened at 2006-02-28 02:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1440041&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: jasquigl (jasquigl)
Assigned to: Nobody/Anonymous (nobody)
Summary: Tasklist broken...

Initial Comment:
I'm not a java programmer, so forgive me if the
information I supply isn't sufficient.

[error] AWT-EventQueue-0: Exception in thread
"AWT-EventQueue-0"
[error] AWT-EventQueue-0: java.lang.NullPointerException
[error] AWT-EventQueue-0:  at
javax.swing.JTable.prepareRenderer(JTable.java:5537)
[error] AWT-EventQueue-0:  at
javax.swing.plaf.synth.SynthTableUI.paintCell(SynthTableUI.java:580)
[error] AWT-EventQueue-0:  at
javax.swing.plaf.synth.SynthTableUI.paintCells(SynthTableUI.java:477)
[error] AWT-EventQueue-0:  at
javax.swing.plaf.synth.SynthTableUI.paint(SynthTableUI.java:263)
[error] AWT-EventQueue-0:  at
javax.swing.plaf.synth.SynthTableUI.update(SynthTableUI.java:210)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintComponent(JComponent.java:710)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:975)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JViewport.paint(JViewport.java:740)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
org.gjt.sp.jedit.gui.DockableWindowManager.paintChildren(DockableWindowManager.java:1113)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JLayeredPane.paint(JLayeredPane.java:559)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintChildren(JComponent.java:811)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paint(JComponent.java:984)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintToOffscreen(JComponent.java:5077)
[error] AWT-EventQueue-0:  at
javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:279)
[error] AWT-EventQueue-0:  at
javax.swing.RepaintManager.paint(RepaintManager.java:1079)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent._paintImmediately(JComponent.java:5025)
[error] AWT-EventQueue-0:  at
javax.swing.JComponent.paintImmediately(JComponent.java:4843)
[error] AWT-EventQueue-0:  at
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:688)
[error] AWT-EventQueue-0:  at
javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:644)
[error] AWT-EventQueue-0:  at
javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManager.java:624)
[error] AWT-EventQueue-0:  at
javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:128)
[error] AWT-EventQueue-0:  at
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
[error] AWT-EventQueue-0:  at
java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
[error] AWT-EventQueue-0:  at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
[error] AWT-EventQueue-0:  at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
[error] AWT-EventQueue-0:  at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
[error] AWT-EventQueue-0:  at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
[error] AWT-EventQueue-0:  at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
[error] AWT-EventQueue-0:  at
java.awt.EventDispatchThread.run(EventDispatchThread.java:121)


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1440041&group_id=588

Hello again,

On Monday 27 February 2006 08:58, Randall R Schulz wrote:
> Hi,
>
> ...
>
> Another anomaly is that if you close all of the jEdit views, the menu
> bar (the Mac OS system-wide one, of course) loses all its jEdit menus
> leaving only the stock Java application menu (named for the
> entry-point class) and that leaves no way to create another view to
> go on working. The only meaningful option at that point is to quit,
> which fortunately is something provided by the application menu.

There's another aspect to this that's a little more pernicious: If you 
quit via the Java application menu, the application code does not get 
to go through its usual shut-down processing and the result is that the 
application state does not get saved (open file list, changed docking 
and window layout settings, etc.). The worst part is that Command-Q 
triggers this "pull the rug out from under the app" behavior, so a 
proper application menu (not the generic Java application menu) really 
must be installed.


Randall Schulz

Hi,

On Monday 27 February 2006 07:35, Randall R Schulz wrote:
> Paul,
>
> On Monday 27 February 2006 03:34, Paul Libbrecht wrote:
> > Isn't this a preference of the MacOS plugin ?
> > At worst a system-property.
>
> It's a system property: -Dapple.laf.useScreenMenuBar=true

True, but it's an option in the MacOS plug-in as well. However, the 
plug-in option seems to have no effect (even after clearing and setting 
it again and restarting jEdit).


> The application menu is still named for the class bearing the Main()
> entry point, but I'm sure that's just another system property (or a
> plist entry once a proper application is built).

Another anomaly is that if you close all of the jEdit views, the menu 
bar (the Mac OS system-wide one, of course) loses all its jEdit menus 
leaving only the stock Java application menu (named for the entry-point 
class) and that leaves no way to create another view to go on working. 
The only meaningful option at that point is to quit, which fortunately 
is something provided by the application menu.


> ...

Randall Schulz 

Paul,

On Monday 27 February 2006 03:34, Paul Libbrecht wrote:
> Isn't this a preference of the MacOS plugin ?
> At worst a system-property.

It's a system property: -Dapple.laf.useScreenMenuBar=true

The application menu is still named for the class bearing the Main() 
entry point, but I'm sure that's just another system property (or a 
plist entry once a proper application is built).

I guess this will be my introduction to Java programming on the Mac. So 
far, so good.


> paul


Randall Schulz

Paul,

On Monday 27 February 2006 03:35, Paul Libbrecht wrote:
> Btw, finding the right .app package may lead you to download a
> release version... at least I haven't found a way for it to come out
> of a build from CVS.
> paul

I don't understand this at all. As I reported, I did find the Cocoa 
classes that allow the MacOS plug-in to operate normally.

By the way, it does not have any user-visible options that relate to 
menu bar handling. I'm still looking for a system property that might 
control this aspect. (In fact, in the past day or so, I'm sure I saw 
something somewhere in my searching. Now I just need to find it again!)


Randall Schulz

Has any thought been given to embedding jEdit in other applications? Are 
there any hooks for doing so?

I've noticed that my program that calls jEdit.main() method to start it 
up, and the jEdit.exit() method to shut it down gets seriously confused 
about the third time this happens.

Is there a more sensible way to do this within the same VM and without 
forking a new process?

-- 
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

Bugs item #1439605, was opened at 2006-02-27 08:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1439605&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Elliotte Rusty Harold (elharo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Remove installer.VariableGridLayout

Initial Comment:
The class installer.VariableGridLayout says "This is
copied from jEdit's org.gjt.sp.jedit.gui package."
There seems little reasoon to do this. Why not just
import that class from that package instead? 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1439605&group_id=588

What, if any, is jEdit's convention for TODO comments? i.e. how are 
these marked in the codebase?

Grepping through the source I find several instances of XXX but only one 
or two instances of TODO. Is XXX what I should use and look for?

-- 
Elliotte Rusty Harold  el...@me...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

Btw, finding the right .app package may lead you to download a release 
version... at least I haven't found a way for it to come out of a build 
from CVS.
paul

Randall R Schulz wrote:
> Hi, Paul,
>
> On Sunday 26 February 2006 13:55, Paul Libbrecht wrote:
>   
>> Randall,
>>
>> for your information, these classes are not in the boot classpath.
>> Adding /System/Library/Java to the classpath makes it work for me.
>>     
>
> Thanks. I did that. It eliminates the exception and the alert, but the 
> main jEdit window still bears the jEdit menu bar and the Mac system 
> menu bar just has a default Java application menu.
>
>
>   
>> paul
>>     
>
>
> Randall Schulz
>
>
>   
>> Randall R Schulz wrote:
>>     
>>> Hi,
>>>
>>> I'd like to run jEdit on my shiny new iMac Core Duo (Intel
>>> processor). I retrieved the latest development source bundle and
>>> can build it and run it, but it's not quite right. After doing just
>>> the top-level ant build, the resulting jEdit runs but does not use
>>> the screen-top menu bar. Cursory use suggests it's functioning
>>> correctly. After building in the subdirectory jars/MacOS running
>>> jEdit is mostly similar, but produces a diagnostic regarding a
>>> problem loading the MacOS plug-in:
>>>
>>> [error] PluginJAR: Error while starting plugin macos.MacOSPlugin
>>> [error] PluginJAR: java.lang.NoClassDefFoundError:
>>> com/apple/cocoa/application/NSMenu [error] PluginJAR:  at
>>> macos.MacOSPlugin.start(MacOSPlugin.java:51) [error] PluginJAR:  at
>>> org.gjt.sp.jedit.PluginJAR.startPlugin(PluginJAR.java:1134) [error]
>>> PluginJAR:  at
>>> org.gjt.sp.jedit.PluginJAR.activatePlugin(PluginJAR.java:473)
>>> [error] PluginJAR:  at
>>> org.gjt.sp.jedit.PluginJAR.activatePluginIfNecessary(PluginJAR.java
>>> :536) [error] PluginJAR:  at
>>> org.gjt.sp.jedit.jEdit.main(jEdit.java:418) [error]
>>> ErrorListDialog$ErrorEntry: /Users/rschulz/jEdit/jars/MacOS.jar:
>>> [error] ErrorListDialog$ErrorEntry: Cannot start:
>>> java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
>>> [error] ErrorListDialog$ErrorEntry: Try updating to a newer version
>>> of the plugin.
>>>
>>> ...
>>>       
>
>   

Isn't this a preference of the MacOS plugin ?
At worst a system-property.

paul

Randall R Schulz wrote:
> Hi, Paul,
>
> On Sunday 26 February 2006 13:55, Paul Libbrecht wrote:
>   
>> Randall,
>>
>> for your information, these classes are not in the boot classpath.
>> Adding /System/Library/Java to the classpath makes it work for me.
>>     
>
> Thanks. I did that. It eliminates the exception and the alert, but the 
> main jEdit window still bears the jEdit menu bar and the Mac system 
> menu bar just has a default Java application menu.
>
>
>   
>> paul
>>     
>
>
> Randall Schulz
>
>
>   
>> Randall R Schulz wrote:
>>     
>>> Hi,
>>>
>>> I'd like to run jEdit on my shiny new iMac Core Duo (Intel
>>> processor). I retrieved the latest development source bundle and
>>> can build it and run it, but it's not quite right. After doing just
>>> the top-level ant build, the resulting jEdit runs but does not use
>>> the screen-top menu bar. Cursory use suggests it's functioning
>>> correctly. After building in the subdirectory jars/MacOS running
>>> jEdit is mostly similar, but produces a diagnostic regarding a
>>> problem loading the MacOS plug-in:
>>>
>>> [error] PluginJAR: Error while starting plugin macos.MacOSPlugin
>>> [error] PluginJAR: java.lang.NoClassDefFoundError:
>>> com/apple/cocoa/application/NSMenu [error] PluginJAR:  at
>>> macos.MacOSPlugin.start(MacOSPlugin.java:51) [error] PluginJAR:  at
>>> org.gjt.sp.jedit.PluginJAR.startPlugin(PluginJAR.java:1134) [error]
>>> PluginJAR:  at
>>> org.gjt.sp.jedit.PluginJAR.activatePlugin(PluginJAR.java:473)
>>> [error] PluginJAR:  at
>>> org.gjt.sp.jedit.PluginJAR.activatePluginIfNecessary(PluginJAR.java
>>> :536) [error] PluginJAR:  at
>>> org.gjt.sp.jedit.jEdit.main(jEdit.java:418) [error]
>>> ErrorListDialog$ErrorEntry: /Users/rschulz/jEdit/jars/MacOS.jar:
>>> [error] ErrorListDialog$ErrorEntry: Cannot start:
>>> java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
>>> [error] ErrorListDialog$ErrorEntry: Try updating to a newer version
>>> of the plugin.
>>>
>>>       

Hi, Paul,

On Sunday 26 February 2006 13:55, Paul Libbrecht wrote:
> Randall,
>
> for your information, these classes are not in the boot classpath.
> Adding /System/Library/Java to the classpath makes it work for me.

Thanks. I did that. It eliminates the exception and the alert, but the 
main jEdit window still bears the jEdit menu bar and the Mac system 
menu bar just has a default Java application menu.


> paul


Randall Schulz


> Randall R Schulz wrote:
> > Hi,
> >
> > I'd like to run jEdit on my shiny new iMac Core Duo (Intel
> > processor). I retrieved the latest development source bundle and
> > can build it and run it, but it's not quite right. After doing just
> > the top-level ant build, the resulting jEdit runs but does not use
> > the screen-top menu bar. Cursory use suggests it's functioning
> > correctly. After building in the subdirectory jars/MacOS running
> > jEdit is mostly similar, but produces a diagnostic regarding a
> > problem loading the MacOS plug-in:
> >
> > [error] PluginJAR: Error while starting plugin macos.MacOSPlugin
> > [error] PluginJAR: java.lang.NoClassDefFoundError:
> > com/apple/cocoa/application/NSMenu [error] PluginJAR:  at
> > macos.MacOSPlugin.start(MacOSPlugin.java:51) [error] PluginJAR:  at
> > org.gjt.sp.jedit.PluginJAR.startPlugin(PluginJAR.java:1134) [error]
> > PluginJAR:  at
> > org.gjt.sp.jedit.PluginJAR.activatePlugin(PluginJAR.java:473)
> > [error] PluginJAR:  at
> > org.gjt.sp.jedit.PluginJAR.activatePluginIfNecessary(PluginJAR.java
> >:536) [error] PluginJAR:  at
> > org.gjt.sp.jedit.jEdit.main(jEdit.java:418) [error]
> > ErrorListDialog$ErrorEntry: /Users/rschulz/jEdit/jars/MacOS.jar:
> > [error] ErrorListDialog$ErrorEntry: Cannot start:
> > java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
> > [error] ErrorListDialog$ErrorEntry: Try updating to a newer version
> > of the plugin.
> >
> > ...

Steve,

On Sunday 26 February 2006 14:13, Steve Snider wrote:
> Randall,
>
> If you search the jEdit mailing list threads from a couple of months
> back, Elloitte Rusty Harold (I believe that is his name) also posted
> about some Mac-specific work to make the application 'feel' more like
> a Mac app.  Perhaps you could dredge up that thread and see whether
> he has made any progress?

Yes. I remember that. I'll contact him to see if he has the problem 
solved or if I can do anything to help out.


> Just a thought (as a fellow Mac user, but no longer much of a
> developer).
>
> -Steve


Randall Schulz

Randall,

for your information, these classes are not in the boot classpath.
Adding /System/Library/Java to the classpath makes it work for me.

paul

Randall R Schulz wrote:
> Hi,
>
> I'd like to run jEdit on my shiny new iMac Core Duo (Intel processor). I
> retrieved the latest development source bundle and can build it and run
> it, but it's not quite right. After doing just the top-level ant build,
> the resulting jEdit runs but does not use the screen-top menu bar.
> Cursory use suggests it's functioning correctly. After building in the
> subdirectory jars/MacOS running jEdit is mostly similar, but produces a
> diagnostic regarding a problem loading the MacOS plug-in:
>
> [error] PluginJAR: Error while starting plugin macos.MacOSPlugin
> [error] PluginJAR: java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
> [error] PluginJAR:  at macos.MacOSPlugin.start(MacOSPlugin.java:51)
> [error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.startPlugin(PluginJAR.java:1134)
> [error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.activatePlugin(PluginJAR.java:473)
> [error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.activatePluginIfNecessary(PluginJAR.java:536)
> [error] PluginJAR:  at org.gjt.sp.jedit.jEdit.main(jEdit.java:418)
> [error] ErrorListDialog$ErrorEntry: /Users/rschulz/jEdit/jars/MacOS.jar:
> [error] ErrorListDialog$ErrorEntry: Cannot start: java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
> [error] ErrorListDialog$ErrorEntry: Try updating to a newer version of the plugin.
>
>
> I looked in vain in the source code and in various places on the
> jEdit.org and jEdit.sourceforge.net Web sites for information on
> building for MacOS, but found precious little.
>
> I should say, I'm new to MacOS X programming (I used to do MacOS
> programming, but only up through release 9 of MacOS, which as we all
> know was an entirely different beast). I have the latest everything (OS,
> utilities, XCode 2.2.1, and the Java 5.0 SDK pre-release from just a
> couple of days ago).
>
> Can anybody give me some pointers? Time permitting, I'd be willing to
> contribute to producing a MacOS application package for jEdit.
>
>
> Thanks.
>
>
> Randall Schulz
>
>
>   

Hi,

I'd like to run jEdit on my shiny new iMac Core Duo (Intel processor). I
retrieved the latest development source bundle and can build it and run
it, but it's not quite right. After doing just the top-level ant build,
the resulting jEdit runs but does not use the screen-top menu bar.
Cursory use suggests it's functioning correctly. After building in the
subdirectory jars/MacOS running jEdit is mostly similar, but produces a
diagnostic regarding a problem loading the MacOS plug-in:

[error] PluginJAR: Error while starting plugin macos.MacOSPlugin
[error] PluginJAR: java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
[error] PluginJAR:  at macos.MacOSPlugin.start(MacOSPlugin.java:51)
[error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.startPlugin(PluginJAR.java:1134)
[error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.activatePlugin(PluginJAR.java:473)
[error] PluginJAR:  at org.gjt.sp.jedit.PluginJAR.activatePluginIfNecessary(PluginJAR.java:536)
[error] PluginJAR:  at org.gjt.sp.jedit.jEdit.main(jEdit.java:418)
[error] ErrorListDialog$ErrorEntry: /Users/rschulz/jEdit/jars/MacOS.jar:
[error] ErrorListDialog$ErrorEntry: Cannot start: java.lang.NoClassDefFoundError: com/apple/cocoa/application/NSMenu
[error] ErrorListDialog$ErrorEntry: Try updating to a newer version of the plugin.


I looked in vain in the source code and in various places on the
jEdit.org and jEdit.sourceforge.net Web sites for information on
building for MacOS, but found precious little.

I should say, I'm new to MacOS X programming (I used to do MacOS
programming, but only up through release 9 of MacOS, which as we all
know was an entirely different beast). I have the latest everything (OS,
utilities, XCode 2.2.1, and the Java 5.0 SDK pre-release from just a
couple of days ago).

Can anybody give me some pointers? Time permitting, I'd be willing to
contribute to producing a MacOS application package for jEdit.


Thanks.


Randall Schulz

Plugin Central Submission item #1438856, was opened at 2006-02-26 16:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1438856&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Neil Bertram (n31l)
Assigned to: Nobody/Anonymous (nobody)
Summary: TypoScript 0.1.1 tagged

Initial Comment:
Name: TypoScript
Version: 0.1.1

Requirements:
* jEdit 4.2final
* JakartaCommons 0.4.4
* JDK 1.4

Announcement:
Added support for multiple templates per page to be
displayed in the site browser, fixed some reported
bugs, reduced dependency to 4.2final. Will now
automatically install the typoscript edit mode when
it's not available.

Source (CVS):
plugins/TypoScript
tag: typoscript-0_1_1

Descriptions unchanged.

Have dropped the dep to 4.2 and added a clean target as
Jeffrey asked for last time.

I would appreciate it if this could be bundled and
released reasonably soon, as people are starting to
download the old version and email me asking for the
same new features over and over, which this version
provides. Also a new major release of TYPO3 (4.0) is
imminent, which the previous version of this plugin
doesn't support.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1438856&group_id=588

Bugs item #1438828, was opened at 2006-02-25 19:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438828&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: editor core
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Elliotte Rusty Harold (elharo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unnecessary casts

Initial Comment:
The jEdit code base contains various redundant casts
which Eclipse flags. The attache dpatch removes them.  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438828&group_id=588

Bugs item #1438827, was opened at 2006-02-25 19:38
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438827&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: web site
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Elliotte Rusty Harold (elharo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incorrect patch submission instructions

Initial Comment:
The jedit guidelines file at
http://cvs.sourceforge.net/viewcvs.py/jedit/guidelines/README.jEdit?rev=1.1&view=markup>
says to send patches to to the jEdit-devel mailing
list. My first patch got flagged by the mailing list
software as overly long. 

Alan Ezust suggests opening a bug report and attaching
a patch instead. Please either:

1. Chnage the guidelines to suggest doing this
(submitting via Sourceforge)

or

2. Enable longer attachments on the mailing list. (Mine
was about 29K.)

Thanks.  

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1438827&group_id=588

Plugin Central Submission item #1437661, was opened at 2006-02-23 12:11
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1437661&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Alan Ezust (ezust)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Console 4.2.4 Tagged in CVS

Initial Comment:
cvs tag: Console_4_2_3

*  Console Version 4.2.3 Requires jEdit 4.2 final, JDK
1.5, ErrorList 1.3.5, ProjectViewer 2.1.1 (optional)
          o  Closing one View does not remove toolbars
from all other views.
          o  Un-broke some earlier plugin-breaking
changes. (Alan Ezust)
          o  Improved Perl error pattern

*  Version 4.2.2 Requires jEdit 4.2 final, JDK 1.5,
ErrorList 1.3.5, ProjectViewer 2.1.1 (optional)
      o     Now it is possible to enable/disable
individual error
  			    matchers with a checkbox there.

      o  Rewrote the Error Pattern dialog into a
JPanel, embeddable in the larger
         OptionPane. No more popping up of dialogs for
editing an error pattern. (Alan Ezust) 
*      Version 4.2.1 Requires jEdit 4.2 final,
ErrorList 1.3.5, and JDK 1.5. Optional: Projectviewer
2.1.0.92 (for listening to events).
      o  Rewrote command execution part to use the JDK
1.5 ProcessBuilder class. This made it possible to
merge stdout and stderr, which means that the output of
make, which sends its "entering/leaving" messages to
stdout, and its error messages to stderr, can be merged
into one stream for parsing.
      o  Applied encoding patch from jedit-plugin-bugs
#1245860.
      o  Context menu on commando buttons lets you
hide/customize the built-in commands with ease.
      o  New beanshell commands bound to system shell
actions: chdir to ProjectViewer root, and chdir to
ProjectViewer current.
      o  Option to bind the above actions to new
ProjectViewer Events.
      o  Console Preferences allow you to set a prefix,
so you can run each command in an alternate shell (not
working yet). 
      
*  Version 4.2 Requires jEdit 4.2 final, JDK 1.4, and
ErrorList 1.3.5
      o Possibility of testing regular expressions in
the Plugin Options - Console - Error Patterns.
      o Rewrote to use java.util.Pattern instead of
gnu.regex.RE.
      o Possibility of selecting which Commando buttons
are shown in the toolbar.
      o Added some more Commando buttons (make, ant) to
choose from.
      o Misc bugfixes - Alan Ezust
    


----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2006-02-25 12:48

Message:
Logged In: YES 
user_id=935841

CVS Tag: Console_4_2_4

Only made changes to the documentation, and replaced the
build.xml file with one that uses the build-support plugin.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=1437661&group_id=588

On 2/25/06, Elliotte Harold <el...@me...> wrote:
> Two questions:
>
> 1. Is there any difference between de...@je... and
> jed...@li...? Are they just aliases for each other?
> I seem to have managed to get both into my address book.

good question.

> 2. The jedit guidelines file
> <http://cvs.sourceforge.net/viewcvs.py/jedit/guidelines/README.jEdit?rev=
=3D1.1&view=3Dmarkup>
> says to send patches to to the jEdit-devel mailing list. My first patch
> got flagged by the mailing list software as overly long. Should it justw
> wait in the moderation queue or should I submit it via a SourceForge bug
> report or some other mechanism instead?

Try opening a bug in the tracker and attaching the patch as an
attachment. That would be better.