Huh? Objects are instances of classes.
Yes, I phrased that badly. What I meant was that a class should be a noun that represents an abstract concept. For example, "Schedule," or "Feed." Methods of those classes should be verbs/actions, like "Feed.download()" or whatever. A telltale sign that your hierarchy is not really OO is when you have classes that are actions, since that's going more towards procedural code. e.g. instead of having a FeedParser class that gets instantiated with an argument, and has a .go() method that returns a useful value, the class should be Feed, and the method should be Feed.parse(). At least, that's what they're teaching in school these days. =)
So is there a CVS/SVN/darcs/whatever set up somewhere?
Yes, check earlier in this thread for it.
What should we call this/What about something with "character"
Dur? I thought we were going to call it FeedCatcher, is that no good? If not, the name should at least be somewhat indicative of what the app does. Also, I'd rather not put "pod" or "cast" in the title, since the uses of RSS feeds are outgrowing simple iPod syncing, not to mention that the internet radio show phenomenon predates the whole podcast movement. I don't especially care though, as long as people can figure out what it does and if they want it from the name.
I have no problem with names with "character" as long as there's sort of a mental connection people can make with the function. Names like Audacity for an audio program or FireStarter for a firewall program are fine. I often have trouble remembering the names of programs I even have installed because they make no sense or are entirely unrelated, so let's avoid names like "Fred" or "Gordon" or the Swahili word for internet =)
Personally, I like Feedcatcher, Ahab, or maybe some clever play on "Pod" since I'm fond of dolphins (and then we can use a dolphin silhouette or something as the icon/logo of the program).
At any rate, let's just pick something and move on, since there's plenty of actual work to be done. If you can't help with the actual code, please check out the latest source from svn, and install/run it and let us know if you encounter bugs (there are probably a lot). No matter how minor, and we can put it on the list of things to fix.