Archive for the ‘RSyntaxTextArea’ Category

RSyntaxTextArea 2.5.7 Released!

Wednesday, June 24th, 2015

RSyntaxTextArea and all of its sister projects have a 2.5.7 release onGitHub and Maven!  These releases fix up some issues found in the latest 2.5.* releases, and made improvements to the Sonatype integration, as well as CI and unit test coverage.  So it was mostly an organizational release, and to “officially” ship a few fixes and features that had made it in the past few months.  Check it out!

CI builds and coverage reports for RSyntaxTextArea

Sunday, February 15th, 2015

In an effort to encourage the writing of unit tests for RSTA, I’ve added CI builds and coverage reports.  You can see the status of these things in the RSTA README.md file.  Yes, the code coverage is terrible – that’s why I’m doing this!  Hopefully a little public shaming will spur some improvement in this area.

The CI is done through Travis-CI, and the actual coverage reports are generated by Jacoco and hosted on coveralls.io, but the yucky details of all this are hidden by Gradle and an awesome gradle plugin.

All of this is currently only set up for the main RSyntaxTextArea project.  If everything works out swimmingly I may enable it for AutoComplete and other projects in the future as well.

SNAPSHOT artifacts are now available

Friday, January 2nd, 2015

Happy New Year!

SNAPSHOT artifacts are now available for both RSyntaxTextArea and RText, thanks to Sonatype.  This will provide folks with an easy way to try out new versions of these libraries before they are “officially” available.

To use the SNAPSHOTs, you’ll first have to reference the Sonatype snapshot repository.  This can be done in a Gradle build script like so:

repositories {
   mavenCentral()
   maven { // Snapshot builds of RSTA artifacts
      url 'https://oss.sonatype.org/content/repositories/snapshots'
   }
}

Then you can just declare your dependencies as usual.  It did seem like I had to be explicit about my desire for 2.6.0-SNAPSHOT, otherwise Gradle/Maven would still fetch the 2.5.6 release artifact:

dependencies {
   compile 'com.fifesoft.rtext:fife.common:2.6.0-SNAPSHOT', 'com.fifesoft:rsyntaxtextarea:2.6.0-SNAPSHOT'
}

Enjoy!

RSyntaxTextArea 2.5.6 Now Available

Wednesday, December 24th, 2014

RSyntaxTextArea and RSTALanguageSupport have a 2.5.6 release on GitHub and Maven!  These releases fix up some issues found in the recent 2.5.4 releases.  They are compatible with the 2.5.4 releases of AutoComplete, RSTAUI and SpellChecker.  RSyntaxTextArea in particular is worth upgrading if your application runs on OS X, because it brings a big performance improvement with rendering tokens with background colors specified.

Moving forward, I hope to more strictly follow semantic versioning, but I give no promises.  But the goal is to no longer tie myself to synchronous releases of all of the RSTA sister projects at once.  All of 2.5.x, for example, should be obviously compatible with one another, and indeed, 2.x should as well.  We’ll see how that goes moving forward.

RSyntaxTextArea 2.5.4 Now Available

Wednesday, November 26th, 2014

RSyntaxTextArea 2.5.4 (and all of its sister projects) are now available on GitHub, Maven and SourceForge!  The biggest change for all projects is the migration from Ant to Gradle for builds.  The primary motivation for this was to make it easier to create artifacts to put into Maven Central, as well as to tinker with something new.  Thus, this is the first release where everything is available in Maven on day 1!  Moving forward, artifacts in Maven will be a standard part of the RSTA release process.

But besides Maven integration, some other goodies were added too, such as syntax highlighting and code folding for Dart and D, as well as simple code completion for XML files.  Check it out!

Code Completion in XML

Friday, October 10th, 2014

I’ve been really, really lazy with adding code completion via DTDs and/or schemas for XML in RSTALanguageSupport, so in the meantime I decoded to add a simpler element/attribute completion scheme.

If you grab the latest from Git, RSTALanguageSupport’s XML support will now offer code completion suggestions for XML element and attribute names:

XML Element Completion

XML Element Completion

How does it decide what to suggest?

For element names, it scans the editor’s contents for any other elements that start with the prefix you’ve typed so far.  For attributes, it scans for other places where you’ve completed an element of the type you’re adding an attribute for; it then suggests any attributes you’ve used for that element elsewhere in the file (and haven’t currently used in the current element):

XML Attribute Completion

XML Attribute Completion

This kind of completion support is pretty handy when you’re editing a larger document, and know you’ve done “the right thing” elsewhere in the file, but cannot recall what it is offhand.  Just let RSTA tell you what to type.  :)

 

D support added to RSyntaxTextArea

Saturday, September 13th, 2014

RSyntaxTextArea now supports syntax highlighting and code folding for D.  Nestable comments are handled properly.  The screenshot below shows some of D’s unique syntax features:

D syntax highlighting

D syntax highlighting

Dart Support added to RSyntaxTextArea

Monday, September 1st, 2014

Syntax highlighting and code folding has just been added for Dart.  Dart aficionados, clone the RSTA repo and let me know if I’ve missed anything with the highlighting!

Dart Support

Dart Support

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).