![]() ![]() The other feature that can come in handy occasionally is to use them as external editors with an FTP client such as Fugu (from my Alma Mater), or Cyberduck, so you can edit the file directly, without having to download it, edit it, save it, and upload it again.Īll in all, these are both quite good editors. Double-clicking on a delimiter works from either end. Smultron will highlight the opening delimiter when a closing delimiter is inserted or crossed over with cursor TextWrangler will highlight the opening delimiter only when the closing one is inserted. Some other features I will briefly mention that both editors share (and comes in very useful, especially with the LISP-based language I use at work), is the ability to double-click on a delimiter (such as a parenthesis or brace), and have the text selection extend to the matching opposite delimiter. Both of these editors support that, but I couldn’t get TextWrangler to recognize functions with my custom syntax, whereas Smultron does it quite well (in both cases it’s based on regular expression matching). Many code editors allow you to go to a function defined in the current file by selecting its name from a menu. (Incidentally, I also have to use Microsoft Visual Studio occasionally at work, and it won’t uncomment a selection if a blank line is included, a problem not shared by Smultron.)Īnother feature that works with Smultron that I couldn’t get to work with TextWrangler was functions. This was not a problem for Smultron (where the comment/uncomment command has the key sequence ?-/, not editable in the preferences), which correctly commented and uncommented selected text. Unfortunately, while TextWrangler correctly recognized and colored comments as such, the comment/uncomment command had no effect on files using my custom syntax definition. In TextWrangler it’s only a menu command by default (annoying), but key sequences can be assigned to all the menu items in the preferences pane (a very nice feature, indeed). First, both editors have a command to comment/uncomment the selected text. While both editors read the syntax files and colored the source code appropriately, it ended up working better with Smultron than with TextWrangler. Syntax elements include keywords, comments, strings, and functions. Both editors allow the user to create custom syntax definitions in Apple’s XML PList file type. ![]() I use this feature at work, where I use a proprietary LISP-based language. This feature was added in the next release, which came shortly thereafter.Ī feature shared by TextWrangler and Smultron is support for custom language syntaxes, allowing colorizing of languages not included. For example, I had requested key strokes to delete from the cursor to the end or beginning of the line, a feature present in TextWrangler (but not in XCode) to which I had grown accustomed. ![]() Furthermore, Smultron is under active development, and the developer is quite responsive about bugs and feature requests. Smultron offers most of the features I used regularly in TextWrangler, including custom language syntax coloring, balancing delimiters, and regular expression searches. I switched to Smultron recently, having previously used TextWrangler extensively. Smultron is a free, open source code editor available for Mac OS X 10.4 (Universal). For projects in which I won’t be using XCode, however, I now generally use Smultron as the code editor. For most C, Objective-C, and Java applications, I use Apple’s XCode IDE for the simplicity of having the editor, compiler, and executable all in one interface. While the choice of a language may dictate the compiler to be used, there are generally a number of options for the code editor. In developing software, the choice of tools used can affect the ease of the job significantly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |