If you're using YouTrack and Confluence together, you might be interested in this little add-on that helps you integrate these two at some level. The add-on brings two macros: 1. issue which simply inserts a link to any YouTrack issue, and this link reflects the issue state, so you can tell, for example, if the issue is resolved or not by just looking at a page. Here's an example of its syntax: {issue:id=DOC-3202} And this is what it produces: Hovering mouse over this link gives a tooltip with even more details like assignee, number of votes, etc.This macro was inspired by o

Dear friends, For quite a while we have been sharing this blog and other resources for both PhpStorm and WebStorm IDEs. We came to the conclusion it’s time to let these products have their own separate resources. This way our visitors can get the most relevant information on the product they use without any distraction or inconvenience. From this moment this blog is closed. No new comments or posts will be published in this blog. Everything already published will remain available. From now on, please follow the new PhpStorm Blog and/or WebStorm Blog to get the most relevant information for

PhpStorm 6 release is just around the corner! Today we’re publishing a PhpStorm 6 Public Preview build 127.67 with a set of latest fixes. Those who already use our EAP builds - please download the latest build and be sure to report all the bugs in the issue tracker to be sure we are working on fixing it. And if you are still using our stable 5.0.x builds - here is a summary of all improvements and new features we are planning to include in upcoming PhpStorm 6 release: PhpStorm 6 significantly expands a variety of everyday actions available to be performed right from the IDE, e.g. managing

PhpStorm 6 brings a new set of customizable templates for PhpDoc blocks and overridden/implemented method body. Now we can decide what content these parts of code will initially have when they are generated automatically. (more…)

Today we're excited to announce Release Candidate build for WebStorm 6! We're really close to the release, so the focus is stability and performance in all subsystems. However there's another new feature that we decided to put in it: support for HTML5 microdata. The IDE will now assist you with completion for properties according to the schema you're using: There's also one more thing to mention. We've got a couple of complains about the IDE unexpectedly changing matching strings when renaming JavaScript variable of function. We've changed this behavior, now strings are skipped if you tur

Here comes new fresh EAP build #126.309. Visible changes are: Emmet support now works in CSS files. Indeed, it is quite powerful (here's the exact list of what's done so far): Given: Result (after you press Tab): IDE now bundles support for Google Closure Linter tool. Now you've got a really nice tool set to be sure that your code is 100% free of errors, haven't you? :-) File watchers will now show output files (minified JS, CSS, source maps) under the source file node in Project view: Also output files will not be error-inspected by the IDE. There's now a built-in file watcher 

Please meet the new WebStorm 6 EAP build number 126.254. The changes worth mentioning include: The IDE will now highlight your JavaScript code according to the libraries that are configured for the file. This way you can now use libraries not only to filter the completion list, but also to clearly see what your code uses and be sure it won't fail in production as it calls a non-existing method from the library that was never supposed to be part of this project. So, if you suddenly get your code highlighted red, please make sure you've configured libraries correctly at File -> Settings -&

Working with multiple files in the editor is par for the course. The challenge, however, is not to get lost in zillions of editor tabs opened for each file in the editor pane. Luckily, smart tab management and a few navigation techniques go a long way toward helping you find your way around opened files quickly and efficiently. (more…)

This is to announce a new WebStorm 6 EAP biuld 126.159. Let's quickly drive through the changes in this build: 1. HTML structure view has been reworked, and now it's much easier to navigate over complex HTML files. More details will follow soon, let me just show a screenshot of HTML5 outline mode: 2. IDE can now grab the latest version of JSHint right from the Web, so you can always stay up to date with all the JSHint features. Just go to Settings -> JavaScript -> JSHint and choose the version you need or continue with the bundled one. 3. We implemented the long-awaited support for

Sometimes you have several different versions of files or folders related to your project locally, or you’ve just downloaded it from a remote source. In this case it’s crucial to work with the most up-to-date copy. If you need to merge changes and synchronise folders,  then it can become even more complicated, as well as difficult to perform manually without any support. The good news is that you can quickly and conveniently compare and/or synchronize files/folders with guidance and support from your IDE, without any external tools. PhpStorm and other IntelliJ Platform IDEs help you explore d

New WebStorm 6 EAP build 126.86 is available for download. We've fixed troubles with LESS support that some of you may have stepped into using previous build. Also, we've brought a couple of improvements for built-in file watchers for TypeScript, CoffeeScript, SASS and LESS transpilation (nice word, eh?). This will make configuration phase even easier. We'll publish more information on this topic shortly to ensure that you can try this at home :) There are also some fixes regarding JavaScript, TypeScript and Dart languages support, and overall platform improvements. Let me also note that lot

WebStorm 6 EAP build 126.37 is now ready for download. What's inside: Go to class action now brings you to JavaScript (via @constructor) and TypeScript classes: Predefined JavaScript libraries list has been reworked and simplified. You can now set up a default presentation (color, background, effect) for each language element (e.g. keywords, comments, string literals etc.). This way it's now extremely easy to keep consistent highlighting of different languages. Many fixes for Debugger, Live Edit, JavaScript, TypeScript, CoffeeScript, CSS and LESS. For those of you who's interested her