Community
Participate
Working Groups
Basic support for the SCSS syntax would be extremely helpful. See: http://sass-lang.com/ SCSS is a very powerful extension to the CSS styntax and adds nested rules, variables, mixins, selector inheritance, and more. It almost works with the normal CSS editor, but the syntax highlighting, indentation and code completion obviously gets confused with nested properties. By basic support I mean recognizing the nested structure for syntax highlighting and indenting and maybe getting code completion to work for normal CSS properties and values. Adding support for variables mixins etc. is probably a different beast.
http://sass-lang.com/editors.html lists an existing editor within Eclipse, and sounds like something to be handled in the Ruby space; it's not an in-scope web standard as I see it.
I agree it's not a real web standard. It's rooted in the Ruby world, but it's gaining popularity outside of that. I personally don't work with Ruby but find it very useful. Unfortunately the first Eclipse editor listed on that page doesn't exist anymore and the second one isn't very useful (only syntax highlighting). Aptana Studio doesn't feature code completion for SCSS. I'm already using the WST CSS editor to edit my SCSS, because I find it the best option, even though the indentation and highlighting breaks.. mainly because code-completion still works most of the time.
It would already be a tremendous help if the following could be considered in the basic CSS editor: - Source -> Shift left/right (ctrl-tab and ctrl-shift-tab) for bulk indent - Code folding to allow nested blocks If it is not appropriate to do this in the stock CSS editor, maybe clone and create a basic scss editor with these improvements? If anyone could point me where to start I would be happy to try and get this to work myself.
(In reply to Thomas Timbul from comment #3) > If it is not appropriate to do this in the stock CSS editor, maybe clone and > create a basic scss editor with these improvements? If anyone could point me > where to start I would be happy to try and get this to work myself. The "stock" CSS editor is part of the WTP Source Editing project. The git repo can be browsed here: http://git.eclipse.org/c/sourceediting/webtools.sourceediting.git/ Clone URLs are available at the bottom of the page. Look at the org.eclipse.wst.css.core/ui bundles.
Thanks. At the moment I've only managed to add 'smart edit' tabbing (shift left/right) by registering an IAutoEditStrategy, but this is of great immediate assistance already. What's the correct way to share this with you? This is my first time using Git (from within Eclipse), do I select "Push to Upstream"?
Usually when contributing patches to Eclipse projects you should push it to Gerrit [1]. But unfortunately, Gerrit is not available for the WTP SSE project. Hopefully the project committers will set it up soon. Meanwhile you can push your changes to your own fork in GitHub and give a link to the respective commits in this bug. First, you need to create new empty project in GitHub. Then change the push configuration of your local WTP SSE repository to push to your new GitHub project. Finally, do the push. You can consult the EGit User Guide [2] for help for each step. [1] https://wiki.eclipse.org/Development_Resources/Contributing_via_Git#via_Gerrit [2] https://wiki.eclipse.org/EGit/User_Guide
I hope this is what you meant: https://github.com/ttimbul/eclipse.wst/commit/23e8a7c99b72889bacdb93fa6720e2d0eecc3fa0
Yes. I meant exactly this. As far as I can understand your patch is a generic improvement of the CSS editor and not really specific to SASS. In such case I recommend to open a new bug in the WTP SSE project [1] (wst.css component) and attach a patch for review from the WTP SSE project committers. As I have mentioned there is still no Gerrit for this Eclipse project, so you should follow the guidelines for attaching a patch file to Bugzilla [2]. You can create the patch file from your Git commit [3]. Once you create the bug, please add a link here, so I know about it. [1] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=WTP%20Source%20Editing [2] https://wiki.eclipse.org/Development_Resources/Contributing_via_Git#via_Bugzilla [3] https://wiki.eclipse.org/EGit/User_Guide#Create_a_Patch_from_a_Commit
Yes it is somewhat generic, new bug here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=472056 I haven't got enough understanding of the parser yet to be able to get nested rules and others to work as easily.
Is any support for SCSS files planned?
I recommend to open an issue about this on the BlueSky project [1]. BlueSky integrates Language Servers with the Eclipse Generic Editor. VSCode has a language server for SCSS, so it should be fairly easy for BlueSky to integrate it too. This should be the shortest path for finally having SCSS support in Eclipse. [1] https://github.com/mickaelistria/eclipse-bluesky
Ruby support has been removed.
