Radical is a GUI builder that can work as a jEdit plugin: http://radical.sourceforge.net/
Project author is (or was) Richard S. Hall. Project development stopped a while ago, and I'm trying to revive and modernize it now.
The version provided here works (to some extent) within jEdit. You can generate Java source code from the GUIs you create. Feel free to try it and comment on it. Please read the usage instructions provided on the web page; some learning is required in order to use the tool, but it's a great tool in my opinion. The main thing I'd like to do is use an XML persistence model for the forms (possibly an existing open source XML model like SwingML) instead of the binary format currently used.
The jar file attached here is built against the latest development version of jEdit trunk, 10708. But I assume it can work with older versions too as the plugin itself is quite old.
Hi, I have been having an issue as of late where Jedit will print out in 1/4th scale. I have gone though all the options I can see and have found nothing which would cause the scaling. No other app is doing this.
I found the fixed number of token types in jEdit very restrictive and unpleasant. When I have some combined code (HTML + PHP + evt. JavaScript + CSS), jEdit colors everything in the similar colors. But having blocks written in different language looking different would be so nice...
I studied jEdit's highlighting definition syntax and figured out that this is not limited by the highlighting system, but by the number of token types.
I've tried jEdit long time ago, then it was quite user unfriendly, crashing and run slowly on my then computer. Now I've found that with plugins, it has all features I look for to switch from my favorite but old editor, HomeSite (which's developement has already ended), EXCEPT for the genial syntax coloring of HomeSite... I will put a screenshot at http://ondra.zizka.cz/temp/HomeSite_screenshot.png . (Intentionally synthetized mix of all languages together, what is bad practice).
So, my feature request is:
As far as the "parsing" system is capable of the feature I ask for, and even the mode files would not have to be rewritten, I guess this is only a matter of the following:
Let's not have fixed set of token types; instead, let's track all token types of each mode and let it be configurable similarly to shortcuts:
1) Separate color configuration for each mode, and
2) Global default color config for certain token types (comment, keyword1, operator), which would be applied if the specific mode setting would be "use default for this token type".
Is this in plan? Or could be? Was it already proposed? I didn't find.
Any response and opinions welcome.
in some IDEs and editors, project management is handled so the files comes to separated pane, as you can see at this screenshot of HomeSite:
http://ondra.zizka.cz/temp/HomeSite_screenshot.png (if not there yet, I'm still looking for the appropriate file to highlight
How about having an optional possibility to show it that way?
In the feature requests forum it was said that feature requests are better posted to the tracker on sf.net.
So I think the forum should close and be replaced with a link to the tracker. Respectively the advice "Please do not submit bug reports to the forums ..." should be expanded for feature requests.
I've installed the Xinsert plugin, and I can modify its options, all the dependencies are installed, everything seems to be right, but its functionality seems to be totally missing. When selecting it on the plugins menu bar, its just 1 entry and it does nothing. Any help would be appreciated.
This editor mode adds syntax highlighting for DokuWiki page editing. The file extensions ".doku", ".dokuwiki", and ".wiki" are used for this mode. HTML mode is imported into this mode to support HTML embedded in the target document.
Just put this together, as my site is running a series of articles on customizing jEdit for use as the preferred editor on OS X. To install: Close jEdit (otherwise, the icons won't change until the next time you launch it), and, if you're using OS X, chances are you will need to "Authenticate" when you place this jar file into your Java home directory (i.e., /Library/Java/Home/lib/ext on plain-vanilla OS X). This means you must type your administrative account's password before OS X will let you place the file in the system folder.
Hope you enjoy it! And please, stop by the site and let me know if you do!
In case you're not happy with the standard icon set, I've uploaded a new icon pack to the Icons and Images section which should give you a more natural looking OS X app. The pack (and instructions for making jEdit look and feel as much like a native OS X app as possible) are also available at my Web site. (Just want to get as many Mac switchers as possible using this great editor!)
Hi all,
Is it possible to write a macro that can return the xpath of the element or attribute the cursor is located at?
For example, given the following xml document, and assuming the cursor is located on the Target element, the macro would return the string: /Links/Link/Target
/htdocs/images/coffee_cup.jpg
I can not find this functionality in the XML plugin or elsewhere.
Possible?
Thanks,
Paul
As soon as you try to type the ':' the whole line will shift over to the
left.
First it has to be saved as a .java file, if it isn't saved as anything
it'll happily work correctly. So create a simple, valid, .java file
and try to add the above lines to it. I have my jEdit set to not use spaces for tabs.
And you have to use tab(s) at the start of the lines.
As soon as you type the ':' The whole line will indent to the left.
Now delete the System.out.println() line, and this time type it
again, but skip typing the ':' and finish the rest of the line, then
go back and add the ':', it will work fine and won't indent the line.
How crazy is that?
I'm looking at the code, and trying some things, but it's still hard to
track down.. It doesn't seem to be a key translation issue, although
it does say:
One feature that I thought would be useful is to have an Opacity controlled "window" plugin.
The plugin would only be useful when docked into one of the defaut positions. However once docked it would have options to control a level of transparency; allowing you to see your desktop of whatever operating system your using. In my case, I like to run PuTTY at the same time as jEdit for running PHP scripts. What I would like to do with this transparency window is to be able to control the PuTTY shell/window through the "window" plugin without minimizing jEdit.
Basically like punching a hole through the jEdit program. Because desktop control would stay as is depending on the operating system and jEdit wouldn't have to be minimized or render any desktop applications specifically. The only thing jEdit would do is provide a hole to see through to your desktop then you could run and use desktop applications normally(the applications would be external to jEdit so if you minimized jEdit you would still be able to use the applications as you would normally).
I don't think this is possible yet, but it would be a nice feature in my opinion.
Although, last I remember Java was still working on a way to control desktop applications using Java, I'm not sure if this has progressed or not...
Anyway, its just a random idea I had. Comments are welcome.
...there's an active jEdit community, but this forum gives the impression discussion is slow/dead. It's also somewhat unfriendly to newcomers as a fair number of threads never get a response.
Hi
I'm using Debian sidux and Java 1.5 which is installed under /usr/bin/java.
I've changed the JAVA_HOME and PATH variable as required.
Nevertheless I'm getting the following error message when trying to start Jedit from a console with typing jedit &:
GC Warning: Out of Memory! Returning NIL!
GC Warning: Out of Memory! Returning NIL!
Exception in thread "main" java.lang.OutOfMemoryError
<>
I've 2.5Gb Mem installed.
What am I doing wrong?
JJ
This version of the Tags plugin has a few enhancements and fixes:
In case of tag collisions, the tags found can be displayed in a dockable window instead of a popup. The 'Tag List' dockable can be opened from the plugin menu and docked in one of the 4 docking positions (or float) like any other jEdit dockable. When the dockable is open, tag collisions will be displayed in the dockable instead of the popup.
The Tag List dockable allows quick filtering by tag attributes (when present in the tag files). This allows you to quick reach the tag you're interested in when there are many tags with the same name, which is common in object oriented languages. The "Filter" menu at the top left of the dockable lets you filter by attribute values.
A new option pane - Actions - was added, allowing you to create custom "follow tag" actions which resolve tag collisions by apply a list of filters, each keeping only those tags having a specific attribute value. This way, you can create an action like "Follow function definition" (which would follow tags whose "kind" attribute is "function" or "method") and another action like "Follow function declaration" (which would follow tags whose "kind" attribute is "prototype", or "function" if there are no tags with a "prototype" kind).
A new option is available in the General option pane, to use line numbers for following tags (when specified in the tag files). This is useful for object oriented languages, where the same tag can be defined multiple times in the same file, each time under a different class, with the exact same signature. It is also useful for differentiating between function declarations and definitions.
Fixed the display of function signatures (when specified in the tag files) in the tag collision list.
I can't get the XML parser to work with jEdit 4.2 final on a new Windows installation. Otherwise, jEdit runs fine.
When I try to use the plugin with an HTML file, I'm told that xml.parser.HTMLParserImpl didn't load because the class xml/parser/XmlParser wasn't found. Seems like those slashes should've been dots. The stack trace is at the end of the message.
I also get an error message, at the same time, that org.apache.xerces.jaxp.SAXParserFactoryImpl wasn't found.
After this, I have to use the Plugin manager to unload the XML plugin before I can type greater-than characters into any buffer that the XML plugin normally works with. Also, none of the functionality of the plugin is available.
Any ideas on how to fix it?
The stack:
java.lang.NoClassDefFoundError: A class required by class: xml.parser.HTMLParserImpl could not be loaded:
java.lang.NoClassDefFoundError: xml/parser/XmlParser
at bsh.BshClassManager.noClassDefFound(BshClassManager.java:552)
at bsh.BshClassManager.plainClassForName(BshClassManager.java:241)
at bsh.BshClassManager.classForName(BshClassManager.java:170)
at bsh.NameSpace.classForName(NameSpace.java:1265)
at bsh.NameSpace.getClassImpl(NameSpace.java:1165)
at bsh.NameSpace.getClass(NameSpace.java:1106)
at bsh.Name.consumeNextObjectField(Name.java:301)
at bsh.Name.toObject(Name.java:202)
at bsh.BSHAmbiguousName.toObject(BSHAmbiguousName.java:59)
at bsh.BSHAllocationExpression.objectAllocation(BSHAllocationExpression.java:86)
at bsh.BSHAllocationExpression.eval(BSHAllocationExpression.java:62)
at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
at bsh.Interpreter.eval(Interpreter.java:641)
at bsh.Interpreter.eval(Interpreter.java:731)
at bsh.Interpreter.eval(Interpreter.java:720)
at org.gjt.sp.jedit.BeanShell._eval(BeanShell.java:446)
at org.gjt.sp.jedit.BeanShell.eval(BeanShell.java:410)
at org.gjt.sp.jedit.ServiceManager$Descriptor.getInstance(ServiceManager.java:321)
at org.gjt.sp.jedit.ServiceManager.getService(ServiceManager.java:264)
at sidekick.SideKickPlugin.getParser(SideKickPlugin.java:142)
at sidekick.SideKickPlugin.getParserForBuffer(SideKickPlugin.java:167)
at sidekick.SideKick.setParser(SideKick.java:131)
at sidekick.SideKick.handleMessage(SideKick.java:155)
at org.gjt.sp.jedit.EditBus.send(EditBus.java:148)
at org.gjt.sp.jedit.jEdit.addPluginJAR(jEdit.java:1034)
at org.gjt.sp.jedit.pluginmgr.ManagePanel$PluginTableModel.loadPluginJAR(ManagePanel.java:376)
at org.gjt.sp.jedit.pluginmgr.ManagePanel$PluginTableModel.setValueAt(ManagePanel.java:298)
at javax.swing.JTable.setValueAt(JTable.java:2662)
at javax.swing.JTable.editingStopped(JTable.java:4661)
at javax.swing.AbstractCellEditor.fireEditingStopped(AbstractCellEditor.java:125)
at javax.swing.DefaultCellEditor$EditorDelegate.stopCellEditing(DefaultCellEditor.java:330)
at javax.swing.DefaultCellEditor.stopCellEditing(DefaultCellEditor.java:215)
at javax.swing.DefaultCellEditor$EditorDelegate.actionPerformed(DefaultCellEditor.java:347)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:291)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6038)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5803)
at java.awt.Container.processEvent(Container.java:2058)
at java.awt.Component.dispatchEventImpl(Component.java:4410)
at java.awt.Container.dispatchEventImpl(Container.java:2116)
at java.awt.Component.dispatchEvent(Component.java:4240)
at javax.swing.plaf.basic.BasicTableUI$Handler.repostEvent(BasicTableUI.java:924)
at javax.swing.plaf.basic.BasicTableUI$Handler.mouseReleased(BasicTableUI.java:1138)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:273)
at java.awt.Component.processMouseEvent(Component.java:6038)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
at java.awt.Component.processEvent(Component.java:5803)
at java.awt.Container.processEvent(Container.java:2058)
at java.awt.Component.dispatchEventImpl(Component.java:4410)
at java.awt.Container.dispatchEventImpl(Container.java:2116)
at java.awt.Component.dispatchEvent(Component.java:4240)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
at java.awt.Container.dispatchEventImpl(Container.java:2102)
at java.awt.Window.dispatchEventImpl(Window.java:2429)
at java.awt.Component.dispatchEvent(Component.java:4240)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
I am using a program called MUP, which compiles music graphics from text files I have been editing in JEdit. There are currently MUP syntax highlighting files for VIM, EMACS and KATE. I'm wondering if there is any way to convert any of these files into a mode file that JEdit can use. Or if there is a good tutorial out there on the way in which these type of syntax files are set up. It's obviously a problem that has been addressed by a number of programs in a variety of ways, but it's pretty much greek to me.
Also, if there is an intro to console tutorial somewhere, I'd like to check it out. The MUP compiler runs from the command line, so I'm thinking it should be possible to get it to compile from the console in JEDIT, but I'm not at all command-line savvy.... Ideally, I'd like to just compile from a key-command.
