Archive for the ‘RSyntaxTextArea’ Category

RSyntaxTextArea 2.5.3 Released!

Sunday, June 29th, 2014

RSyntaxTextArea 2.5.3 was just released on GitHub!  Here’s what’s new:

RSyntaxTextArea:

  1. Improvements to PHP syntax highlighting.
  2. In HTML and XML, “mark occurrences” should match tag names even when the caret is in an attribute, not just when it is in the tag name itself.
  3. Java syntax highlighting updated for Java 8 classes, interfaces, and enums.
  4. SQL: matching opening/closing parens are now highlighted.
  5. Fixed several bugs.

AutoComplete:

  • Only minor changes to support/stay in sync with RSyntaxTextArea 2.5.3.

RSTAUI:

  • Only minor changes to support/stay in sync with RSyntaxTextArea 2.5.3.

RSTALanguageSupport:

  1. Improvements to CSS code completion.
  2. Improvements to PHP code completion.  Documentation for many functions is now included.
  3. JavaScriptOutlineTree now understands basic JavaScript OO paradigms much better.

SpellChecker:

  • Only minor changes to support/stay in sync with RSyntaxTextArea 2.5.3.

TokenMakerMaker:

  • Added “Recent Files” sub-menu to the File menu.
  • Added an option to install a theme on the RSTA editor when previewing changes to a TokenMaker.
  • Bumped version number in the About dialog to “1.0″ to match that in the documentation.

Enjoy!

 

JavaScript Outline Tree is getting smarter

Sunday, June 8th, 2014

The JavaScriptOutlineTree class is getting smarter in the next release of RSTALanguageSupport.

As previously reported a little while ago, the outline tree has recently been able to recognize JS classes created by defining members on a prototype.  That functionality has just been extended in a couple of ways:  first, defining an entire prototype at once is now handled correctly (e.g. adding all fields to a prototype at once):

Recognizing prototypes

Recognizing prototypes

Next, Object.create() is parsed properly; all property descriptors passed in as the second argument to the method are properly added to the desired prototype:

Recognizing Object.create()

Recognizing Object.create()

Further, as the JS parser is smart enough to figure this stuff out now, you can quickly navigate to these newly-identified class members via Ctrl+Shift+O.  Pretty nice!

Only a couple of new things might get added before the next release – code completion for built-in objects such as Math, Object, JSON, etc.  Beyond that, I’d like to add some form of language support for Angular and possibly jQuery, but we’ll see.  As a large part of the JS language support was written by someone other than myself, who hasn’t been active recently, it might take a little bit of time for me to figure out the best way to add such features in (the JS language support is currently designed to support code completion for server-side scripting as well as browser-based JS work, so things aren’t as simple as they might seem).

RSyntaxTextArea 2.5.2 Released!

Sunday, March 9th, 2014

RSyntaxTexArea 2.5.2 was just released on GitHub!  Here’s what’s new:

RSyntaxTextArea:

  1. Whether or not curly braces denote code blocks is now handled on a language-index level, not per TokenMaker. This means TokenMakers such as HTML, JSP, and PHP can provide auto-indentation and curly brace closing for ‘sub-languages’ such as JSP and CSS.
  2. Java syntax highlighting updated for Java 8 classes, interfaces, and enums.
  3. Added “mark occurrences” support for HTML.
  4. Curly braces can now be automatically closed when editing CSS.
  5. The SearchEngine class now automatically selects the next match after a Replace operation.
  6. Fixed errors when loading/saving Theme XML.
  7. Fixed several bugs.

AutoComplete:

  • Only minor changes to support/stay in sync with RSyntaxTextArea 2.5.2.

RSTAUI:

  • After doing a “replace” operation with the Replace tool bar, the next valid replacement region is selected in the editor.

RSTALanguageSupport:

  1. The JavaScript language support can now use JSHint for its squiggle underlining of errors and warnings. A .jshintrc file can be specified to override the default JSHint behavior.
  2. CSS code completion.
  3. Fixing bug in XML outline tree for XML files with DTDs specified.

The SpellChecker library was not updated; the 2.5.1 release is still the most current, and is compatible with RSTA 2.5.2.  The idea is that the most recent 2.5.x versions of all of the sister libraries are all compatible with one another.

Enjoy!

CSS Code Completion

Tuesday, December 24th, 2013

Code completion for CSS files has been added to RSTALanguageSupport.  Icons were graciously borrowed from Eclipse (as usual).

You get code completion for at-rules and HTML tags for selectors:

at-rules and HTML tags

at-rules and HTML tags

As well as property names:

Property Completions

Property Completions

And for certain properties, you’ll also get code completion for their values:

Value Completions

Value Completions

By default, the completion popup is automatically triggered (after a delay) when typing the “@” character for at-rules, and when typing ‘:’ or a space after a property name.  As always, this is configurable.

Moving forward, short documentation for each CSS property (and values too!) would be awesome.  If anyone has time or motivation and wants to contribute, pull requests or patches are welcome!

RSyntaxTextArea and RText 2.5.1 released!

Wednesday, November 13th, 2013

Both RSyntaxTextArea (and its sister projects) and RText have brand new 2.5.1 releases available on GitHub and SourceForge!  The RSTA updates fixed a couple of bugs that had crept into the library in the 2.5.0 release.  RText (which hasn’t seen an update in a few months) is now using the latest, greatest RSTA libraries, which also means it’s using the slick new search toolbars I blogged about previously.

Check ‘em out!

Search API Updates

Sunday, September 22nd, 2013

The next release of RSyntaxTextArea and RSTAUI will feature some enhancements to the Search API.

Find and Replace operations were always done through the SearchEngine class.  This class contained the following static methods:


   public static boolean find(JTextArea textArea, SearchContext context)
   public static boolean replace(RTextArea textArea, SearchContext context)
   public static int replaceAll(RTextArea textArea, SearchContext context)

The find() and replace() methods returned whether a match was found/replaced, and the replaceAll() method returned the number of replacements performed.

In order to do a “mark all”, you had to call a method on an RTextArea instance:


   public int markAll(String toMark, boolean matchCase, boolean wholeWord, boolean regex)
   public void clearMarkAllHighlights()

In the next release of RSTA, the “mark all” API will be moved into SearchEngine, so that it is a one-stop shop for everything related to search. Further, these methods will return a new SearchResult object, containing more uniform, detailed information on the result of the operation.

The find() and replace() methods will now check context.getMarkAll(), and if it returns true, they will automatically perform a “mark all” operation along with the find/replace requested. This is very useful because often, people want to visually see what other matches are nearby the one actually found and selected.

The search-related components in RSTAUI have been updated as well. Besides the existing Find and Replace dialogs, there are now two new components – FindToolBar and ReplaceToolBar. When wrapped in a CollapsibleSectionPanel, these tool bars can provide a search UI integrated into an application’s main window, as opposed to the standard approach of modal dialogs. This is the trendy new way of doing things. In addition, these components use an animation to “slide” in and out of the UI, breathing a little bit of life into a Swing application.

Below is an example of setting up a window where Ctrl+F and Ctrl+H will bring up a FindToolBar and ReplaceToolBar, respectively:

   JPanel contentPane = new JPanel(new BorderLayout());
   frame.setContentPane(contentPane);
   JMenuBar mb = new JMenuBar();
   frame.setJMenuBar(mb);
   JMenu menu = new JMenu("Search");
   mb.add(menu);
   // Create our search tool bars and tie their search contexts together.
   findToolBar = new FindToolBar(this);
   replaceToolBar = new ReplaceToolBar(this);
   replaceToolBar.setSearchContext(findToolBar.getSearchContext());
   // Add our search tool bars to the "collapsible section panel."
   // Ctrl+F and Ctrl+H will display these tool bars. Use the returned actions to
   // create menu items for our application menu bar.
   CollapsibleSectionPanel csp = new CollapsibleSectionPanel();
   contentPane.add(csp);
   int ctrl = getToolkit().getMenuShortcutKeyMask();
   KeyStroke ks = KeyStroke.getKeyStroke(KeyEvent.VK_F, ctrl);
   Action a = csp.addBottomComponent(ks, findToolBar);
   a.putValue(Action.NAME, "Find...");
   menu.add(new JMenuItem(a));
   ks = KeyStroke.getKeyStroke(KeyEvent.VK_H, ctrl);
   a = csp.addBottomComponent(ks, replaceToolBar);
   a.putValue(Action.NAME, "Replace...");
   menu.add(new JMenuItem(a));

Here’s an example of what the tool bars look like:

 

Find Tool Bar

Find Tool Bar

Replace Tool Bar

Replace Tool Bar

Ctrl+F/Ctrl+H toggles between them, and Escape hides the currently visible one, if any.  If “Mark All” is enabled, all matches are selected in the editor as you type, which is a very nice feature.  The “mark all” event waits for a short time after you stop typing before it fires (defaulting to 200 ms).  That way, it doesn’t perform a mark-all operation for each letter you type if you type really quickly.

Just like the older Find and Replace dialogs, the Find and Replace tool bars will offer code completion for regular expressions:

 

Regex assistance

Regex assistance

This code is already pushed to GitHub; all I have left to do is some more testing.  I also plan on improving the performance of “mark all;” it’s slower than the “mark occurrences” support in RSTA and there’s no reason for that.  And since these new components make it so easy and handy to have “mark all” enabled all the time, I figured I’d go ahead and knock that out sooner rather than later.

RSyntaxTextArea 2.5.0 Released!

Monday, August 26th, 2013

RSyntaxTextArea 2.5.0 was just released on GitHub!  The sister libraries AutoComplete, SpellChecker, RSTAUI were updated as well.  Here’s what’s new:

  • The minimum required JRE for the libraries was bumped up to Java 5 from 1.4.  There was no hard requirement for this from a feature point of view, but it allows us to fix a few issues here and there, and modernize the code base, which is a boon for developers.
  • Improvements in both the painting code and syntax parsing code.
  • Added syntax highlighting and code folding for .htaccess files.
  • Bug fixes in JavaScript and Clojure syntax highlighting.
  • The source repositories were (obviously) moved from the old SVN repositories hosted here on fifesoft.com to GitHub.
  • A few other minor changes.

Check it out and let me know what you think!

RSyntaxTextArea repositories now on GitHub, require Java 5

Sunday, August 11th, 2013

Two big things going on with RSyntaxTextArea!

First, the source for RSTA ia being moved from our personal SVN server to GitHub.  Since GitHub is the place to host open source projects these days, hopefully this new home will provide RSTA with more exposure and accessibility.  AutoComplete, SpellChecker, and the other sister libraries are moving over as well.  I haven’t quite decided yet what will happen to the current SVN server; my current idea is to keep it up and available, but to edit the readme files and Ant scripts to talk about the new location (and not actually build anything in the case of the Ant scripts, to force people to notice!).  But I can’t decide whether it’s better to just remove the repository entirely – that will force users to see it’s no longer there, causing them to go to the site and realize the source is now on Github.  While it’s a little more harsh, it will keep the project from appearing “dead” to people who simply monitor the SVN and see no updates being made.

The second big change is that, starting with the next release, RSyntaxTextArea will require Java 5.  Yes, I’m finally retiring support for Java 1.4.  If you still need to run on such an ancient JVM, you can continue to use 2.0.7 (or even fork it on Github!).  If any huge issues are found I’ll be happy to create a maintenance branch based off 2.0.7 for you Java 1.4 folks, but I seriously doubt that’ll happen.

Migrating to Java 5 doesn’t do much for the library itself, but it does modernize the code base, and fixes a couple of odd issues here and there.  You’ll find “java5″ branches in each RSTA project now; that’s where all the action is.  I’m trying to embrace git’s painless branching and all.  :)  When the work is finally done (should be in a day or two) I’ll merge these branches back into master.

Finally, I’ll be adding all known issues into the GitHub issue tracker and any other bits and pieces left remaining.  As an aside, I’ve found GitHub’s interface to be painless, fast, and intuitive.  Much better than the clunky old SourceForge interface.

.htaccess file support

Sunday, July 14th, 2013

The upcoming release of RSyntaxTextArea will support syntax highlighting and code folding for .htaccess files.  This was just added in SVN commit 814.

htaccess Support

htaccess Support

RSyntaxTextArea and Java 1.4 Support

Sunday, June 23rd, 2013

Does anybody really need Java 1.4 support anymore?  RSTA is one of the few remaining, active Swing libraries that supports this ancient version of Java.  It reached its EOL in 2008 (almost 5 years ago!), and even its extended support ended in February 2013.  Being a syntax highlighting text component, there hasn’t really been anything added to the JDK from Java 5 onward that would benefit it, so I’ve been keeping its minimum JRE version back at 1.4, just to keep it as “compatible” as possible.  However, there are a few drawbacks because of this:

  1. There is one API change in the JDK that occurred between Java 1.4.2 and 1.5 that affects RSTA.  The code in the repository builds cleanly when built with a true 1.4 JDK, but you will receive an error for XmlParser.java when building with Java 5+ (even if you set -source 1.4).  When building RSTA with the included Ant build scripts, you will get a big fat explanation of this spit to stdout, so you know rectify the situation if it happens to you (just add a throws-clause to a single method), but Java novices may not fully understand what’s not working.  Moving the bar up to 1.5 will clean this issue up entirely.
  2. For JavaScript code completion, RSTALanguageSupport has a dependency on Mozilla Rhino, which is developed with Java 5 but offers a 1.4-supporting version, I believe using Retroweaver.  While this is fine and dandy, and everything works, a future version of Rhino may well not include a pre-built 1.4-compliant Rhino jar, and I certainly don’t want to be in the business of building and supporting it myself.  It would be a little nicer if this nuance weren’t there.
  3. One area where the JDK does offer nice new functionality for an editor like RSTA is XML parsing.  We could add schema-based squiggle underline validation to XML files.
  4. It would be a little nice to modernize the code base.

If anyone feels strongly that we should keep releasing pre-built versions of RSTA that run on Java 1.4, please let me know, preferably in the forums.