Submitted by Thursday, 24 June, 2004 - 18:34
I have started an effort to formalize the quality assurance methodology of jEdit. If you'de like to help out, surf your way over to the Quality Assurance Overview
Attention: Plugin authors and hackers
Submitted by Wednesday, 4 February, 2004 - 07:56
There have been many plugins submitted to this site, and even a few only mentioned on the mailing lists, that have never been released on Plugin Central. Some are hacked versions of existing plugins, some are completely new. We'd like to encourage all of you to release
your plugins on Plugin Central
so they are more available to the community. Installing and updating plugins through the plugin manager is just plain easier than downloading them here.
We'd also like to see your improvements make it back into the cvs repository
. Slava and Mike will be happy to add anyone to the project who wants to work on a plugin.
If you're hacking an unmaintained plugin (see Plugin Maintainers
), you can take it over, or just add your improvements and do a single release. If you're hacking a maintained plugin, talk to the current maintainer. They're usually happy to accept contributions.
Plugins and 4.1final
Submitted by Monday, 30 December, 2002 - 22:24
First of all, a number of plugins need to be updated for the new icon set; right now they either look out-of-place or icons don't show up at all. This includes AntFarm, Sessions, JBrowse, AntViz, and maybe others.
Also, I would really, really, like to see someone step up to either take over CodeAid and Jane, or start from scratch to write a code completion plugin that actually works.
I would also like to see ProjectViewer and Gruntspud improve to the point where they are usable for day-to-day work.
Making jEdit's feature set more accessible
Submitted by Wednesday, 9 October, 2002 - 18:52
From reading the jEdit 4.1 feature suggestions
article, it seems the majority of suggested features are already in jEdit (wheel mouse scroll, word wrap, saving files in a background thread, window docking, ...). This suggests that users are having a hard time finding out about jEdit's feature set; what can be done to make the learning curve easier?
jEdit development resumes
Submitted by Friday, 2 August, 2002 - 18:35
I have started work on jEdit again. You can find the beginnings of 4.1pre3 in the CVS, although currently the only changes are a few minor tweaks and bug fixes. There will be more changes soon, with an actual 4.1pre3 release before the end of August.
Slava Pestov away until the end of July
Submitted by Sunday, 23 June, 2002 - 06:26
I am leaving New Zealand on the 29th June. I will be in Australia until the 20th July. During this time I will have e-mail access, however I will not be doing any jEdit development. On the 21st July, I am going to Canada. Once I settle in, I will resume jEdit development.
jEdit 4.1 development begins
Submitted by Monday, 27 May, 2002 - 08:10
I have recently begun working on jEdit 4.1. You can see some early work in the CVS repository. Changes so far include improved printing, improved syntax highlighting, various user interface improvements, SOCKS proxy support (for people behind an MS proxy server), and more. You can find a full change log here
New ErrorSource API
Submitted by Tuesday, 27 November, 2001 - 10:49
The changes are as follows:
- The EditBus plugin has been dissolved, and all classes have been moved to the ErrorList plugin. So you must remove any dependencies on "EditBusPlugin" from your plugin's property file.
- All ErrorSource API classes have been moved to the "errorlist" package; so you will need to add "import errorlist.*;" where necessary.
- To register an error source, you must now call:
Modifying plugins for jEdit 4.0
Submitted by Monday, 12 November, 2001 - 07:10
- Under jEdit 3.2.2 and prior versions, the QuickNotepad plugin had a separate class, QuickNotepadDockable, implementing the DockableWindow interface. The class's methods delegated actions to the plugin's top-level visible component, a class derived from JPanel called QuickNotepad. The DockableWindow interface is deprecated in jEdit 4.0, so this class was eliminated. If the top-level component had implemented the DockableWindow interface, it would have been necessary to remove the implements statement and eliminate the getName() and getComponent() methods of that in the plugin class (unless, of course, the plugin itself requires them).