![]() ![]() Hopefully, once some are released, there will be an easy, Package-Control-esque method for installing them. We're still in the early days of Coda 2 as such, there currently aren't any plugins available on Panic's website. Why isn't there a helpful command palette that allows me to specify which action to execute with text? I can't always remember the keyboard shortcut for creating a split why can't I pull up the command palette, and type "split"?Īt this point, I consider a command palette to be essential in my workflow, yet Coda is missing one entirely. Command PaletteĬonsidering the fact that Sublime Text 2, in barely a year, has become the golden editor amongst web developers, you would think that Coda might adopt some of the most touted features in that editor. Nonetheless, it's a feature that might be helpful to some - just not me. Do they understand what a branch, stage, or commit is? My instinct is that, if you do, then you'll absolutely prefer to perform these sorts of commands in the Terminal - likely using your own custom aliases to speed things up. It very well might be helpful to those who aren't entirely comfortable in the Terminal, but, still, I wonder how many of these folks are truly using version control. So, sure, adding a UI for Git was a smart move. Git integration in Coda 2 is certainly not a minus, but more of an "ehh." The previous version of Coda provided Subversion support (while the community moved to Git). Sheesh, don't make me build a tool, like Prefixr, to get around this. Don't make me memorize whether or not Microsoft now provides its own prefix for gradient support. If, behind the scenes, Coda would maintain a list of every CSS3 property, along with its required prefixes, that would be huge. Note: a smattering of Mozilla prefixes are provided, but not nearly as many. If convenience were the only downside, that would be one thing, but the problem is that their decision to only provide Webkit generation and auto-completion endorses the notion (especially for newcomers) that it's okay to tailor designs specifically for one engine. When questioned (on Twitter), Panic noted that it's incredibly simple to manually add the other prefixes. Why will it auto-complete -webkit-animation, but not any of the others ( ms, o, moz)? Why does it render a Webkit gradient, but not for the other vendors? It makes sense the live preview uses the Webkit engine, so they need to ensure that the gradients (and other CSS3 properties) that the GUI produces will render correctly.īut, particularly when considering the huge debates that have centered around CSS and Webkit in the last half year, Panic's decision to seemingly endorse Webkit-exclusive CSS3 properties is a terrible one. There's no denying that Coda's Webkit-based support is fantastic. Oh, and as for Opera and Microsoft prefixes ( -o and -ms, respectively), you can forget about it. Yep, the official version doesn't work - and neither does -moz-transform (or any of the other versions, for that matter). The documentation only registers if I specificially use -webkit-transform. You might be surprised to find that, if I type the official transform property, nothing shows up in the sidebar ( there's also no auto-completion for the property). It's very helpful…and limiting at the same time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |