Lowfokus
Archive for category Entry Level Programming
Fantastic Objective-C Courses
Posted by technohermit in Entry Level Programming, Objective-C, iPhone on 2010/06/11
If you are interested in Objective-C programming, or just plain old C programming, you should check out any books written by Stephen Kochan. I recently took his Objective-C online course (live streaming), an 8-lecture course, with a fantastic forum, for an astounding $75. If you are new to programming in general, don’t fret. Stephen walks you through it in an easy to understand way. Knowing the libraries, on the other hand, will take time. Nothing but your own ambition to learn those will get you there, though. You can find Stephen’s courses here: classroomm.com
His accompanying book, necessary for the course, can be found here: Objective-C 2.0
Moving Around in Vim
Posted by technohermit in Apple, OS X, OS X Shell, Uncategorized, Unix, vi on 2009/11/19
I’ve written a couple of beginning UNIX for OS X entries, such as creating a .bash_profile and .bashrc file using vim. Here is another vim tutorial for moving around in the screen editor, so you can see just how powerful it’s commands can be.
This post will deal with mostly command mode, the default mode when you open vim (or an existing file with it.) To move the command marker around the file without entering INSERT mode consists of four basic keys. Moving to the next/previous word, to the beginning of a paragraph, etc. will require a bit more memorization.
You want to first familiarize yourself with the h, j, k, and l keys. The outer two (on a standard keyboard) move your cursor left or right one-character; h, to the left, and l to the right. j will move your cursor up to the next line, while k moves it down one line. The fact that you are in command mode means no changes are made to your text at this point. You can use the arrow keys for the same functionality, but getting used to the keys will help you keep your hands where they belong–typing and editing text.
Moving to the beginning of the current line is done by pressing O (zero). To move to the end of the current line press $. + moves your cursor to the beginning of the next line, and – moves you to the beginning of the previous line.
Next are some basic ideas for commands. Some will take a number argument, followed by a command. Some can be written with a number argument followed by another command. For example, x in command mode means delete a character. To delete a word, or the rest of a word if you are in the middle of one, you type dw. If you precede x with a number, n, vim will delete the following n characters from the line. The command to delete the next four characters would be written, simply, as 4x. To delete the next four words, you would type 4dw.
Vim is a very capable text editor once you learn more about its commands, and get used to bouncing between INSERT and command modes. Below you can find a table of common commands and their function, at least enough to get you on your way as a skilled vim user.
|
Movement Command |
Function |
|
h |
Move Left One Character |
|
j |
Move Down One Line |
|
k |
Move Up One Line |
|
l |
Move Right One Character |
|
0 |
Move to First Character Of Current Line |
|
$ |
Move to Last Character Of Current Line |
|
+ |
Move to First Character Of Next Line |
|
w |
Move to Next Word or Punctuation Mark |
|
W |
Move to Next Word |
|
e |
Move to End of Current Word |
|
E |
Move to End of Next Word |
|
b |
Move Back to Beginning of Word or Closest Punctuation |
|
B |
Move Back to Beginning of Word |
|
) |
Move to End of Current Sentence |
|
( |
Move to Beginning of Current Sentence |
|
} |
Move to Start if Next Paragraph |
|
{ |
Move to Start of Previous Paragraph |
|
Delete Command |
Function |
|
x |
Delete Current Character |
|
X |
Delete Character Immediately Left Of Cursor |
|
dw |
Delete Current Word |
|
10dw |
Delete Ten Words |
|
D |
Delete To End of Current Line (also d$) |
|
dd |
Deletes Current Line |
|
20dd |
Deletes Twenty Lines |
|
dG |
Deletes From Cursor to End |
|
u |
Undo (doesn’t work for single character deletion) |
Cron Jobs on OS X
Posted by technohermit in Apple, OS X Shell, Uncategorized, Unix on 2009/11/15
Since OS X Tiger, cron has been replaced by a utility called launchd, and three separate launch daemons. Rather than having to run crontab to manipulate scripts, they are run by launchd according to three separate directories inside of /etc/periodic.
The scripts contained in these folders are run at specified intervals by three preference files, in XML format, found in the /System/Library/LaunchDaemons folder. You can manipulate the .plist files with a text editor or Apple’s Property List Editor (if you’ve installed Developer Tools.) They are named, simply enough, com.apple.periodic-daily.plist, com.apple.periodic-weekly.plist, andcom.apple.periodic-monthly.plist. They are, by default, set to run at the same time as the old cron jobs, in the middle of the night. If you happen to shut down your Mac, it might be a good idea to change these intervals to a time when you’re sure the computer will not be shut down, as these jobs are important.
You will find a script in each of these folders called 999.local. This file is set to read-ony by default, and is for ”backwards compatibility with the old /etc/daily.local” according to the comments in the file. (I’m running Snow Leopard.) I’d recommend not modifying the scripts in the /etc/periodic folders, and creating a /etc/daily.local, /etc/weekly.local, and /etc/monthly.local file for your cron jobs, as you have the 999.local script in each of the daily, weekly, and monthly sub-directories of /etc/periodic to tell your scripts to run. Any future system updates could change the default files in those three directories, so if you modify those you may end up losing your scripts. Avoid that by setting up your own.
If you are running aTiger, the 999.local file may not exist, and you will have 500.daily, 500.weekly, and 500.monthly files inside their appropriate /etc/periodic directories. You should still create a daily.local, weekly.local, and monthly.local script file and place them in the /etc directory, and they will be called from the respective 500.* file.
Setup Your .bash_profile On OS X | A Sample Bash Profile
Posted by technohermit in Apple, OS X, OS X Shell, vi on 2009/11/07
This is another addition to my entry level OS X shell category. This one covers setting up a more detailed bash profile, so certain things are done by default when you open your Terminal.
We start by opening the Terminal in your ~/Applications/Utilities folder. If you don’t know what that means please start with this post, as it will show you a very basic beginning to the Terminal in OS X. Be sure you are in your home directory by typing pwd at the bash prompt and hit enter. It should look similar to this:
Next, we start vim opened to your .bash_profile. At the bash prompt type vim .bash_profile and hit enter. If the file exists, it will open it, if not it will create one for you. Your Terminal window should now look like this:
My screen shows one alias I created in my last tutorial. I like that one but technically it doesn’t belong in your .bash_profile, it belongs in a file called .bashrc. The .bash_profile is for your login shell options, and the .bashrc file is read for subsequent interactive shells; meaning a shell opened to type commands, not just to run a script from a file automatically. You can launch another shell on top of your login shell by typing the shell name at the prompt, i.e., bash, and then hitting enter.
This lesson will focus on login defaults, such as the PATH variable in your .bash_profile. In the process, we will be using vim, so if you are unfamiliar with that, practice makes perfect!
The PATH variable is where the system searches for binaries (shell scripts, programs, etc.) to execute. All UNIX systems provide a default path, but you can add to it. As you add scripts of your own creation and such, you probably want to create a directory in your home folder to store them. This way if you screw something up, it will affect you and not the system. For example, an erroneous rm command if you are in the /bin directory could be really bad news.
Let’s go ahead and first create a new directory called bin in your home directory. Create a new interactive shell by pressing ⌘-N. Type mkdir bin and hit enter. Now type ls and hit enter. You should see the new directory listed with your other folders:
This is where you can store any shell scripts that you create, as they are easy to find in this folder. In vim, type “i” without quotes to get you into INSERT mode. You will see –INSERT– at the bottom of your Terminal window. Now you can begin typing text. You should comment your script files, and your other various profiles so you know what something does if you ever need to edit. It’s just good programming practice to get the comments done as you progress with coding, not when you’re done!
To make a single line comment, the first character on the line needs to be the pound sign, #. Type in #Additional binary folders, and hit enter. Next, we set the PATH like so, to *add* to the default PATH: export PATH=$PATH:/Users/yourusername/bin
You can see in my screenshot below what the file should look like. Replace the yourusername with your actual username for your account. Mine is Tech, so that’s how it shows in my screenshot. Also keep in mind, that UNIX is case-sensitive:
Now you can save this by hitting the escape key, and typing :w then pressing enter. Let’s add some more commands to the profile. We can set a welcome message to the login, and set the shell’s timer to check for new mail. This really only matters if you use a text-only mail client, such as PINE or Alpine. It will not affect the OS X Mail client.
Set a message to display when you login with the echo command. This is a good command to know for the command line as well, as you can see certain system variable settings, such as your current PATH. You can do this by typing echo $PATH at the bash prompt and hitting enter. To use echo in your .bash_profile to set a welcome message, type echo followed by the message:
echo Welcome back, Mr Awesome! Your present working directory is: $PWD
looks like this when you log in:
To set the mail check timer, write a line in your .bash_profile like so: export MAILCHECK=30
The time set is in seconds, and OS X’s bash shell by default is set to 60 seconds. Your .bash_profile should now look similar to this:
Next time I will cover creating a simple shell script, and changing file permissions to run them. Also, I will try to cover some common aliases, as well as creating your .bashrc file, which is where we store the aliases. Thanks for reading, and if you have any suggestions or questions, please feel free to ask!
Using vim In OS X — A Text Editor Tutorial For Beginners
Posted by technohermit in Apple, OS X, OS X Shell, Uncategorized, vi on 2009/11/03
Here is a quick tutorial for people unfamiliar with text editors in UNIX. If you are just getting started with the Terminal in OS X, you probably need to create your .bash_profile and such, so that you can keep your settings upon logging out of the shell. I will show you how to create this file in a text editor called vim, which stands for vi IMproved.
Vim is a very powerful text editor, and if you have any experience in UNIX at all, you probably were shown pico, which is easier to use at first due to some of the commands being shown at the bottom of the screen as you work in pico’s buffer. In pico, there is no separation from command or input modes, also making it a bit less confusing. The buffer simply means what is shown on your screen, not yet written to disk. While a GUI text editor such as Microsoft Word or Apple’s Pages do not tell you that you are working in a buffer input mode, technically it is the same thing. If they crash, you lose what you changed if it was not saved prior to the crash.
Vim is a little obscure, yet extremely functional. You start vim by typing vi or vim at the bash prompt in Terminal. Terminal is located in your ~/Applications/Utilities folder by default on OS X. When it opens, you are by default in command mode. Vim shows you this startup screen, which has a bunch of tildes (~) on the left-hand side, and some version information in the center:
If you type something in, the startup screen goes away and the first tilde also disappears. The tilde characters simply clarify lines in the buffer. They will not print, they are just there showing you where the next lines are. Once started, you are by default in Vim’s command mode. If you type vim testfile.txt at the bash prompt, vim will open the file testfile.txt in whichever directory you are currently in. If testfile.txt doesn’t exist, vim will create the file and open into the edit buffer for you, skipping the welcome screen:
As shown in the screenshot (click to enlarge it, as with all screenshots on this blog), the buffer is in INSERT mode. By default, no matter what file you open or create, vim starts in command mode. It doesn’t ever show —COMMAND— at the bottom of the screen. Vim lets you know you aren’t in command mode by telling you that you are in INSERT mode.
To get back into command mode, which is where you will end up saving files to disk, changing the contents of vim’s 26 named buffers (consider them like the clipboard in a GUI text editor), moving around the screen, deleting lines, etc. Anything you want to do with the file besides type in text will generally be done in command mode. Let’s save this file now, so you can see how it works to get in and out of command mode.
First, hit the ESC key. On almost every keyboard ever, this will be the key at the very top-left corner of the keyboard. You should no longer see –INSERT– at the bottom of the Terminal window. Now type the following command, without the quotes: ”:w testfile.txt“. See screenshot below:
You can see at the bottom of the Terminal window that the write command was successful. You also see that three lines were written containing a total of 138 characters. You can verify the file was written by typing (again, without quotes) “:q“, and hit enter. This quits vim. At the bash prompt, type “ls” and hit enter. You should see your new file in the list of the directory. To remove (delete) the file, type “rm testfile.txt” and hit enter.
Now to create your .bash_profile, so you can save certain settings. When Terminal starts, it will read this file to load alias information, screen settings and such, if they are explained in this file. As you become more familiar with the Terminal and start to have preferences for certain things, i.e., showing hidden files when you get a list of a directory, you may want to create an alias for the ls command so it shows them by “default” because of your .bash_profile.
First, navigate to your home directory if you are not there now. You do this by typing the command “cd ~” at the bash prompt and hitting enter. Terminal will show your computer name, followed by your present working directory, and yourusername$, which is the bash prompt. You should see something like this:
Create your empty .bash_profile by typing “vim .bash_profile” and hitting enter. We will create a simple alias and save the profile. Then we will quit Terminal, restart it and verify the alias still works.
By default, the alias wouldn’t work again after you quit Terminal. If it is in your profile, it will work when you open a new Terminal, such is the point of having a profile. To type in what I show above, press the letter “i“ on your keyboard to put you in insert mode. Then type the following exactly:
dirA=”ls -lia”
Hit the ESC key, and type: “:w” to save the file. Now type “:q” to exit vim and return to the bash prompt. You can verify the file was written and it’s contents by typing “cat .bash_profile” and hitting enter:
Now quit and re-open Terminal. You should now be able to get a detailed list of your directory, showing hidden files, by typing dirA and hitting enter:
Next time I will show you how to navigate through text, delete lines and add or retrieve lines to and from the named buffers. If there are certain things you would like to learn about Terminal or vim, please leave comments below. Please also let me know if any of this could be better clarified, as I check my comments often and will respond promptly. Thanks for reading!
Simple Introduction To Apple’s Unix Using Terminal on OS X
Posted by technohermit in Apple, Entry Level Programming, OS X, OS X Shell, Uncategorized on 2009/10/24
This post is for someone interested in learning UNIX on Mac OS X Snow Leopard, but lacks experience using a command line, or has only C:\ prompt knowledge. I will show you, simply, how to map a DOS command to a UNIX command, and to save your profile so the alias name you create is persistent. If you are a shell scripting genius, this post is something you are encouraged to comment on and expand upon, as learning scripts and commands for OS X can be input many different ways. It never hurts to have different suggestions. I will try to make this at the minimum a weekly edition to my blog, and expand each article further than the next.
Let’s get started. First, open Terminal from your /username/Applications/Utilities folder. This is the command line utility for UNIX, by default it is Bash (Bourne Again Shell.)
You will see your entire present working directory prior to the $ prompt. The tilde (~) represents /Users/your home folder. The standard format is computer name: pwd. You can type the simple command pwd and the shell will respond with the folder you are currently accessing.
I like a cleaner shell screen, so I type bash, and hit enter. This opens a new bash shell, on top of the existing shell. Next, the command clear deletes the current Terminal text and starts with a fresh bash prompt. You end up with a Terminal screen that looks like this:
Here, we can start by showing the man (short for manual; built in UNIX help pages) page for the command ls (list), which is basically the dir command in DOS. Simply type man ls at the command line and hit enter. You can move down the pages line by line using the down arrow key on your keyboard. To exit the manual, simply type q.
The man page shows you the various options you can use along with the ls command, for example, ls -lia. This command is particularly useful when searching a directory for hidden files (they start with a period), as Finder refuses to display them by default:
Now, if you are used to DOS, here is a helpful way to stick with the commands you know, yet tell Terminal to run UNIX commands. You create an alias, basically a command name you make up mapped to a system command. If you want to use options such as -lia, you need to enclose the command in double quotes. The syntax of the alias command in bash is alias newCmdName=systemCmdName. The command in DOS for a directory listing like the one above is dir /a. So we can map dirA to ls -lia like so: alias dirA=”ls -lia”
Note that UNIX is also case-sensitive, for files as well as commands:
You can simplify entering commands by using the up arrow to cycle through previously typed in commands. The history command, saves the commands you enter by line number, which you can view by typing history. To execute the line number, type an exclamation point followed by the line number:
Now, to save this new alias dirA you created into your bash profile. This way it doesn’t get erased when we kill the shell and quit Terminal. You may not have a profile set up for bash in your home directory, so what you need to do is create one. Bash will look for .bash_profile first, so it is best to name any profile you want to use on a regular basis with this name. It is a hidden file, so you need to have the period in the file name. For simplicity, you can create a simple text file in your favorite text editor, name it bash_profile (without an extension)and save it in your home directory. Write the exact command on one line like so: alias dirA=”ls-lia”
Save the file, and then change the name in Terminal. Use the command mv to change the name so it begins with a period. Simply type mv bash_profile .bash_profile and press enter:
That did two things: one, you moved the file; two, you learned that mv is the same command as the DOS command move. You can follow the procedure above to make an alias for the mv command, and place it on the next line in your .bash_profile, so it remains permanent for your login shell. If you like running an “non-login” shell as I do above, you can use the command cp to copy your .bash_profile to .bashrc like so: cp .bash_profile .bashrc
Here is a short list of a few DOS commands, along with their respective UNIX bash counterparts (pdf of list here):
|
DOS COMMAND |
UNIX COMMAND |
|
DIR |
LS |
|
MOVE |
MV |
|
COPY |
CP |
|
FIND |
GREP, FGREP, EGREP |
|
MEM |
TOP (virtual memory use VM_STAT) *use ctrl-c to end TOP command* |
|
CD |
CD (PWD to display current directory) |
|
DEL |
RM |
That’s all for this quick lesson. Stop by next week for more DOS examples in UNIX, and (hopefully) working with vi, UNIX’s text editor.
myBlogEdit
Posted by technohermit in Entry Level Programming, Uncategorized, Web Tech on 2009/10/09
So I decided to go all out and make it easier for me to blog, even if I’m stuck with no intraweb, somewhere where the dredded “E” is in the upper left hand corner of my iPhone. I have been looking into things like this here OS X app called….you guessed it, myBlogEdit.
Set up is pretty simple so far.
- Download and install.
- Command-Comma for Preferences. Highlighted in blue, you will see the XML-RPC thing. This is important to also set up in settings on your WordPress Dashboard.
- Fill in your site info, and you’re pretty much done.

I’m diggin’ that this app has a bunch of HTML tags for your clicking approval, as well as an empty set that does a nice drop-down list. It has taken me a while to get this first post out with the program, but it’s because I’m taking screen shots and telling you all about it as I go. Suffice it to say, it’s pretty slick so far.
Unfortunately, I cannot seem to change the CSS for the preview, and I’m going to write the developer and ask him why that is. I cannot cut and paste my CSS into the preference, nor can I drop a CSS file on it. The only option you have is blank, or “default” (program author supplied). I do note that you can type in the box, however I do not consider typing all of your CSS out all over again a viable option. You can choose cut copy and paste from the file menu, but paste seems to be the only one lacking function. Bummer. That will put the brakes on me using this app full time for sure.
Upload is pretty straight forward, and it does look like the preview version. I have to say that you should note the width of an image you want to upload prior to you accepting the upload. It seems that thumbnails are automagically generated for you after you make images in excess of 150px. Pretty neat.
Suffice it to say, though, that you really do need to love editing your blogs in HTML form in order to like this application. If you are used to the WSYWIYG web version that WordPress gives you to use, than you probably aren’t going to be a huge fan of changing strictly to HTML. For those of us out there that click the HTML tab on that web interface, this little program is pretty good.
So one thing I learned the hard way, do not delete the post from WordPress, or it won’t let you publish it again. The error I got was invalid post ID, found in the xml data in the log. myBlogEdit just gives a cryptic popup advising you to have XML-RPC enabled, and check the error log as well. Do yourself a favor and check the error log if it worked before and suddenly doesn’t. Well, that’s it for now, until I get more used to writing with this application. Give me about a month and I’ll come back and tell you how it’s been going.




















