[ jEdit-announce ] jEdit 2.6pre3 now available

[Slava P. <sp...@gj...>]

jEdit 2.6pre3 is now available from <http://jedit.sourceforge.net>.
This release adds a new window docking API that will eventually replace
PluginHolder.

+ New Features

- Window docking added to the core. This allows plugins and other windows
  to be 'docked' into views. By default, all dockable windows are shown
  in their own frames. This can be changed in Utilities->Global Options->
  Docking. This obsoletes the PluginHolder plugin.

+ Enhancements

- Previously, buffer closing and search & replace would block the GUI
  until all pending I/O was complete. Now, these commands only do it if
  it is really necessary
  the buffer _being closed_ is currently being loaded or saved
- If the default edit mode is not 'text', *.txt files are now opened in
  text mode anyway
- jEdit now remembers all FTP passwords until it is quit. To force it
  to forget passwords while it is still running, invoke Utilities->Forget
  Remote Passwords
- More VFS code cleanups
- Documentation updates

+ Bug Fixes

- Double-clicking on a directory in the 'save as' dialog box did not have
  the desired effect (since 2.6pre2)
- On some systems, File.list(), for whatever reason, returns files in the
  list, which return false when exists() is called on them. This caused NPE's
  (since 2.6pre2)
- The VFS browser would throw 'VFS session in use' errors after the
  Global Options dialog box was closed (since 2.6pre2)
- The 'Add to Favorites' button in the VFS browser would throw an NPE if the
  tree view was active (since 2.6pre2)
- The FTP VFS now resolves symlinks, so links to directories should no
  longer show up as plain files in the browser
- The DirectoryListSet would reject directories whose names didn't match
  the file name filter, and not check any files within them (since 2.6pre2)
- On some JVMs, IORequest.java would cause VerifyErrors, and as a result,
  buffers could not be loaded or saved (since 2.6pre2)
- Markers would not be loaded properly (since 2.6pre1)

+ API Changes

- Plugins that use PluginHolder to dock themselves in views will need to
  be updated to use the new API
- Plugins that dock themselves in directly (eg, BufferSelector) will need
  to be updated for the new component hierarchy