And again, the “ideal IDE for PHP” from JetBrains ^) In the time that has elapsed since the previous build , we managed to acquire an official website , visit ZendCon'09 and finally get to the promised performance optimization. There was time for a few new features. While the build is swinging, look under the cat - besides the usual details there will be a couple of words about ZendCon and about the unique functions of the platform / WI.

ZendCon'09

Before the conference, there were tutorials - the opening of the PHP session on IBM I5 was for me. IBM teamed up with Zend to bring PHP to mainframes . If you leave aside the i5 ecosystem, then for everyone else this can also have significant consequences, especially if IBM helps develop the core of the language. In 5.3, some optimizations have already appeared, but judging by other more “adult” technologies, the main work is still to come.
')
Keynout (and most of the sessions) were very vigorous and optimistic - this year PHP 5.3 was released, a new ZendStudio appeared (and 7.1 was specifically released for the conference), the whole stack and the Zend toolkit are being improved, in general, both the language and the platform and the community are moving go ahead :)

During lunchtime and while the main people were in the sessions, we talked a lot to Zend employees - and even impressed some ZendStudio developers with our technologies. In turn, we were interested in hearing about how they develop the Eclipse platform and help coordinate the efforts of the Eclipse Foundation. Still, JetBrains is a fairly small company :) From engineering things it was interesting to hear about working on the language core, as well as automatic profiling (especially from the point of view of a java-web developer with serious experience)

What's new in this build

Impressed by talking to users at ZendCon, we started optimizing. We used such heavyweights as ShugarCRM and Magento as “stress tests” (we wanted to try out Bitrix, but did not find an open source version). Literally the first profiling sessions showed that type inference produced too much garbage in memory, and it could lead to looping (and freezing) - now these problems have been fixed. I would like to say at once that this is only the initial optimization and we plan to seriously pursue this further. * Very * I want to hear feedback from all who upgrade. If you have specific problems - write in any way. I personally process all feedback.

New features:

• improved PHPDOC generation
• navigation / search for uses for global variables
• recognizing class members based on name for those cases where type inference is not possible
• SFTP support
• autocompletion after the new keyword
• namespaces are displayed in the file structure tree
• quicfix (Alt-Enter) to define unknown variables with var

Many bug fixes, details in the blog and tracker

Unfortunately, there are known problems.

• The most serious is degradation: multi-line literals in this assembly are incorrectly highlighted as containing the WI-494 error
• Several namespace XXX declarations; (with ";") in one file will be mistakenly recognized as embedded WI-497
• renaming a variable removes the $ sign from the WI-500 name

We will try to release the update as soon as possible. Wait for bug fixes, optimization and of course new features :)

Something about the unobvious possibilities of WI

The release is coming and we started to collect all the information about the functions of WebIDE in one place . Even if you are already familiar with the editor, I recommend at least viewing the list. And here I will talk about a couple of very useful but not quite obvious features. So, if your PHP project is used to generate XML, JS, CSS, SQL or some other language supported by WebIDE, you can work comfortably using the following functions:

"External" language for PHP

For each file or folder, you can set “external” in relation to PHP language instead of default HTML via the Settings | Template Data Languages ​​panel. This setting is stored in the project file.

"Internal" language for string literals in PHP

Inside the literal, press Alt-Enter and select “Inject Langugage” and then the desired language. Not yet remembered. In the future, it will be possible to specify that * for example * the first string parameter of the query () function is SQL (and choose a dialect)

For both cases, full language support will be included - including compl and refecting. Using these features you can get full support for any combination of languages%)



At this point I finish and wait for any questions and suggestions :)