PhpStorm & WebStorm 2.0 EAP build 103.8

PhpStorm & WebStorm 2.0 EAP build 103.8 is available. Transition to odd branch number signifies that the project has entered its final stage – basically we’ll stop throwing in new and experimental stuff and will focus on bugfixing, usability and performance.

Anyway, albeit important bugfixes in all areas, the notable changes are:

  • PHP Undefined variable got a new engine with compete data flow analysis. After some obvious bugs on our side were fixed you should get much better results than with old engine – about 2x less false positives (stats gathered by analyzing several popular OS projects)
  • PHP debugger got options to sort variables in view and skip selected files (Check out Settings | PHP | Debug | Skipped paths for configuring latter)
  • Cross-Browser bookmarklets for both Zend Debugger and xDebug are available. Get them from jetbrains.com/phpstorm/marklets – and do not hesitate with feedback and check back for updates
  • Deployment finally got “Warn when uploading over newer file [No / Compare timestamp & size / Compare content]” option, see Settings | Deployment | Options
  • Inspection profiles management is enabled, including sharing and exporting inspection profiles. See Settings | Inspection profiles
  • Editor gutter menu is now fully customizable under Settings | Menus and Toolbars | Editor gutter menu

Complete changelog
Please note that ALL of this is work in progress and will undergo series of both technical and cosmetic changes.

Download PhpStorm & WebStorm 2.0 EAP build 103.8 for your platform from project EAP page. No patch-update is available for this build.

Develop with pleasure!
-JetBrains Web IDE Team

This blog is permanently closed.

For up-to-date information please follow to corresponding WebStorm blog or PhpStorm blog.

 
This entry was posted in Early Access Preview, PhpStorm, WebStorm and tagged , . Bookmark the permalink.

12 Responses to PhpStorm & WebStorm 2.0 EAP build 103.8

  1. erbione says:

    “we’ll stop throwing in new and experimental stuff and will focus on bugfixing, usability and performance.”

    this is good news, please check editing CSS file with more than 7000 lines, working with huge files is dramatical.

  2. Urkman says:

    @erbione:
    Perhaps you should split the file for development and join them in deployment…

    Urkman

  3. Rafi says:

    Agree with @Urkman. There’s no valid excuse for working on a 7000 lines css :)

  4. erbione says:

    ahhh so this is the way to work with large files, great ! So no need to improve performance…

  5. teejay says:

    Same for big js files, for instance the debug_all version of ext js. has around 70000 lines. Pretty much impossible to look something up there.

    Dont agree with rafi and urkman, css on dev side should be written as clean as possible. some people tend to write lots of comments, which is a good thing one hand, but a bad thing regarding the locs.Once u deploy u should try to bring down the length of your css.

    We once outsourced our cutting, and what we got back was a enourmous css file with far more than 3000 locs and than u have to live with it if u dont want rewrite everything. So a good css editor should handle that!

  6. Rafi says:

    @teejay: when you deploy you’re supposed to build a compressed and clean version of your css/js.

    @erbione: try to disable inspections. It might help in the meantime.

  7. Максим says:

    Ребята, когда вы сделает чтобы интерфейс так сильно не тормозил?

    Выпадающие меню, экран сеттингов – все это нереально медленно работает, машина amd phenom 4x II, 6gb ram…

  8. Andriy Bazanov says:

    @Максим
    Когда Вы настроете/почините свой компютер? Машине почти 4 года — полет нормальный: AMD Athlon 64 x2 3800+ 2.01GHz, 2GB RAM, Win XP

  9. teejay says:

    @rafi I was talking about that :). Yes the deploy process should take care of minify, compression or what so ever, but in dev mode u should not constrain yourself to a editor. dont get me wrong. I am a huge fan of phpstorm and i think there is nothing better out there.

  10. Urkman says:

    @teejay:
    To work with extJs in a development environment, take a look at this: http://www.sencha.com/forum/showthread.php?64920-Updated-for-3.x-Scripts-to-include-individual-ExtJS-source-files

    For me, there is never a need for files larger than 2000 Lines in a project. If we hit that mark, we redesign this parts of the application and split those files

    Urkman

  11. Jim says:

    PHP debugger got options to sort variables in view and skip selected files (Check out Settings | PHP | Debug | Skipped paths for configuring latter)

    This does not seem to be working. I have places sever files into this list with no apparent effect.

  12. Nikolay Matveev says:

    @Jim
    Please create an issue for that – http://youtrack.jetbrains.net/issues/WI#newissue=yes
    Describe there your expectations about behavior and actual behavior.
    Thank you for report!

Comments are closed.