Simple Practices to Enhance Your Daily Development

As time passes, our brains develop routines for what we do. Development is no exception. My brain has half a hundred (or maybe more) little routines that it’s been trained to enact when certain requirements are fulfilled.

There are generic practices that hold across most disciplines. These are especially easy to see when working with computers. How the keyboard and mouse interact. What tools are best to use for a particular job. Processes already in place in the system to allow greater efficiency.

In my (relatively short) time as a Clarion Dev, I’ve managed to accumulate a number of wonderful practices that without which, I would be a lot slower. Not that I’m quick, but I’m quicker with these in place.

My plan is for this post to grow via input from around the world, as well as my own as I come across them. Here be the (dragon) information.

Keep in mind too, that this post is tailored for folk who are new to the Clarion world.


[ctrl] Y    Remove Line

A very nifty trick (thanks Brett and Devan), this removes the line of code the cursor is situated on. Nice!


F10    Extended Text Dialog 

As of Clarion 6.1 (ish, ?) you can press F10 in an entry field within the templates to get an Extended Text Dialog window pop up, allowing you to "see" much more of what you are typing.

Great for Filters and other places where you sometimes type quite a long line of code!


[ctrl] R    Compile

Possibly the most used in my arsenal of speedy cyborg brain enhancements. Buttons are old-school, Twin keystrokes are the new web 2.0!


[ctrl] S    Save

This one I learned from MS Office. It’s been beaten into my subconscious routine. Always pressed, after most actions, unless I specifically don’t want to save.


[alt] M->E    Comment All

This one is great. Highlight 1 or more lines of code (SHIFT and arrow keys), then press this key sequence and it’s all Commented Out. OUT. Nice.

[alt] E -> M, ESC, [enter] on yes for the "are you sure", [ctrl] S (just for consistency, even though the compiler saves before .. compiling), [ctrl] R.



– Embeds are a single-click away. Why go through multiple clicks/windows?


Leave a Reply

Your email address will not be published. Required fields are marked *