1. What are all naming conventions I need to be aware of? db table is plural, model is singular, controller is plural. so you have the User model that is backed by the users table, and visible through the UsersController. files should be named as the wide_cased version of the class name. so the FooBar … Read more
Unfortunately, it’s not so simple when you deal with legacy conventions. And DOM Events have a lot of history behind them. Here’s how type attribute of Event is defined in DOM2 Events specification: Interface Event (introduced in DOM Level 2) type (of type DOMString, readonly) The name of the event (case-insensitive). The name must be … Read more
function startEditing(){ if (user.canEdit(currentDocument)){ editorControl.setEditMode(true); setButtonDown(btnStartEditing); } } Should read like a narrative work.
Naming numbers is terrible practice, one day something will need to change, and you’ll end up with unsigned five = 7. If it has some meaning, give it a meaningful name. The ‘magic number’ five is no improvement over the magic number 5, it’s worse because it might not actually equal 5. This kind of … Read more
If you are going to be distributing a lot of stuff, I would really suggest getting a domain name. Another alternative however would be to use your e-mail: e.g. bob@gmail.com would become com.gmail.bob. This is less common than using domain names but is still done by some and still ensures uniqueness.
In general, I break lines before operators, and indent the subsequent lines: Map<long parameterization> longMap = new HashMap<ditto>(); String longString = “some long text” + ” some more long text”; To me, the leading operator clearly conveys that “this line was continued from something else, it doesn’t stand on its own.” Other people, of course, … Read more
I guess it’s ok if you think it helps, but many Clojure projects don’t do so — cf. Compojure (using a top-level compojure ns and various compojure.* ns’s for specific functionality), Ring, Leiningen… Clojure itself uses clojure.* (and clojure.contrib.* for contrib libraries), but that’s a special case, I suppose. Yes! You absolutely must do so, … Read more
With just Ruby (i.e. not Rails), naming is only a convention. In Rails the convention of using underscores is necessary (almost). I think convention #2 lowercase_and_underscore.rb is more common and looks pretty good, though an article Here says lowercasenounderscore.rb is the Ruby convention. Pick either which ever convention is more common or which ever one … Read more
The crucial factor is whether the menu option requires additional information (input or a selection) before it carries out the operation. So Help-About doesn’t require an ellipsis, but File-Open does. That’s what the Microsoft, Apple and KDE guidelines say anyway. Microsoft Windows applications are supposed to follow Microsoft’s “User Experience Guidelines”. Here’s what they say … Read more
Douglas Crockford gives a reason for choosing the K&R style1: I always use the K&R style, putting the { at the end of a line instead of the front, because it avoids a horrible design blunder in JavaScript’s return statement. The blunder he is referring to is how JavaScript handles the return statement differently in … Read more