Something that would be really nice to see in a future version of JustCode is support for CSS. (And HTML, for that matter). With the size of Web Sites now, managing CSS can become a real headache, and Visual Studio offers very little support for this beyond standard HTML pages. If you nest any pages (Master Pages in ASP.NET, Layouts in ASP.NET MVC 3.0 Razor, etc) you lose CSS intellisense, and even in the default modes, there is no kind of refactoring support.
One of the big appeals of JustCode was it's JavaScript support. Support for CSS would be really awesome. Specifically the following...
- Refactoring [Name]
- Refactoring [Class to Id]
- Refactoring [Id to class]
- Abstracting [Pull style into class]
- Refactoring [Move class into a different .css file]
- Highlighting
- Sub-Page Intellisense [Able to see available .css classes on inherited pages, like Layouts (MVC 3.0) and Master Page inheritors]
- Declaration Re-arranging [Able to find groups of css classes and re-arrange them to preferred sequence for proper cascading]
Just my $.02.
9 Answers, 1 is accepted
Thanks for your feature request!
I added a PITS item where you can vote for the feature. We will definitely consider it for one of our next releases.
Best wishes,
Ivo Bratoev
the Telerik team
Thank you for following up on CSS support. Actually we have began work on implementing it so I hope we'll make you happier JC user soon :-) We'll update the PITS item accordingly. Our bad for not doing it till now.
I will use the opportunity and ask you what features from JC you would like to see supported for CSS as well. Looking forward to hearing from you again.
Vladi
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
Things I see as feasible
- Javascript/CSS intellisense across the entire application. Tired of not getting it in sub-views in Razor.
- CSS 3.0 Hints/Warnings similar to JavaScript
- Brace Matching/Outlining with CSS just like Javascript/C#
- Go to Member support in CSS (class/selector)
- Find Usages in CSS (including Razor)
- Simple class refactoring
Things that I would love to see, but are probably too grand.
- DOM box Model per browser demo within CSS editor.
- SASS/LESS intellisense.
- CSS map
What would look great is if each class could essentially be examined like an object, and then declared classes that inherit from them be smaller child objects (imagine the rounded box 'classes' vs. the square box 'enums' in the default Visual Studio class diagrams). The extended data (imagine the dropdown properties/members from the visual studio class designer) would be akin to showing either the files that used said class, or if were even conceivable, the actual files and then tree-view list of the elements in each file that used them, with the ability to click on any class and see a series of lines connecting where it gets used.
Is this a ridiculously huge feature for something that doesn't even offer CSS support? Absolutely. Would it be [expletive deleted]? Hell. Yes.
Also, if said features were implemented, I would be very willing to pay more for the product. The amount of time alone any one of those three could save would be great.
Many thanks for your features suggestions. They are very useful for us and we are looking through them. As the CSS support is still under development your help is just in time and will be taken into account. We will introduce the CSS support in some of our next internal builds but we'll be rolling the features gradually. So stay tuned. We are looking forward to hearing from you again.
Vladi
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>