For the first time in over 5 years a major release will be made to jEdit! Alan Ezust has now committed a change that makes the next release version 4.3.0. With a new visual look, better platform support, many more features and much improved performance I can safely say that it's a great release and much welcomed!
When I discovered jEdit back in 2002/2003 I was happy to see that there was finally an editor that met all my weird needs and supported all the platforms I was using. I felt that my search for an editor was over… Continue reading jEdit makes major release for first time in 5 years
After switching to Java 6 I encountered a couple of problems using the Mac OS X plugin for jEdit. After waiting a couple of months to get annoyed with the missing mac integration I finally got my act together and re-coded the plugin to support the API changes.
I've managed to get most of the functionality you would expect from a regular mac program working and have now decided to release an alpha version for any testers that might want to get their hands dirty
Here's the changelog and features:
- Initial release
- Support for drag and drop onto the dock icon
- Support for Open With for files that are associated with jEdit
- Application menu integration
- "Preferences" will open Global Preferences
- "About jEdit" will open the Help -> About jEdit… dialog
- CMD-click in titlebar now displays the current buffer path in a drop down. Clicking on a folder will reveal that folder in the finder.
- The red close button now indicates the entire view's modification status. This way it will be consistent with the "save modified buffers?" dialog.
Kris (the original author of the mac plugin) is not completely without credit on this one since I used his plugin as a reference of what needed to be done.
Please give your comments
The following image (first one) is my proposal to a new splash screen for jEdit. The image would, if accepted, replace the classic one (second one) in jEdit and should reflect the default icon and the general feel of the editor.
– Second suggestion
Update: The second splash screen (and a new about screen based on the same look) has been committed to SVN and will be available in jEdit 4.3pre15.
– First suggestion
– Classic/current splash screen
Since this is only a proposal there may be a lot of changes before any replacements are made. The layout and the elements of the new splash was based on the classic splash since current users shouldn't feel alienated by it.
Apple recently released Java 6 SE through a Java update. With the release of Java 6 Mac users can now enjoy better OS X integration besides the many other improvements in Java 6.
Using Java 6 as the default JVM has implications with a standard jEdit installation on Mac. But the solution is simple…
Being a jEdit user I was eager to try out the new JVM version to see if there were any general improvements.
Since Mac users has gone long without proper OS integration, one jEdit developer (Kris Kopicki) decided to fix this with a Mac OS X plugin that included many small improvements.
With the new update Apple has completely removed the cocoa API (packages in com.apple.cocoa). The result: jEdit will fail to start with Java 6 SE.
jEdit will simply "bounce" once and then quit. This is caused by a fatal exception during startup.
The fix is simple: Remove the Mac OS X plugin.
With the improved cocoa/mac support many of the features in the plugin are unncessesary. Key-mappings are improved to use the CMD-buttons in all textareas and the menubar is now moved to the actual Mac menubar.
How to remove the plugin:
- Right click/CTRL+click the jEdit application icon
- Choose "Show Package Contents"
- Go to the Contents/Java/jars folder
- Delete the MacOS.jar file (you may need to authenticate to do this)
Launching jEdit with Java 6 SE should now be possible. Alternatively to setting Java 6 SE as your standard JVM you can set the Contents/Info.plist file property: "Root/Java/JVMVersion" to "1.6+" instead of "1.5+". Either way should work.
Another blogpost about jEdit – this time it's the main application icon.
I've modified the new Tangofied jEdit icon so it's more atune to the Tango look but also somewhat like other OS X icons.
This is a draft of the final icon. The final icon will have modified shadows.
Update: The icon is now available with correct shadows for Mac OS X
jEdit, a popular cross-platform java-based editor, has for long been using an icon theme without any appeal to common sense or visual liking. About a year ago I slowly started working on a patch that could help us change this and give jEdit the visual feel or a professional and well-working tool that newcomers can trust to work as expected.
During the time I've been using and spreading the use of jEdit I've noticed that people tend to initially distrust jEdit since it doesn't offer an interface they can relate to.
jEdit offers many features and has a hard time offering them to the user in a familiar way and even more difficult to make them visually appealing.
Anyhow – a year ago or so I came across the Tango Desktop Project and started integrating it into jEdit. The patch was recently merged into jEdit's trunk version and will be available in the next development release, jEdit 4.3pre14.
People have responded positively and those who became more familar with the classic icons has also given the possibility choose the "classic" icon set in the "Appearance" options-section:
Alan Ezust invited me to become a developer on jEdit with focus on any bugs related to the icon patch and perhaps other issues as well. After accepting I am now looking for small ways to improve the general feel of the editor.
If possible I will also look into getting better Mac OS X support since I use an iMac at work.
jEdit starts a "jedit server" that loads your settings, environment and basicly loads everything but the GUI.
This process is what slows it down, but there are several things you can do to speed up the process:
- Upgrade to Java 1.7 (beta). I find it rock stable, but you might not.
- On Linux, you may enable OpenGL rendering by passing the following arguments:
java -Dsun.java2d.opengl=True -jar jedit.jar
- Keep the number of plugins low. Don't install too many auto-complete plugins such as DotComplete. It takes time to load the language-dictionaries in these plugins.
Last but not least: to have the jedit "server" running as a daemon in the background seriously decreases startup-time!
However, it comes with a catch: Some plugins still require you to restart jedit in order to use them. 4.2 includes a new plugin-API that allows dynamic loading, so with time this isn't an issue. Also: certain setting-changes require you to restart jedit.
Restarting jedit isn't just closing the window. You need to kill the jedit-server process, but it's just labeled "java"/"javaw" in most task-manager tools on both Linux and Windows. Just kill those you can find, but be warned that you may kill other java programs if you get the wrong process.
Run this command to start the server-daemon:
java -jar jedit.jar -nogui -background