Official stance on CSS3?

Before I start filing youtrack issues regarding non functioning CSS3 properties what is the official take on what is supported and what is not, and when will it be?
I know CSS3 is still fragmented but certain modules are in an advanced state and implemented in most (if not all) browsers. Like for example rgba colors. All curent browsers support that, but it is not supported in phpstorm.

9 comments
Comment actions Permalink

Hello, Peter

Currently, we don't support CSS3 according to its specification. We'll consider a possibility to implement this in PhpStorm 3.0

0
Comment actions Permalink

Well, I'm not saying the whole CSS3 spec should be implemented right away, it is still in 'development' so anything can still change. I am just saying that any part/property/value/type/selector etc. that is already implemented by all browsers should be considered since most of us are using them on a daily basis already.

Which brings me to another point, I just had a look at the roadmap and I notice that the (near) future of phpstorm seems to be aimed not at specs and standards but at apis and frameworks. And these are always a matter of personal choice and can even change based on the project. I don't understand why something like Symphony gets preference over htaccess or SSI or even simple documentation? Not to mantion fine tuning all the features (like code formatting, assitance, remote access, etc.)
Wouldn't it be more prudent and logical to make the base product encompass all standards and specifications and basic "tools" a web designer/developer needs and then (later) add the less standard things (like frameworks) as plugins? That way you avoid a product that becomes bloated and fragmented when it comes to being a standard.

Just asking, I am just curious as to how such decisions are made and priorities are decided upon.

0
Comment actions Permalink

I agree with Peter 100% Unless jetbrains is prepared to support every PHP framework out there. Why even waste the time?

0
Comment actions Permalink

I strongly disagree. For example, netbeans, and eclipse have zf support. I have several zf projects on hich I work time to time. If I have zf project as my main project I suppose I will prefer netbeans over phpstorm. I use phpstorm over 1.5 year and saw netbeans 2-3 times in my life. I think this lack of frameworks support stops many developers to use phpstorm.

I'm personally don't see any sense in CSS3 support in IDE while I must support IE7-8 and Firefox 3.6. I guess this will not change at least next 2 years...

0
Comment actions Permalink

What's stopping you now from using ZF with PHPStorm? I do. I mean what kind of support are you looking for? You already get code-sense and doc's in PHPStorm?

I would prefer Jetbrains to fix the various bugs and refine the product before throwing in soecific framework support.

0
Comment actions Permalink

Please submit your feature ideas to YouTrack and we will consider them for implementation.
As to Css3 support, we handle Css 2.1 + additional syntax / properties of Css3 from the practical experience.
Given that, please create issues for missing but used Css3 stuff.

0
Comment actions Permalink

Very big list of things, the most important are: autocomplete for helpers, controller-view one click naviagation, autocomplete for variable set in the controller in the view.

0
Comment actions Permalink

Gents, please stop arguging - CSS support and PHP framework support doesn't interfere in any way *including* allocation of our development focus.
PHP stuff and JS/HTML/CSS stuff is handled by different people.

0

Please sign in to leave a comment.