Here you can see that “customerRS” is selected on line 14 and all the other places where it appears in the method is also highlighted.

This feature can be very handy to see how things are used in your code and is much easier than using the Find panel.

Note: The matching is done by full word tokens. So if you highlighted just “customer” in the above code, then nothing is matched because that does not match the “customerRS” tokens.

To turn this feature on, head over to Settings, Coding and check the box for “Display selection matches”.

You can also change the color that is used for the matching by changing the Syntax color “Selection Match Color”.

Paul learned to program in BASIC at age 13 and has programmed in more languages than he remembers, with Xojo being an obvious favorite. When not working on Xojo, you can find him talking about retrocomputing at Goto 10 and on Mastodon @lefebvre@hachyderm.io.

• Facebook
• X
• LinkedIn
• GitHub
• YouTube

What’s New in Xojo 2024r4

Xojo 2024r4 brings a range of exciting updates that enhance cross-platform development, improve security, and provide more tools for creating dynamic and interactive applications. Here are some of the standout features:

Web Framework
Enjoy smoother and more efficient web applications with updates to Xojo’s Web Framework. Improved memory usage and numerous bug fixes ensure that your web apps run reliably and perform optimally, providing a better experience for your users.

Discover Web Framework Improvements

These updates and enhancements are designed to make your development process more efficient, productive, and enjoyable. Whether you’re building new applications or enhancing existing ones, Xojo 2024r4 provides the tools and capabilities you need to succeed.

Get Started

To learn more about Xojo 2024 Release 4 and begin your development journey, please visit the Xojo 2024r4 Release Notes. The update is available for download now from the Xojo downloads page.

What’s Next?

We’re continuously working on new features, updates, and enhancements to our platform. If you have any suggestions or ideas, please add them to the Xojo tracker. We’re always looking to improve and expand Xojo to better serve our community.

Thank you for being part of the Xojo community. We’re excited to see what you create with Xojo 2024r4!

• Facebook
• X
• LinkedIn
• GitHub
• YouTube

Line Highlight

The first change is that the entire line containing the cursor is now highlighted. This makes it much easier to find where your cursor is on large displays and matches behavior that is common in other coding editors, such as BBEdit or Visual Studio Code. This highlight is controlled in Coding Settings:

Here is what he row highlight looks like:

Syntax Help Area

With the enhancement to show method overloads in the Syntax Help area a couple years ago, the area was changed to dynamically resize its contents depending on what is shown there. Although some liked this design there were others that felt that it was distracting to have the Syntax Help Area size change so often.

An improvement made last year altered the syntax help area behavior so that it is only updated when the mouse cursor stops moving for a moment. Because of that change, we are able to introduce the option to have a fixed-size Syntax Help Area.

In the Coding Settings, you can choose: 2, 3, 4, 5, 6 Lines or Resizable. The default is now 3 lines. If more information is shown than will fit in the Syntax Help Area, there is a scrollbar (which you can now actually use since the area won’t update with new information until you stop moving the mouse).

You should also notice improved syntax help in general. The lookup engine is now better able to infer context to show more accurate information. I’m particularly pleased that CType now shows in the Syntax Help Area because I can never remember the order of the parameters!

Standardize Format

A long-standing request (from 2010!) was to have the Standardize Format option available on the Code Editor command bar. Lots of people like their code formatted nicely and Standardize Format is a great way to do that.

Now you can easily click a button on the command bar to quickly format everything in the code editor, instead of first having to Select All and then choose a contextual menu option.

If you really like your code to be formatted automatically, don’t forget you can always turn on “Apply standardize format after ending line” in the Coding Settings.

And don’t forget that you can also create your own script to format your code any way you want. Learn more about this in Custom Code Reformatting in the docs. You might also want to try to this powerful reformatting script.

If you have other suggestions for Code Editor improvements, please be sure to create an Issue. One popular suggestion is to have the text under the cursor be highlighted throughout the code editor (see Issue #74741), which I have started to investigate. Read all about the Xojo Code Editor in the Xojo Docs.

Paul learned to program in BASIC at age 13 and has programmed in more languages than he remembers, with Xojo being an obvious favorite. When not working on Xojo, you can find him talking about retrocomputing at Goto 10 and on Mastodon @lefebvre@hachyderm.io.

• Facebook
• X
• LinkedIn
• GitHub
• YouTube

What’s New in Xojo 2024 Release 3

We’ve been working hard to bring you the best possible cross-platform development experience, and Xojo 2024 Release 3 delivers. Here are some of the highlights:

These updates and enhancements are designed to make your development experience more efficient, productive, and enjoyable. Whether you’re building a new application or updating an existing one, Xojo 2024 Release 3 provides you with the tools and capabilities you need to succeed.

Get Started

To learn more about Xojo 2024 Release 3 and to get started with the development process, please visit the Xojo 2024r3 Release Notes. The update can be downloaded right now, from the Xojo downloads page.

What’s Next?

We’re always working on new features, updates, and enhancements to our platform. If you have any suggestions or ideas, please don’t hesitate to add them to the Xojo tracker. We’re always looking for ways to improve and expand Xojo.

Thank you for being part of the Xojo community. We’re excited to see what you’ll create with Xojo 2024r3!

• Facebook
• X
• LinkedIn
• GitHub
• YouTube

In this article we will highlight several functions provided by the Xojo IDE that allow you to speed up and improve productivity in your large projects.

Filter the Navigator

The Navigator filter field allows you to limit the number of visible items in a section to those matching the typed text. This can filter a list to include only the objects used, such as controls, or even items that match the names of events, methods, properties, constants, etc. -practically any of the items added to the project except the code itself.

If you need to keep all elements of your project visible while browsing through matching results, it is preferable to use the standard search which you can access using Command + F (on macOS) or Control + F (Windows and Linux).

Going Directly to a Project Item

However, there are many times when you know the exact name of the item you want to select/display; whether it’s the name of a method, event, or even a control itself. In these cases, it is much quicker to use the Project > Go to Location option (Command + Shift + L on macOS; Control + Shift + L on Windows and Linux).

When you select this command, a dialog box will appear where you can type the path of the item you want to select. So, for example, if you want to go to the method “myMethod” found in the window “MyWindow” you would type: “MyWindow.myMethod”. The text field in that dialog offers auto-completion which means that, in most cases, you will only have to start typing the name of the main item and use the Tab key to access the menu displaying all the matches to select any sub-item you wish to select.

Additionally, and unlike the filter field, the hierarchy of the project elements will remain visible in the Navigator as they are.

Powerful Searches

This is undoubtedly the most powerful option that you can access using the keyboard shortcut Command + F (on macOS) or Ctrl + F (Windows, Linux), or by clicking on the magnifying glass icon in the bottom bar of the IDE.

Once you access the Find panel and start typing in the search field, the list below will start to populate with all the matches (by default); but you will probably find it more useful in larger projects to have the list refresh after you press the Return key. To do this, go to the Preferences window and, in the General section, change the “Find/Filter results appear” option to “After pressing Enter/Return”.

While by default the Find window displays matches found throughout the entire project, there are times when you may want to narrow it down to either the selected item, including any subclasses that may be based on that item, or simply the item in question; you can do this by using the following buttons:

Another added advantage of the search area is that it keeps a history of previously performed searches, thus speeding up the process when you need to revisit a new group of elements. In addition, you can change from simple (textual) searches to the more powerful use of regular expressions (RegEx) when looking for elements in your project.

Of course, this same panel also allows you to replace the searched text with other text on all the matches shown… but be careful before confirming. Make sure that they truly apply to the elements you want and not to others just because they start with the same word entered in the search field!

Bookmarks: Sitting There for You

In many cases, you will use the above systems to edit the code in a given method or event; especially if these are areas of code that you visit frequently. If that is the case, then you will find Bookmarks a really useful feature.

You can add or remove Bookmarks in the code editor by accessing the contextual menu from the currently selected line of code. You can also add as many Bookmarks as you need to a single code block, which is especially useful for large blocks of code on a given method, for example.

Once you have all your Bookmarks defined, you will simply need to select the menu option Bookmarks > Show All to have them displayed in the search area where you can select them.

Tip: Use the Preferences > General > Menu > Edit Menu Shortcuts option to assign a keyboard shortcut to the Bookmarks > Show All command. This will make it quicker to update the bookmarks listed in the Search area when they are not listed.

Tabs and Workspaces

Sometimes it is preferable to have several items in view when working on a large project, so that you can switch between them quickly; or to have the Layout Editor and the Code Editor for the same object. This is where Tabs and Workspaces are extremely useful.

By default, the Xojo IDE window has a single tab that displays all the elements added to the project, but you can open as many tabs as you need, and these tabs will be preserved when you close and reopen the same project, just as Workspaces will.

So, if you need to focus on a particular module or class, you can double-click on the item in the Navigator to open it in a new tab. Want more clarity, especially if your tabs bar is overcrowded? In that case, you can drag the tab in question outside the window boundaries to open it as a new IDE window (a new Workspace). Of course, you can also use keyboard shortcuts to move between open tabs in a single IDE window.

As you can see, Workspaces are new IDE windows for a single project. In fact, you can have as many as you need using the New > Workspace menu option. However, this option is only recommended if your setup has a high-resolution screen or multiple screens connected to your computer.

Conclusions

As we have seen, using filtering, searches, bookmarks, tabs and even the “Go To Location” command, among other options mentioned, will greatly speed up navigation when you are working on large projects.

What other IDE techniques do you use? Share them with us on the Xojo Forum or on social media.

Happy programming with Xojo!

Javier Menendez is an engineer at Xojo and has been using Xojo since 1998. He lives in Castellón, Spain and hosts regular Xojo hangouts en español. Ask Javier questions on Twitter at @XojoES or on the Xojo Forum.

• Facebook
• X
• LinkedIn
• GitHub
• YouTube

Starting with Xojo 2023r1 you can now do this in the Xojo Code Editor.

To swap lines, put the cursor on a line and press Option+Up Arrow (Mac) or Alt+Up Arrow (Win/Linux) to move the line up in the code. Press Down arrow to move down. Here’s a quick view of how this looks:

It also works with a selection:

To duplicate a line, put the cursor on the line and press Option+Shift+Down Arrow (use Alt instead of Option on Windows/Linux):

This also works with a selection:

I hope these new commands can make your time in the Xojo Code Editor more productive!

Paul learned to program in BASIC at age 13 and has programmed in more languages than he remembers, with Xojo being an obvious favorite. When not working on Xojo, you can find him talking about retrocomputing at Goto 10 and on Mastodon @lefebvre@hachyderm.io.

Xojo’s team was all vaxxed-up and so happy to get together in Nashville for #XDC2022. Tennessee’s Music City was a delightful backdrop for the first in-person Xojo event since 2019. Check out the short highlights video from Nashville and then join us for #XDC2023 in London, UK. You can register here.

This year the Xojo team and community welcomed a new Xojo engineer, Ricardo Cruz. Ricardo has applied his expertise to advance and improve Xojo Web. To quote one of Xojo’s engineers, “Ricardo coming in has been awesome,” a sentiment echoed on the Forum and the community in Nashville.

Xojo Web has come so far this year. Control reliability has improved, IDE previews have improved and reconnections have really improved. The web framework can now more often reconnect back to the same web session if it still exists. This is one of the things Ricardo is really happy about, “You can switch to your email app in your mobile, copy something to the clipboard, come back to the web app and it is still there, ready to continue.” Under the hood, some dependencies received updates, like jQuery. As a user, you don’t have to do anything, just use the new Xojo version! Try to tell that to another web developer, that’s sci-fi outside of Xojo. Also, thanks to the community, the memory and CPU usage continues to be improved release after release. “Honestly from my perspective it is just fun to play with little projects in it because it has really matured,” says Xojo’s Director of Engineering, Travis Hill.

Speaking of technical achievements, this year we added two new targets to Xojo: Windows on ARM 64 and Linux on ARM 64. On Windows, you can natively deploy to ARM-based tablets and laptops that run Windows. On Linux, you can deploy to 64-bit Raspberry Pi which can address significantly more RAM than 32-bit versions.

We built the Xojo Cloud Control Panel with an updated version of Xojo, and thanks to some Web framework improvements the controls now stay more responsive under load. Plus we’ve added Xojo Cloud servers in Sydney, Australia for web developers in Australia and New Zealand. We also continued improving and testing our upcoming support for Android, which is now feature complete and awaiting some remaining bug fixes before we make it available to everyone.

In addition, we want to brag about a few technical improvements, including the numerous PDF updates implemented by Xojo Engineer and now PDF expert, Javier Menéndez. Also there is the option to generate Program Database (PDB) files on Windows and improved multi-monitor support shepherded by Xojo Engineer William Yu. The list goes on: Code Assistants, on-device debugging in iOS, new Xojo Documentation site, adding Controls at runtime, loading speed faster for big projects, and the time team-Lefebvre built a web app to Calculate Combat Rolls in Twilight Imperium…

Inside Xojo we improved a lot too. Besides welcoming Ricardo and his beard to the team, we migrated Xojo’s bug and feature reporting platform from the internally managed Feedback tool to the much loved Issues. This has increased productivity, streamlined work flow, made it easier to search and find, comment, edit. The team couldn’t be happier!

This year also included Xojo’s first Bug Bash in a long time! During the Bug Bash, Xojo’s Code Editor got some much needed improvements resulting in noticeably faster updates. Plus updates to the Syntax Help Area thanks to Xojo Engineer and retro-computing expert, Paul Lefebvre. Besides the very real smashing of 100 bugs, the bash had the unintended consequence of giving the engineers an opportunity to work on things they don’t normally work on, giving engineers opportunities to collaborate and better solve things.

All in all, 2022 was a year of forward movement for Xojo. Which has us leaning into 2023 with a lot of excitement and expectation. Our team is committed to continuing to make Xojo the best cross-platform development tool and we thank you for being part of Xojo’s continued success!

Code Editor

The Code Editor is one of the most commonly used parts of Xojo, so we are always trying to improve it. One of the problems that been reported with it is that it can use quite a bit of CPU. There was also a report of disk access when typing in the Code Editor. After studying the code, I determined that disk access could have been occurring during code hint lookups (that were searching a SQLite database) while typing, but this problem was no longer occurring with the switch to the new documentation in 2022r1 which uses a much smaller in-memory database.

However, I did notice that the Code Editor was sometimes doing too much work. For one example, the code indenting and folding was updated after every character was typed.

Since indents and folding do not usually need to be updated while you are typing, we changed it so that those things are updated when you pause typing, press return or do specific actions that warrant an immediate update (pasting text, for example). The benefit to this change is that much less CPU is used while typing in the code editor and it is harder to type faster than the code editor can respond.

There were other similar improvements to the mouse movement. Previously the Syntax Help Area would be updated live as the mouse moved around the Code Editor. This was distracting and used a lot of CPU as it looked up what to display. With this release, the Syntax Help Area is only updated when the mouse stops moving. This is far less distracting when moving the mouse around and you should no longer see the CPU spike. A nice benefit of the Code Editor using less CPU is that your laptop battery should last longer when you are coding in Xojo.

Also related to the Syntax Help, sometimes it would not show syntax hints based on where the mouse cursor was and sometimes you had to click to get the hint to appear. A few bugs with that were found and fixed so that you should now have more consistent and accurate information.

Some other Code Editor fixes include:

• The text cursor no longer sometimes remains visible when the Code Editor does not have focus. I found it confusing when that happened.
• Syntax hints are displayed for more keywords, such with looping and conditionals.
• Option-Right-Arrow no longer positions the cursor incorrectly in certain situations.

Syntax Help

It had been a long-standing complaint that the Syntax Help Area only showed the method signature for a single method, which was not all that helpful when it was a method that had multiple overloaded signatures, which is frequent with object-oriented programming.

Travis initially implemented the changes to allow the Syntax Help Area to show multiple method overloads. You may be surprised to learn that this actually required changes to the AutoComplete component.

There were a lot of changes, but they were not too difficult. The trickier part was finding the various permutations and edge cases, which is where I came in. Initially we had the Syntax Help Area expand to show all the overloads, but during pre-release testing we noticed this could cause it to expand to fill the entire code area if you had a lot of overloads (such as with XojoUnit’s Assert() methods). We decided to instead have a max size of 4 lines and use a scrollbar if there were more.

When reviewing this display code I noticed that the Syntax Help Area was always meant to use the same font as the Code Editor, but due to a bug (from 2013 or so) it was unintentionally using the system font. Using the Code Editor font for this makes it much easier to read.

While in this part of the code I also improved the display of the descriptions that appear in the Syntax Help Area (after the member syntax) when they are set on project item members (using the Description field in the Inspector). In addition, Constructor descriptions are now shown.

Thanks

Xojo has been around for over 20 years now and with continued iterative improvements throughout the years has remained a useful and productive tool for thousands of developers making desktop, web and mobile apps. I am honored to be able to work on it and am always in awe of the great things that I see our users create, things that they may not have been able to make using other more complicated tools.

I want to thank everyone for their bug bash submissions and especially those that helped test during the 2022r3 pre-release period. Your well-crafted Issues with sample projects were appreciated! As announced at the Xojo Developer Retreat last month, we are going to continue this with two weeks of bug bashing at the start of each release cycle, which begins around the time a release such as this ships.

// This script takes the current selected comment
// and changes the comment prefix.

Function Name() As String
  Return "Swap Comment Prefix"
End Function

Function CanEdit(selection As String) As Boolean
  // Check if comments starts with // or '.
  Return Left(selection, 2) = "//" Or Left(selection, 1) = "'"
End Function

Function Edit(selection As String) As String
  // Swap // with ' or swap ' with //
  If Left(selection, 1) = "'" Then
    Return Replace(selection, "'", "//")
  ElseIf Left(selection, 2) = "//" Then
    Return Replace(selection, "//", "'")
  End If
End Function

This is not too lengthy, so let’s examine the parts. With a code assistant, there are three methods that are required: Name, CanEdit and Edit.

The Name() method returns a string containing the name that will appear in the Code Assistants menu. You can nest items using slashes, so “Paul/Swap Comments Prefix” would have this appear in Code Assistants->Paul->Swap Comments Prefix.

The CanEdit() method provides the code editor selection as a parameter. In this method you should return True if this code assistant is allowed to edit the selection. If you return True, the name will appear in the Code Assistants menu. If you return False it will not appear in the menu.

The code above checks if the selected text starts with the comment prefixes we want to swap: // or ‘.

The Edit() method is where you modify the selection, returning new text that will replace the selection in the Code Editor. This method does a single replace of “//“ with “’” and “’” with “//“.

Save the above script as SwapCommentPrefix.xojo_code_assistant and copy it to the Scripts folder in your IDE install folder.

If Xojo was running, you can tell it to reload those scripts by holding down Cmd (on Mac) or Control (Windows/Linux) when right-clicking.

Now type a comment like this:

‘ This is a comment.

Select that comment and right-click. Choose Code Assistants->Swap Comment Prefix.

The line now shows as:

// This is a comment.

For other sample Code Assistant scripts, go to Examples/Advanced/IDE Scripts/Code Assistants in the Xojo download folder.

Learn more in this video! Be sure to share your Code Assistant scripts in the forum!

For those of you that don’t consider reading through over 220 items as fun as I do, here are a few things I thought I would highlight, in no particular order.

• Desktop projects now save icon resources as compressed PNGs. This can greatly reduce binary/xml project file size and also reduce the .xojoresources file size in text projects. In the case of the Eddie’s Electronics sample project, the binary project dropped from 11MB to 780K, the XML project from 22MB to 1.1MB and the .xojoresources file from 11MB to 388K.

• Need to iterate through a String’s characters in a completely unicode-friendly way (including emojis)? Rather than using the String.Characters iterator, use the new String.Codepoints iterator which returns one value for each unicode scalar.

• You can now install Xojo on Windows ARM 64-bit. Xojo itself remains an Intel x86-64 binary, but Windows ARM has a translation system built-in that will allow Xojo to run. This should allow those of you using ARM Windows in a VM on an Apple Silicon Mac to use Xojo there. If you’re interested in native Xojo support for Windows ARM, subscribe to Feedback Case 62672 so you’ll be notified of updates.

• Auto-complete continues to get smarter and faster. It can’t quite write your code for you, but now it does a better job of substituting text and offering suggestions, among other things.

• The Code Editor has more improvements, particularly in the area of code folding. Another improvement is that you can use Go To Location to jump to a specific line in the code using “#50” (for example) in addition to the previously allowed “50”.

• For use with Declares, there is now an OSHandle class that can handle either an Integer or a Ptr.

• And although we mentioned it in another blog post, I’d still like to remind people that you can again build your Mac apps from Windows and Linux. Improvements in the open-source linker project used by Xojo allowed us to bring this feature back. Of course, please continue to test your Mac apps on an actual Mac before you ship them.

Line Numbering and the Gutter

Code Editor Line Numbering is now an IDE preference instead of a per-Code Editor preference. In the Preference (or Options) window, choose Coding and then turn on “Show line numbers in gutter” to enable line numbering on all Code Editors.

With Line Numbering enabled, the gutter area is a bit wider to show the line number. As you move the cursor around in the Code Editor, notice that the gutter highlights to indicate the line you are on. This can be very handy to help find where the cursor is in a busy method.

You can also now click on a line number in the gutter to select the entire line. This is helpful if you want to copy the entire line, but it is also a great way to make it a bit easier to study a particular line of code more carefully.

Code Folding

If you’ve not used it before, Code Folding allows you to collapse (or fold) code to help reduce clutter in the Code Editor. You do this by clicking on the small “-” indicator that appears to the left of a code block. When code is folded that indicator changes to a “+”, which you can click to make the code visible again. Folded code is never removed, it is just temporarily hidden.

In this release, we improved the “-“ and “+” indicators so that they show with a rounded rectangle to be a bit friendlier. The code folding line highlights are also now slightly less distracting.

Super Return

When you are on an incomplete line of code, you can press Shift-Return (also known as Super Return) to automatically provide some assistance. For example, start typing an If statement like this:

If True

and press Shift-Return after typing True. The Code Editor will fill in the “Then” and “End If” and put the cursor between them:

If True Then
  <-- Cursor here
End If

When you press Super Return with a For loop, not only is the Next added as it always was, but if you have an inline loop variable, then it is added to the Next as well. This can make it easier to match nested loops.

Although this was added in 2021 Release 1, you may also find this tip useful: Press Super Return on a comment line to start a new line with a comment.

Related to Super Return is Option Return or Control-Alt Return on Windows/Linux. When you press Option Return on a line, a new line is added with the code continuation character placed at the end of the current line.

In 2021 Release 2, when you press Option Return when inside quotes for a String, the string is completed and things are extended to the next line.

Other Improvements

The Project -> Go To Location feature lets you jump to a specific method in your project by typing the class and name, for example: CustomerDetailsWindow.LoadCustomers

In 2021 Release 2 you can now also add a line number to jump to a specific part of the code. This is great when asking someone else on the team to look at some code, especially in a lengthy method. You can do this by putting a “#” followed by the line number like this: CustomerDetailsWindow.LoadCustomers#15

Sometimes you want to get the text for a method signature, but don’t want to copy the entire method and all its code (which was what you previously got when you select a method in the Navigator and choose Copy). Now you can right-click on the method signature in the header of the Code Editor and choose “Copy signature” to copy the signature to the clipboard.

As usual, be sure to check out the full release notes for 2021 Release 2 as there are other cool things to find or download 2021 Release 2 and try it yourself!

When dealing with how variables are shown by auto-complete, you first need to understand the concept of a variable’s ‘visibility’ or scope.

When a variable is declared, its scope is limited to the block of code in which it is declared. For example, add a method with this code:

Dim myVariable As Integer
For myVariable = 0 To 9
  // Do something
  MsgBox(myVariable.ToText)
Next

In the above code the scope of the variable myVariable is the entire method. This includes being within the ‘For…Next’ loop.

Now consider this code in a method:

For myVariable As Integer = 0 To 9
  // Do something
  MsgBox(myVariable.ToText)
Next
// myVariable cannot be used here and will not auto-complete

The block of code within which myVariable is declared is the ‘For…Next’ loop.  The scope starts at ‘For’ and ends at ‘Next’. Because of this limiting scope myVariable does not auto-complete outside the loop and if you type it manually in code like this you will get a compile error for that line that says “This item does not exist”:

For myVariable As Integer = 0 To 9
  // Do something
  MsgBox(myVariable.ToText)
Next
myVariable = 10 // compile error here

(Thanks to Robin Lauryssen-Mitchell for this tip.)

Monaco
This font is installed by default on MacOS. It is big and very easy to read.
http://www.gringod.com/2006/11/01/new-version-of-monaco-font/

Menlo
Also included by default on MacOS.
http://en.wikipedia.org/wiki/Menlo_(typeface)

Source Code Pro
Adobe just released this font in 2012 or so and I really like it. I have been using as my default font since I first found out about it. The screen shot below shows how it looks in Xojo on Mac.

https://github.com/adobe-fonts/source-code-pro

Inconsolata
This is what I used until I switched to Source Code Pro. It is a little smaller than other fonts at the same point size.
http://levien.com/type/myfonts/inconsolata.html

ProFont
This is the first alternative font I used. I think the others mentioned here are nicer.
http://www.tobias-jung.de/seekingprofont/

What do you use?
There are dozens of other great programming fonts. What is your favorite? Let us know on Twitter (@xojo).
Note: A version of this post was previously published in Oct 2012.