Posts Tagged ‘highlighting’

Spring 3.1 c-namespace in IntelliJ IDEA 10.5 EAP build 106.561

Friday, April 22nd, 2011

Spring 3.1 “c-namespace” facility is now supported in IntelliJ IDEA 10.5 with code completion, error highlighting, quick fixes and code generation.

Grab the fresh IntelliJ IDEA 10.5 EAP build 106.561, check the release notes and send us your feedback.

Happy Easter Holidays!

New in 10.5: Highlighting of HTML tag tree

Wednesday, April 20th, 2011

Recently we’ve added a new code highlighting feature that should make it easier to work with big and complex HTML files, with deep nested tags structure:

Please note that highlighting is only activated when there is more than one tag with the same name in the hierarchy.

By default, only 6 parent tags are highlighted with 6 different colors. You can change the depth to highlight or completely disable the feature in Settings | Editor | Appearance | Enable HTML tag tree highlighting.

Also you can tweak the colors in Settings | Colors & Fonts | HTML.

This feature is very new and we want your opinions. You are welcome to try it in the latest IntelliJ IDEA 10.5 EAP build and let us know what you think.

Hibernate Criteria API Supported in IntelliJ IDEA X

Tuesday, August 17th, 2010

Since IntelliJ IDEA X property names can be completed and navigated. Unrecognized properties are highlighted by the corresponding inspection.

The screenshot says it all in a visual manner.

Download IntelliJ IDEA X EAP build and try this feature.

Using Scope-Based Code Highlighting

Sunday, May 10th, 2009

One of not so well-known features of IntelliJ IDEA is an ability to differently highlight certain scopes in code editor.

To use it, open the Settings dialog, under IDE Settings expand Editor, then expand Colors & Fonts, and select Scope Based preferences. You will see a list of predefined scopes, and the Edit Scopes button that lets you easily create your own.

Each scope is assigned a distinct color/font scheme — just like different language elements in Java, which makes it easy to distinguish from other code in the editor.

In the following example, it is used to quickly differentiate between real testing code and JUnit Classes (pattern: lib:org.junit..*):



Other use cases include highlighting of, for example, third-party framework code, distinguishing normal code from assertions, etc.

Global unused declaration inspection

Monday, April 27th, 2009

Thanks to improvements in the internal indexes behind the Intellij IDEA code insight engine, Maia will be able to instantly highlight some java classes, methods and fields which are unused across the entire project.

To use the feature, enable the Unused declarations inspection.

unused members

Of course, all sorts of JEE @Inject annotations, test code entry points
and other implicit dependencies configured in the Unused declarations inspection
are deeply respected.