jedit-devel Mailing List for jEdit

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

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Alain Robert (arobert)
>Assigned to: Ollie Rutherfurd (orutherfurd)
>Summary: JBrowse-1.4.5

Initial Comment:
Name: 
Java Browser

Version Number: 
1.4.5 

Requirements:
JDK 1.4.1 
jEdit 4.2 Pre9

plugin dependencies:
none

required third-party applications
none

Announcement:
updated to support the new plugins framework jEdit 4.2.

Source Code:
plugins/JBrowse
tag: jbrowse-1_4_5


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

>Comment By: Ollie Rutherfurd (orutherfurd)
Date: 2004-02-29 17:48

Message:
Logged In: YES 
user_id=265596

Hi Alain, when packaging JBrowse I noticed activate was set
to 'startup'.  Does it need to be set to startup, or could
it be 'defer'? I tried it w/defer and things seemed to work
ok, but I didn't dig too deep.

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

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

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

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Brad Mace (bemace)
>Assigned to: Ollie Rutherfurd (orutherfurd)
Summary: JCounter 0.5.0

Initial Comment:
JCounter v0.5.0

Requirements:
jdk 1.4.1
jedit 04.02.08.00
ProjectViewer 2.0.2
CommonControls 0.8.2

Announcement:
Updated for new plugin API and ProjectViewer 2.0.2

Source:
plugins/JCounter tag: release-0_5_0

Description:

Provides statistics such as Code, Comment, code %, and
blank lines for files.  It can parse the current
buffer, all open buffers, or all files from a project
in the Project Viewer plugin, and provides averages,
maxs, and totals.

Long Description:

Provides statistics such as Code, Comment, code %, and
blank lines for files.  It can parse the current
buffer, all open buffers, or all files from a project
in the Project Viewer plugin, and provides averages,
maxs, and totals.  For Java files, it also counts
methods and imports, parses class/interface names, and
displays interface names in italic.



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

>Comment By: Ollie Rutherfurd (orutherfurd)
Date: 2004-02-29 16:37

Message:
Logged In: YES 
user_id=265596

Hey Brad, below is a patch for actions.xml -- w/o it I'm
getting a bunch of Beanshell errors when I try to invoke
some of the actions.  Also, I'm getting NPEs when either
clicking on a row in the JCounter dockable to switch to a
buffer or when jEdit is opened with the JCounter dockable open.

Index: actions.xml
===================================================================
RCS file: /cvsroot/jedit/plugins/JCounter/actions.xml,v
retrieving revision 1.2
diff -u -b -i -r1.2 actions.xml
--- actions.xml	24 Jan 2003 18:18:00 -0000	1.2
+++ actions.xml	29 Feb 2004 21:25:27 -0000
@@ -19,19 +19,19 @@
 	<ACTION NAME="jcounter.reparse-all">
 		<CODE>
 		
view.getDockableWindowManager().addDockableWindow("jcounter");
-			JCounterProperties.getInstance().getSource().init();
+		
jcounter.JCounterProperties.getInstance().getSource().init();
 		</CODE>
 	</ACTION>
 	<ACTION NAME="jcounter.export-flat">
 		<CODE>
 		view.getDockableWindowManager()
-               
.getDockable(JCounterPlugin.NAME).exportToFlatFile();
+               
.getDockable(jcounter.JCounterPlugin.NAME).exportToFlatFile();
 		</CODE>
 	</ACTION>
 	<ACTION NAME="jcounter.export-wiki">
 		<CODE>
 		view.getDockableWindowManager()
-               
.getDockable(JCounterPlugin.NAME).exportToWiki();
+               
.getDockable(jcounter.JCounterPlugin.NAME).exportToWiki();
         </CODE>
 	</ACTION>
 </ACTIONS>



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

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

hallo giulio,

i am sorry, i couldn't understand much of your post or was too 
impatient to or whatever.

looking at jean's reply now i wonder if what you want to achieve 
looks like this:

http://home.nexgo.de/blackwell/downloads/SideKickJavaParser.png

because if so, you can see that it is seemingly possible without a 
problem.



with best regards

blackwell

Bugs item #849573, was opened at 2003-11-26 12:04
Message generated for change (Comment added) made by igge_1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=849573&group_id=588

Category: editor core
Group: minor bug
Status: Open
Resolution: None
Priority: 5
Submitted By: Daniel Aarno (macbishop)
Assigned to: Nobody/Anonymous (nobody)
Summary: tilde (~) doest not work with international keyboard layouts

Initial Comment:
Using international keyboard layaouts (Swedish) I am unable 
to type the characters ~ and ^ in jEdit 4.x. This problem 
shows up on both Linux and Mac OS X using JVM 1.4.x. I 
have also come across this on Solaris, but I'm unable to 
check the version of that JVM. Switching to US keyboard 
layout imediately solves the problem.

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

Comment By: igge (igge_1)
Date: 2004-02-29 21:24

Message:
Logged In: YES 
user_id=930107

Yeah, I have found out a solution. I installed Java 1.5.0 Beta and now it works!

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

Comment By: igge (igge_1)
Date: 2004-02-11 21:43

Message:
Logged In: YES 
user_id=930107

Same problem here.

German keyboard, jedit 4.1 and 4.2pre9, Java 1.4.2

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

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

Hi Giulo ,

> I also fired up the JythonInterpreter plugin, just to have a look
> at how a
> Python script has been represented in the Structure Browser. You
> see, the
> Python case is much more similar to my own Prolog case, because
> there is no
> easy way to provide a single root for a tree representation: it's
> not like
> the Java case, where you could suppose a binary correspondence
> between
> files and classes, and using the single class included in each file
> as the
> root for your tree representation; it's not like the XML case,

when writing the jpydebug pluggin which is a Python debugger's pluggin
, I also provide a tree representation of the Python source using the
sidekick pluggin inside the debugger. I have been faced with the
single root limitation. For the python language this is not a big
problem assuming you accept to represent the python tree in the
following way :

#filename.py
|
--- # modulename ( =3D> filename minus the py suffix )
     |
     --- classes
     |
     --- functions

The above representation is just a way to work around the sidekick
single root assuming that python syntax makes a clean separation
between the python file container and the module name which may be
considered as a namespace , even if the module name is deduced from
the python file name.

Jean-Yves

On Sun, 29 Feb 2004 17:02:24 +0100, Giulio Piancastelli wrote:

>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick






_____________________________________________________________________
Envie de discuter en "live" avec vos amis ? Télécharger MSN Messenger
http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France

Hi all,

I'm currently writing Sidekick support for my PrologConsole plugin, and 
while trying to offer an appropriate tree structure to the Structure 
Browser, I stumbled across a strange behaviour in the navigation facilities 
provided by Sidekick. It is in fact my undestanding (and the premise of 
this whole message) that, in order to be able to navigate the tree 
structure, an asset after another using the Go To Next Asset action 
provided by Sidekick, that tree structure must feature a single root other 
than the element representing the file, which always appears in the 
Structure Browser, even if no parser is provided for the particular buffer. 
That is, the structure should appear as follows:

#Filename
|
---#SingleRoot
    |
    ---#AnElement
    |
    ---#AnotherElement
    |  |
    |  ---#ASubElement
    ---#YetAnotherElement

It still is my understanding that, if the #SingleRoot element is missing, 
thus the tree is somewhat rooted at #Filename, trying to navigate the 
document asset by asset with the Go To Next Asset facility will likely 
result in a failure, for example with the navigation halting between two 
assets separated by one or more empty lines. Mind you, I did not have a 
look at Sidekick's source: I'm just reporting what I see developing my own 
support and using some of the plugins that already support Sidekick's 
Structure Browser.

In fact, I had a look at how Jane treats Java source files. The #SingleRoot 
element is the public class contained in the buffer, having fields and 
methods as children. But, if after a public class declaration, another 
class (now with the default package visibility) is added, Jane does not 
display it in the Structure Browser. The navigation asset by asset in the 
buffer works, just because there is that #SingleRoot element, but at the 
cost of completely ignoring other classes defined in the buffer.
Eclipse got it right: it sees the file as a compilation unit, not just as a 
*single* class container. As such, it can contain many different class 
definitions. But, to let Jane treat Java files as Eclipse does, the 
#SingleRoot element should now represent the source file as a class(es) 
container. Alas, there already is an element representing the file in the 
Structure Browser, and there is no point in duplicating it. But, if more 
classes would be added to the tree, as children of #Filename, the 
navigation asset by asset would stop working at some point in the middle of 
the buffer.

Then, I tried out the XML plugin. XML documents should be rather easy to 
represent as trees, because they are, in fact, trees by design. But, that's 
not entirely the story. In fact, you have a root element in any XML 
document, with children, subchildren and leaf and all that, and the 
structure would be a perfect tree if you just decided not to consider the 
XML prologue, DOCTYPE declarations, and processing instructions like 
stylesheets associated with the document. This is exactly what the XML 
plugin does: it provides a perfectly reasonable tree structure with 
#SingleRoot being the root element of the XML document, a structure that 
can be navigated asset by asset without a single problem, but at the cost 
of forgetting to represent the XML prologue and the other elements I've 
already listed. Now suppose to include those forgotten elements in a tree 
structure representing an XML file: which would now be the root element of 
that structure? I believe it would be an element labelled with the name of 
the represented file... but, again, such an element already exists in the 
Structure Browser, and there is no point in duplicating it.

I also fired up the JythonInterpreter plugin, just to have a look at how a 
Python script has been represented in the Structure Browser. You see, the 
Python case is much more similar to my own Prolog case, because there is no 
easy way to provide a single root for a tree representation: it's not like 
the Java case, where you could suppose a binary correspondence between 
files and classes, and using the single class included in each file as the 
root for your tree representation; it's not like the XML case, where you 
could easily exploit the natural mapping between trees and XML structures, 
just forgetting elements which are very likely not to be touched again once 
they are written down.
And, in fact, the author(s) of the JythonInterpreter plugin did the same 
thing I did (at least until now) for my Prolog support: they did not 
feature a #SingleRoot element in the Structure Browser tree representation. 
Then, I did try to navigate the Python buffer asset by asset, only to be 
stroken by the same flaw already experienced for Prolog buffers: the 
navigation stops at some point in the buffer, for example when two 
first-level assets are separated by one or more empty lines.

 From what I've seen, it seems that a tree structure does not perfectly 
match with any of the source code in three of the most used (at least by me 
;)) languages today (plus, of course, Prolog). In fact, it also seems that 
when a tree structure can be perfectly navigated asset by asset, such a 
structure have abstracted away some part of the source contained in the 
buffer currently represented. (The benefits of this abstraction could be 
questionable: while I'm more than happy to forget about the XML prologue 
and DOCTYPE declarations, which I write once and never touch again for each 
document, I'm not so eager on giving up one or more Java classes 
representation.) On the other hand, when the tree structure try to 
faithfully represent a buffer's contents, it must give up on the navigation 
facility, whenever a candidate for a #SingleRoot element does not clearly 
stands out (which, I would say, happens in all the cases I've described). 
More often than not, anyway, the only candidate for the #SingleRoot role 
would be an element representing the file, such the #Filename element: but 
that's already always present in any Structure Browser representation, and 
there's no point in duplicating it: for example, I could easily fake a 
#SingleRoot in Prolog files using the Theory concept, that is every Prolog 
file represents a theory composed by the predicates contained in it, but 
how would I name such an element? I'll probably use the same filename, and 
even if I could use different icons, or fall back on the fact that the two 
elements (#Filename and #SingleRoot) are on different levels in the tree to 
distinguish between the two, you can clearly see that the file and theory 
concepts overlaps each other to the extent I'd say they are really the same.

All this long message has been written just to illustrate a situation and 
to ask for suggestions on how to cope with it: do Slava (the author of 
Sidekick) and other plugins developers who offer Sidekick support feel that 
something should be changed in the way Structure Browser trees are 
navigated asset by asset, or should I (and probably others, just remember 
the JythonInterpreter plugin case) fake some kind of root element for my 
buffers' representation, and learn to live with it?

Thank you very much in advance for any help.

Best Regards,
Giulio Piancastelli.

PS - I'm sorry if I have neglected plugins offering Sidekick support other 
than the three (Jane, JythonInterpreter, XML) I've based my analysis on 
(maybe LatexTools?), but I've only tried the ones supporting the languages 
I use on a regular basis.

Plugin Central Submission item #906917, was opened at 2004-02-29 14:27
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=906917&group_id=588

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Wiktor Adamski (wadamski)
Assigned to: Nobody/Anonymous (nobody)
Summary: JavaFold - folding mode for java sources

Initial Comment:
Provides folding for:
- code blocks embraced by brackets {} (skips brackets 
in comments and strings),
- multi-line comments,
- single-line comments,
- lines that ends with ';' - e.g. may be used to fold 
imports.

Version 0.1 (for jEdit 4.1):
- src : 
http://bardzotajnekonto.w.interia.pl/JavaFold_0.1.zip
- bin : 
http://bardzotajnekonto.w.interia.pl/JavaFold_0.1.jar

Version 0.2 (for jEdit 4.2):
- src : 
http://bardzotajnekonto.w.interia.pl/JavaFold_0.2.zip
- bin : 
http://bardzotajnekonto.w.interia.pl/JavaFold_0.2.jar



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

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

Bugs item #906548, was opened at 2004-02-28 18:15
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=906548&group_id=588

Category: text area and syntax packages
Group: minor bug
Status: Open
Resolution: None
Priority: 5
Submitted By: Matt Francis (mattfrancis)
Assigned to: Nobody/Anonymous (nobody)
Summary: BeanShell error after simple editing operation

Initial Comment:
(jEdit version 4.2pre9)

A simple editing operation leads to a BeanShell error 
(stack trace attached).

To reproduce:

- Begin a new buffer (File->New).

- Set edit mode to "c++" (Utilities->Buffer Options).

- Type "X}", cursor left and press return.

- BeanShell error should be thrown.


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

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

Thanks for your help there. I think I've actually hit upon a way of doing
what I need by invoking the Javadoc classes. Obviously this means you'd need
tools.jar available, and there may be other issues I haven't stumbled on
yet, but it looks good so far and has the advantages that all the parser
code is written for me by Sun :-) and there shouldn't be too many problems
getting it to work with Java 1.5 syntax code.

What would be interesting would be a framework for storing properties on a
plugin-specific basis. e.g. jEdit exports a service via the ServiceManager
with get and set property methods, then Project Viewer or Sessions come
along with implementations of that service & the user can then save
properties such as classpaths by project without having a specific
dependency on a plugin.

Obviously this is a half-formed idea at best, as there are a great many
properties you wouldn't want to store in this way, and it would be nice not
to have to use different property setter methods.

----- Original Message -----
From: "Slava Pestov" <sl...@je...>
To: <jed...@li...>
Sent: Friday, February 27, 2004 9:09 PM
Subject: Re: [ jEdit-devel ] Feature Request - Plugin Property Namespacing.


> A change like this would break too much. Too much code exists that
> assumes a single namespace.
>
> Just use common sense -- prefix your names with a resonably unique
> prefix...
>
> On Mon, 2004-02-23 at 09:49, Anthony Roy wrote:
> > I think it would be a good idea to namespace the properties defined in a
> > plugins xxx.props file. The idea would be to prepend the plugin name to
> > the start of any property defined in xxx.props, so that a property
> > aaa.bbb = blah would be saved as the jedit property xxx.aaa.bbb = blah
> >
> > Alternatively properties could be enforced to be prepended with the
> > plugin name by a simple checker which rejected the plugin for loading if
> > the properties were not in the correct format.
> >
> > An approach like one of these would not be particularly resource
> > consuming in the plugin architecture, but would prevent property
> > conflicts between plugins and the jEdit core or indeed other plugins.
> >
> > I may just be clumsy or unlucky, but I have had conflicts with both of
> > my plugins, one between Jazzy and the Aspell spellchecking plugin, where
> > both defined the check-spelling property to name an action, and recently
> > where the LaTeXTools General Option Pane replaces the jEdit Global
> > options General Panel (now fixed in CVS and resubmitted to Plugin
> > Central :-) ).
> >
> > Clearer guidelines should be provided in the plugin documentation
> > perhaps, but I don't think that plugins should be allowed to operate
> > outside of their own scope without some work (such as initialization
> > code which explicitly calls jEdit.setProperty(key, value) for example).
> > There should even perhaps be a setQualifiedProperty(key, value) method
> > in the EditPlugin class which ensures that the key is prepended with the
> > name of the plugin, and adds it if not.
> >
> > Discuss... :-)
> >
> > --
> > Anthony.
> >
> > e: ho...@an...
> > w: http://www.ant-roy.co.uk
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> --
> Slava Pestov
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel

On Fri, 2004-02-27 at 22:09, Slava Pestov wrote:

> A change like this would break too much. Too much code exists that
> assumes a single namespace.
> 
> Just use common sense -- prefix your names with a resonably unique
> prefix...

Maybe that's not the case to put these changes in right now, maybe you
could branch for something like 5 or what is, in your mind, the next
major release.

my 0.2EURO

-- 
Thelmo

Plugin Central Submission item #906336, was opened at 2004-02-27 23:14
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=906336&group_id=588

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Alain Robert (arobert)
Assigned to: Nobody/Anonymous (nobody)
Summary: Java Browser 1.4.5

Initial Comment:
Name: 
Java Browser

Version Number: 
1.4.5 

Requirements:
JDK 1.4.1 
jEdit 4.2 Pre9

plugin dependencies:
none

required third-party applications
none

Announcement:
updated to support the new plugins framework jEdit 4.2.

Source Code:
plugins/JBrowse
tag: jbrowse-1_4_5


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

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

Fixing this is not possible at the moment -- the syntax engine is not
flexible enough.

On Fri, 2004-02-27 at 14:13, Dale Anson wrote:
> I noticed when adjusting html.xml that if my html file has something 
> like this:
> 
> <script>
> <!--
>    (script goes here)
> //--></script>
> 
> Then syntax hightlighting is wrong after the </script>. If I change the 
> html like this:
> 
> <script>
> <!--
>    (script goes here)
> //-->
> </script>
> 
> Then it works correctly.
> 
> I'm not an expert on the edit modes, does anyone know how to adjust 
> html.xml to work correctly in the first example? I realize that the 
> example is bad form, but I'm working with a bunch of html files 
> generated by someone else.
> 
> Thanks,
> 
> Dale
> 
> 
> Dale Anson wrote:
> > Attached is a patch for the html editing mode. It adds html tag names as 
> > keywords. I split out table and form elements in particular so they can 
> > be color-coded differently than the other tags, which makes it a lot 
> > easier to pick out the form elements embedded in a table with a lot of 
> > in-line styles.
> > 
> > Dale
> > 
> > 
> > ------------------------------------------------------------------------
> > 
> > --- html.xml	2004-01-29 09:41:00.000000000 -0800
> > +++ new_html.xml	2004-02-26 13:51:34.000000000 -0800
> > @@ -43,6 +43,8 @@
> >  			<BEGIN>&amp;</BEGIN>
> >  			<END>;</END>
> >  		</SPAN>
> > +      
> > +      
> >  	</RULES>
> >  
> >  	<!-- ESCAPE is not exactly right but it is needed to correctly
> > @@ -59,6 +61,116 @@
> >  		</SPAN>
> >  
> >  		<SEQ TYPE="OPERATOR">=</SEQ>
> > + 		<KEYWORDS>
> > +         <!-- mostly block elements -->
> > +         <KEYWORD1>HTML</KEYWORD1>
> > +         <KEYWORD1>HEAD</KEYWORD1>
> > +         <KEYWORD1>BODY</KEYWORD1>
> > +         <KEYWORD1>FRAMESET</KEYWORD1>
> > +         <KEYWORD1>ADDRESS</KEYWORD1>
> > +         <KEYWORD1>BLOCKQUOTE</KEYWORD1>
> > +         <KEYWORD1>CENTER</KEYWORD1>
> > +         <KEYWORD1>DEL</KEYWORD1>
> > +         <KEYWORD1>DIV</KEYWORD1>
> > +         <KEYWORD1>H1</KEYWORD1>
> > +         <KEYWORD1>H2</KEYWORD1>
> > +         <KEYWORD1>H3</KEYWORD1>
> > +         <KEYWORD1>H4</KEYWORD1>
> > +         <KEYWORD1>H5</KEYWORD1>
> > +         <KEYWORD1>H6</KEYWORD1>
> > +         <KEYWORD1>HR</KEYWORD1>
> > +         <KEYWORD1>INS</KEYWORD1>
> > +         <KEYWORD1>ISINDEX</KEYWORD1>
> > +         <KEYWORD1>NOSCRIPT</KEYWORD1>
> > +         <KEYWORD1>P</KEYWORD1>
> > +         <KEYWORD1>PRE</KEYWORD1>
> > +         <KEYWORD1>DIR</KEYWORD1>
> > +         <KEYWORD1>DL</KEYWORD1>
> > +         <KEYWORD1>DT</KEYWORD1>
> > +         <KEYWORD1>DD</KEYWORD1>
> > +         <KEYWORD1>LI</KEYWORD1>
> > +         <KEYWORD1>MENU</KEYWORD1>
> > +         <KEYWORD1>OL</KEYWORD1>
> > +         <KEYWORD1>UL</KEYWORD1>
> > +         <KEYWORD1>ABBR</KEYWORD1>
> > +         <KEYWORD1>ACRONYM</KEYWORD1>
> > +         <KEYWORD1>CITE</KEYWORD1>
> > +         <KEYWORD1>CODE</KEYWORD1>
> > +         <KEYWORD1>DEL</KEYWORD1>
> > +         <KEYWORD1>DFN</KEYWORD1>
> > +         <KEYWORD1>EM</KEYWORD1>
> > +         <KEYWORD1>INS</KEYWORD1>
> > +         <KEYWORD1>KBD</KEYWORD1>
> > +         <KEYWORD1>SAMP</KEYWORD1>
> > +         <KEYWORD1>STRONG</KEYWORD1>
> > +         <KEYWORD1>VAR</KEYWORD1>
> > +         <KEYWORD1>B</KEYWORD1>
> > +         <KEYWORD1>BIG</KEYWORD1>
> > +         <KEYWORD1>I</KEYWORD1>
> > +         <KEYWORD1>S</KEYWORD1>
> > +         <KEYWORD1>SMALL</KEYWORD1>
> > +         <KEYWORD1>STRIKE</KEYWORD1>
> > +         <KEYWORD1>TT</KEYWORD1>
> > +         <KEYWORD1>U</KEYWORD1>
> > +         <KEYWORD1>FRAMESET</KEYWORD1>
> > +         <KEYWORD1>FRAME</KEYWORD1>
> > +         <KEYWORD1>NOFRAMES</KEYWORD1>
> > +         <KEYWORD1>BASE</KEYWORD1>
> > +         <KEYWORD1>ISINDEX</KEYWORD1>
> > +         <KEYWORD1>LINK</KEYWORD1>
> > +         <KEYWORD1>META</KEYWORD1>
> > +         <KEYWORD1>SCRIPT</KEYWORD1>
> > +         <KEYWORD1>STYLE</KEYWORD1>
> > +         <KEYWORD1>TITLE</KEYWORD1>
> > +         
> > +         <!-- table tags -->
> > +         <KEYWORD2>TABLE</KEYWORD2>
> > +         <KEYWORD2>CAPTION</KEYWORD2>
> > +         <KEYWORD2>COLGROUP</KEYWORD2>
> > +         <KEYWORD2>COL</KEYWORD2>
> > +         <KEYWORD2>THEAD</KEYWORD2>
> > +         <KEYWORD2>TFOOT</KEYWORD2>
> > +         <KEYWORD2>TBODY</KEYWORD2>
> > +         <KEYWORD2>TR</KEYWORD2>
> > +         <KEYWORD2>TD</KEYWORD2>
> > +         <KEYWORD2>TH</KEYWORD2>
> > +         
> > +         
> > +         <!-- form tags -->
> > +         <KEYWORD3>FORM</KEYWORD3>
> > +         <KEYWORD3>BUTTON</KEYWORD3>
> > +         <KEYWORD3>FIELDSET</KEYWORD3>
> > +         <KEYWORD3>LEGEND</KEYWORD3>
> > +         <KEYWORD3>INPUT</KEYWORD3>
> > +         <KEYWORD3>LABEL</KEYWORD3>
> > +         <KEYWORD3>SELECT</KEYWORD3>
> > +         <KEYWORD3>OPTGROUP</KEYWORD3>
> > +         <KEYWORD3>OPTION</KEYWORD3>
> > +         <KEYWORD3>TEXTAREA</KEYWORD3>
> > +         
> > +         
> > +         <!-- tags that don't fit above -->
> > +         <KEYWORD4>A</KEYWORD4>
> > +         <KEYWORD4>APPLET</KEYWORD4>
> > +         <KEYWORD4>BASEFONT</KEYWORD4>
> > +         <KEYWORD4>BDO</KEYWORD4>
> > +         <KEYWORD4>BR</KEYWORD4>
> > +         <KEYWORD4>FONT</KEYWORD4>
> > +         <KEYWORD4>IFRAME</KEYWORD4>
> > +         <KEYWORD4>IMG</KEYWORD4>
> > +         <KEYWORD4>MAP</KEYWORD4>
> > +         <KEYWORD4>AREA</KEYWORD4>
> > +         <KEYWORD4>OBJECT</KEYWORD4>
> > +         <KEYWORD4>PARAM</KEYWORD4>
> > +         <KEYWORD4>Q</KEYWORD4>
> > +         <KEYWORD4>SCRIPT</KEYWORD4>
> > +         <KEYWORD4>SPAN</KEYWORD4>
> > +         <KEYWORD4>SUB</KEYWORD4>
> > +         <KEYWORD4>SUP</KEYWORD4>
> > +         
> > +
> > +
> > +      </KEYWORDS>
> >  	</RULES>
> >  
> >  	<RULES SET="JAVASCRIPT" DEFAULT="MARKUP" IGNORE_CASE="TRUE">
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
-- 
Slava Pestov

Plugin Central Submission item #894530, was opened at 2004-02-10 13:04
Message generated for change (Comment added) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=894530&group_id=588

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Rob Fletcher (rfletch6)
>Assigned to: Ollie Rutherfurd (orutherfurd)
Summary: JTools 1.6

Initial Comment:
Name: JTools

Version: 1.6

Author: Robert Fletcher (rfl...@ya...)

Source: CVS plugins/JTools tagged "release-1_6"

Requirements: Java 1.3, jEdit 4.2pre5, ErrorList 1.3, 
CommonControls 0.8, JakartaCommons 
0.3, JavaCore 0.6

Announcement: New version uses JavaCore for 
classpath management, improves the Extend Wizard and 
fixes a few minor bugs.

Short Description: The JTools plugin provides a set of 
commands designed for managing import statements in 
Java code and creating boilerplate code for extended 
classes.

Long Description: The JTools plugin provides a set of 
commands designed for managing import statements in 
Java code and creating boilerplate code for extended 
classes. Commands include inserting an import 
statement for the classname under the caret, validating 
imports and resolving of wildcards, sorting of import 
statements, converting all imports to wildcards and an 
extend wizard.

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

>Comment By: Ollie Rutherfurd (orutherfurd)
Date: 2004-02-27 17:42

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

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

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

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

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Rob Fletcher (rfletch6)
>Assigned to: Ollie Rutherfurd (orutherfurd)
Summary: JavaCore 0.6

Initial Comment:
Name: JavaCore

Version: 0.6

Author: Robert Fletcher (rfl...@ya...)

Source: CVS plugins/JavaCore tagged "release-0_6"

Requirements: Java 1.3, jEdit 4.2pre5, JakartaCommons 
0.3

Short Description: The JavaCore plugin is designed to 
act as a central location for the management of 
classpaths and sourcepaths that may be used by other 
Java-centric plugins.

Long Description: The JavaCore plugin is designed to act 
as a central location for the management of classpaths 
and sourcepaths that may be used by other Java-
centric plugins. It uses jEdit 4.2's services API to tie 
together plugins providing classpath/sourcepath 
information and those using it. Neither need be aware of 
the other. This allows the user to select the service 
most useful to their style of work. A default service is 
included.

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

>Comment By: Ollie Rutherfurd (orutherfurd)
Date: 2004-02-27 17:30

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

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

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

Plugin Central Submission item #899295, was opened at 2004-02-17 21:53
Message generated for change (Comment added) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=899295&group_id=588

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Brad Mace (bemace)
>Assigned to: Ollie Rutherfurd (orutherfurd)
Summary: JUnitPlugin 0.0.3

Initial Comment:
JUnitPlugin 0.0.3

Requirements:
	* JDK 1.3.1
	* jEdit 4.2pre8
	* CommonControls 0.2

Announcement:
	Updated for 4.2

Source:
	plugins/JUnitPlugin
	tag: release-0_0_3


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

>Comment By: Ollie Rutherfurd (orutherfurd)
Date: 2004-02-27 17:21

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

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

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

Plugin Central Submission item #892427, was opened at 2004-02-07 10:21
Message generated for change (Comment added) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=892427&group_id=588

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: matteo galiazzo (matteogaliazzo)
>Assigned to: Oliver Rutherfurd (orutherfurd)
Summary: phpCompletionPlugin

Initial Comment:
This is a completion-code plugin for php. It parses the working file, 
the included/required files, if they are reacheable, builds an object 
oriented representation of the code, then popups a window with the 
prompts. 

The prompted elements are: 
- global, local variables (and the parameters if we are inside a 
function);
- methods and variables of a class and the classes it extends from 
if we type -> after an object instance;
- methods of a class if we type :: after a class name;
- php functions from the selecteds function groups and predefined 
variables;
- defines.
You can switch-off/on the prompted elements with the checkboxes 
in the option panel. 
For the predefined functions you can choose which function groups 
activate/deactivate. 
You can also choose the rendering style for each element.

Since I love object-oriented programming I have written this plugin 
for using php in a object oriented way. 


I think the code is still full of bugs, and the parser crashes with 
non-linear code (ex. classes inside if clauses, or class instances 
inside the same class body). 

I've stolen a function from DotCompleter plugin 
(getPointOnTextArea()) and read the CompleteWord code for 
inspirations about the popup.

The xml files for the predefined php functions are taken by the 
Quanta libs.


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

>Comment By: Oliver Rutherfurd (orutherfurd)
Date: 2004-02-27 16:55

Message:
Logged In: YES 
user_id=265596

Matteo, the attached jar file is missing a build.xml,
properties file, actions.xml, etc... See here:
http://plugins.jedit.org/building.php for directory layout,
requirements, etc...

Also, could you please provide a "release profile", as
described here: http://plugins.jedit.org/releasing.php


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

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

A change like this would break too much. Too much code exists that
assumes a single namespace.

Just use common sense -- prefix your names with a resonably unique
prefix...

On Mon, 2004-02-23 at 09:49, Anthony Roy wrote:
> I think it would be a good idea to namespace the properties defined in a 
> plugins xxx.props file. The idea would be to prepend the plugin name to 
> the start of any property defined in xxx.props, so that a property 
> aaa.bbb = blah would be saved as the jedit property xxx.aaa.bbb = blah
> 
> Alternatively properties could be enforced to be prepended with the 
> plugin name by a simple checker which rejected the plugin for loading if 
> the properties were not in the correct format.
> 
> An approach like one of these would not be particularly resource 
> consuming in the plugin architecture, but would prevent property 
> conflicts between plugins and the jEdit core or indeed other plugins.
> 
> I may just be clumsy or unlucky, but I have had conflicts with both of 
> my plugins, one between Jazzy and the Aspell spellchecking plugin, where 
> both defined the check-spelling property to name an action, and recently 
> where the LaTeXTools General Option Pane replaces the jEdit Global 
> options General Panel (now fixed in CVS and resubmitted to Plugin 
> Central :-) ).
> 
> Clearer guidelines should be provided in the plugin documentation 
> perhaps, but I don't think that plugins should be allowed to operate 
> outside of their own scope without some work (such as initialization 
> code which explicitly calls jEdit.setProperty(key, value) for example). 
> There should even perhaps be a setQualifiedProperty(key, value) method 
> in the EditPlugin class which ensures that the key is prepended with the 
> name of the plugin, and adds it if not.
> 
> Discuss... :-)
> 
> -- 
> Anthony.
> 
> e: ho...@an...
> w: http://www.ant-roy.co.uk
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
-- 
Slava Pestov

I noticed when adjusting html.xml that if my html file has something 
like this:

<script>
<!--
   (script goes here)
//--></script>

Then syntax hightlighting is wrong after the </script>. If I change the 
html like this:

<script>
<!--
   (script goes here)
//-->
</script>

Then it works correctly.

I'm not an expert on the edit modes, does anyone know how to adjust 
html.xml to work correctly in the first example? I realize that the 
example is bad form, but I'm working with a bunch of html files 
generated by someone else.

Thanks,

Dale


Dale Anson wrote:
> Attached is a patch for the html editing mode. It adds html tag names as 
> keywords. I split out table and form elements in particular so they can 
> be color-coded differently than the other tags, which makes it a lot 
> easier to pick out the form elements embedded in a table with a lot of 
> in-line styles.
> 
> Dale
> 
> 
> ------------------------------------------------------------------------
> 
> --- html.xml	2004-01-29 09:41:00.000000000 -0800
> +++ new_html.xml	2004-02-26 13:51:34.000000000 -0800
> @@ -43,6 +43,8 @@
>  			<BEGIN>&amp;</BEGIN>
>  			<END>;</END>
>  		</SPAN>
> +      
> +      
>  	</RULES>
>  
>  	<!-- ESCAPE is not exactly right but it is needed to correctly
> @@ -59,6 +61,116 @@
>  		</SPAN>
>  
>  		<SEQ TYPE="OPERATOR">=</SEQ>
> + 		<KEYWORDS>
> +         <!-- mostly block elements -->
> +         <KEYWORD1>HTML</KEYWORD1>
> +         <KEYWORD1>HEAD</KEYWORD1>
> +         <KEYWORD1>BODY</KEYWORD1>
> +         <KEYWORD1>FRAMESET</KEYWORD1>
> +         <KEYWORD1>ADDRESS</KEYWORD1>
> +         <KEYWORD1>BLOCKQUOTE</KEYWORD1>
> +         <KEYWORD1>CENTER</KEYWORD1>
> +         <KEYWORD1>DEL</KEYWORD1>
> +         <KEYWORD1>DIV</KEYWORD1>
> +         <KEYWORD1>H1</KEYWORD1>
> +         <KEYWORD1>H2</KEYWORD1>
> +         <KEYWORD1>H3</KEYWORD1>
> +         <KEYWORD1>H4</KEYWORD1>
> +         <KEYWORD1>H5</KEYWORD1>
> +         <KEYWORD1>H6</KEYWORD1>
> +         <KEYWORD1>HR</KEYWORD1>
> +         <KEYWORD1>INS</KEYWORD1>
> +         <KEYWORD1>ISINDEX</KEYWORD1>
> +         <KEYWORD1>NOSCRIPT</KEYWORD1>
> +         <KEYWORD1>P</KEYWORD1>
> +         <KEYWORD1>PRE</KEYWORD1>
> +         <KEYWORD1>DIR</KEYWORD1>
> +         <KEYWORD1>DL</KEYWORD1>
> +         <KEYWORD1>DT</KEYWORD1>
> +         <KEYWORD1>DD</KEYWORD1>
> +         <KEYWORD1>LI</KEYWORD1>
> +         <KEYWORD1>MENU</KEYWORD1>
> +         <KEYWORD1>OL</KEYWORD1>
> +         <KEYWORD1>UL</KEYWORD1>
> +         <KEYWORD1>ABBR</KEYWORD1>
> +         <KEYWORD1>ACRONYM</KEYWORD1>
> +         <KEYWORD1>CITE</KEYWORD1>
> +         <KEYWORD1>CODE</KEYWORD1>
> +         <KEYWORD1>DEL</KEYWORD1>
> +         <KEYWORD1>DFN</KEYWORD1>
> +         <KEYWORD1>EM</KEYWORD1>
> +         <KEYWORD1>INS</KEYWORD1>
> +         <KEYWORD1>KBD</KEYWORD1>
> +         <KEYWORD1>SAMP</KEYWORD1>
> +         <KEYWORD1>STRONG</KEYWORD1>
> +         <KEYWORD1>VAR</KEYWORD1>
> +         <KEYWORD1>B</KEYWORD1>
> +         <KEYWORD1>BIG</KEYWORD1>
> +         <KEYWORD1>I</KEYWORD1>
> +         <KEYWORD1>S</KEYWORD1>
> +         <KEYWORD1>SMALL</KEYWORD1>
> +         <KEYWORD1>STRIKE</KEYWORD1>
> +         <KEYWORD1>TT</KEYWORD1>
> +         <KEYWORD1>U</KEYWORD1>
> +         <KEYWORD1>FRAMESET</KEYWORD1>
> +         <KEYWORD1>FRAME</KEYWORD1>
> +         <KEYWORD1>NOFRAMES</KEYWORD1>
> +         <KEYWORD1>BASE</KEYWORD1>
> +         <KEYWORD1>ISINDEX</KEYWORD1>
> +         <KEYWORD1>LINK</KEYWORD1>
> +         <KEYWORD1>META</KEYWORD1>
> +         <KEYWORD1>SCRIPT</KEYWORD1>
> +         <KEYWORD1>STYLE</KEYWORD1>
> +         <KEYWORD1>TITLE</KEYWORD1>
> +         
> +         <!-- table tags -->
> +         <KEYWORD2>TABLE</KEYWORD2>
> +         <KEYWORD2>CAPTION</KEYWORD2>
> +         <KEYWORD2>COLGROUP</KEYWORD2>
> +         <KEYWORD2>COL</KEYWORD2>
> +         <KEYWORD2>THEAD</KEYWORD2>
> +         <KEYWORD2>TFOOT</KEYWORD2>
> +         <KEYWORD2>TBODY</KEYWORD2>
> +         <KEYWORD2>TR</KEYWORD2>
> +         <KEYWORD2>TD</KEYWORD2>
> +         <KEYWORD2>TH</KEYWORD2>
> +         
> +         
> +         <!-- form tags -->
> +         <KEYWORD3>FORM</KEYWORD3>
> +         <KEYWORD3>BUTTON</KEYWORD3>
> +         <KEYWORD3>FIELDSET</KEYWORD3>
> +         <KEYWORD3>LEGEND</KEYWORD3>
> +         <KEYWORD3>INPUT</KEYWORD3>
> +         <KEYWORD3>LABEL</KEYWORD3>
> +         <KEYWORD3>SELECT</KEYWORD3>
> +         <KEYWORD3>OPTGROUP</KEYWORD3>
> +         <KEYWORD3>OPTION</KEYWORD3>
> +         <KEYWORD3>TEXTAREA</KEYWORD3>
> +         
> +         
> +         <!-- tags that don't fit above -->
> +         <KEYWORD4>A</KEYWORD4>
> +         <KEYWORD4>APPLET</KEYWORD4>
> +         <KEYWORD4>BASEFONT</KEYWORD4>
> +         <KEYWORD4>BDO</KEYWORD4>
> +         <KEYWORD4>BR</KEYWORD4>
> +         <KEYWORD4>FONT</KEYWORD4>
> +         <KEYWORD4>IFRAME</KEYWORD4>
> +         <KEYWORD4>IMG</KEYWORD4>
> +         <KEYWORD4>MAP</KEYWORD4>
> +         <KEYWORD4>AREA</KEYWORD4>
> +         <KEYWORD4>OBJECT</KEYWORD4>
> +         <KEYWORD4>PARAM</KEYWORD4>
> +         <KEYWORD4>Q</KEYWORD4>
> +         <KEYWORD4>SCRIPT</KEYWORD4>
> +         <KEYWORD4>SPAN</KEYWORD4>
> +         <KEYWORD4>SUB</KEYWORD4>
> +         <KEYWORD4>SUP</KEYWORD4>
> +         
> +
> +
> +      </KEYWORDS>
>  	</RULES>
>  
>  	<RULES SET="JAVASCRIPT" DEFAULT="MARKUP" IGNORE_CASE="TRUE">

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

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Nathan Tenney (natet)
>Assigned to: Oliver Rutherfurd (orutherfurd)
Summary: XInsert update for jEdit 4.2

Initial Comment:
Name: XInsert
Version: 1.9
Requirements: Java 1.2, jEdit 4.0.1
Announcement: XInsert updated to fix load problem with
jEdit 4.2
Source code: jEdit CVS plugins/XInsert


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

>Comment By: Oliver Rutherfurd (orutherfurd)
Date: 2004-02-27 09:35

Message:
Logged In: YES 
user_id=265596

Nathan, I updated the plugin for 4.2 dynamic
loading/unloading and fixed a ClassCastException caused by
having macros in the macros directory -- not in directories
below it.  I went ahead and committed the changes, as they
were minor, rather than bothering w/a patch.

Packaged & Uploaded.

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

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

Plugin Central Submission item #902681, was opened at 2004-02-23 08:36
Message generated for change (Settings changed) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=902681&group_id=588

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Anthony Roy (ant-roy)
Assigned to: Oliver Rutherfurd (orutherfurd)
Summary: LaTeXTools 0.5.1 - urgent update!

Initial Comment:
 Name: LaTeXTools
Author: Anthony J. Roy
Version: 0.5.1
Requires: JDK 1.3
jEdit 04.02.06.00
SideKick 0.2
Console 3.7

Announcement: LaTeXTools 0.5.1

Bugfix release:
- changed properties to avoid conflict with jEdit core
option panels.

Source Code: jedit CVS tag: plugin_release_0-5-1

This is an important release and should be rushed
through if possible, since 0.5 causes the jEdit General
Options in the Global Options list to be replaced by
the LaTeXTools General Options panel.

Anthony Roy.

e: ho...@an...
w: http://www.antroy.co.uk

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

Comment By: Anthony Roy (ant-roy)
Date: 2004-02-25 11:25

Message:
Logged In: YES 
user_id=651411

Sure - I had actually spent quite a bit of time doing this,
but it seems that I have put everything a directory too
deep. I'll bring everything up a level before the next
release, and take another look at the build.xml.

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

Comment By: Oliver Rutherfurd (orutherfurd)
Date: 2004-02-24 08:28

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

Anthony, can you please update the directory structure of
this plugin in accordance with
http://plugins.jedit.org/building.php.

build.xml should be in the root directory and ideally would
be as close to the template build file as possible.
It's much quicker and easier if one can build using: ant
-Djedit.install.dir=foo -Dinstall.dir=woo -Ddocbook.xsl=boo
clean dist clean.  Packaging is much more time consuming
(and error-prone) when we've got to tweak the build file
(docs target was commented out) and figure out the nuances
of build files.

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

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

Plugin Central Submission item #892512, was opened at 2004-02-07 14:08
Message generated for change (Settings changed) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=892512&group_id=588

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Brad Mace (bemace)
Assigned to: Oliver Rutherfurd (orutherfurd)
Summary: Outline 1.0.0

Initial Comment:
Outline 1.0.0

Requirements:
* JDK 1.4.1
* jEdit 4.2pre8
* SideKick 0.3
* ErrorList 1.3.1
        

Announcement:
	Initial plugin central release

Source:
	plugins/Outline
	tag: release-1_0_0

Short Description:
	Provides a SideKick structure tree which displays
folds rather than language specific structures.

Long Description:
	Provides a SideKick structure tree which displays
folds rather than language specific structures.


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

Comment By: Oliver Rutherfurd (orutherfurd)
Date: 2004-02-10 08:44

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

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

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

Plugin Central Submission item #893444, was opened at 2004-02-09 10:14
Message generated for change (Settings changed) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=893444&group_id=588

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Anthony Roy (ant-roy)
Assigned to: Oliver Rutherfurd (orutherfurd)
Summary: Jazzy 0.3.0

Initial Comment:
Name: Jazzy
Version Number: 0.3.0
All Requirements:
    * JDK 1.3.1_07
    * jEdit version 04.02.06.00
    * Jazzy 0.5 libraries to be bundled with the plugin:
        - jazzy-core.jar
        - jazzy-swing.jar
        These are located in the CVS repository with
the plugin source.

Announcement: Upgrade to the 4.2 API. Also bundles
latest Jazzy release.

Source Code:  jEdit CVS module plugins/Jazzy tag:
version_0-3-0

Descriptions: 
Short - A pure Java spellchecking plugin based on the 
           SourceForge project Jazzy.

Long  - This plugin allows a spellcheck to be carried out 
           using the Jazzy spellchecking engine, and a
dictionary 
           consisting of a simple word list. An english
dictionary 
           can be downloaded from:
http://sourceforge.net/projects/jazzy/.

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

Comment By: Oliver Rutherfurd (orutherfurd)
Date: 2004-02-09 11:16

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

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

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

Plugin Central Submission item #893178, was opened at 2004-02-08 22:00
Message generated for change (Settings changed) made by orutherfurd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=625093&aid=893178&group_id=588

Category: None
Group: None
>Status: Pending
Priority: 5
Submitted By: Brad Mace (bemace)
Assigned to: Oliver Rutherfurd (orutherfurd)
Summary: CommonControls 0.8.2

Initial Comment:
CommonControls 0.8.2

Requirements:
jdk 1.4.1
jedit 04.02.08.00

Announcement:
CommonControls update

Source:
plugins/CommonControls tag: release-0_8_2


At Slava's request I have moved what was going to be
Widgets into the CommonControls plugin.

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

Comment By: Oliver Rutherfurd (orutherfurd)
Date: 2004-02-10 11:31

Message:
Logged In: YES 
user_id=265596

Packaged & uploaded.

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

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

Plugin Central Submission item #905664, was opened at 2004-02-27 00:16
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=905664&group_id=588

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nathan Tenney (natet)
Assigned to: Nobody/Anonymous (nobody)
Summary: XInsert update for jEdit 4.2

Initial Comment:
Name: XInsert
Version: 1.9
Requirements: Java 1.2, jEdit 4.0.1
Announcement: XInsert updated to fix load problem with
jEdit 4.2
Source code: jEdit CVS plugins/XInsert


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

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