In the year or so that I’ve been using ST3, I’ve found it easy enough to customize and extend it that I’ve been highly motivated to actually do those things. \u00a0Part of that work has been building my own syntax file for HLSL. \u00a0Now, my syntax file isn’t overly complex or even as complete as I’d like it to be, but… regex (Sidenote: \u00a0if someone much better at regex than me looks at this and laughs at my pitifulness, I fully welcome help making improvements!). \u00a0However, what I did was define function definitions and callsites, and that opens up an interesting possibility in ST3 beyond just more syntax highlighting; with that information, if you put your shader files into a sublime-project file, you get automatically hooked up to ST3’s Goto Definition framework. \u00a0Here’s what that looks like:<\/p>\n
And, once you have this working, it’s a short jump to getting a library-wide autocomplete functioning. \u00a0Unfortunately, I cannot share my autocomplete indexing solution, but I can share my syntax file. \u00a0Here<\/a> it is! \u00a0Hopefully you enjoy it, and again I fully welcome suggestions for improvements. \u00a0Also, here<\/a> is my theme file, if you’re interested in a very HLSL-specific color coding, but it’s absolutely not required.<\/p>\n","protected":false},"excerpt":{"rendered":" Don’t worry, this’ll be a quick one. If you write shaders, then you’ve certainly dealt with the issue of what to write them in. \u00a0Since there’s no true shader IDE (And seriously, why isn’t there? \u00a0They’re mainstream enough at this point that I can’t imagine it’s a niche market anymore, \u2026 Continue reading ![\"syntax1\"](\"http:\/\/www.teamfizzgames.com\/Matt\/wp-content\/uploads\/2016\/09\/syntax1.png\")
<\/a><\/p>\n