• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOPopUpButton
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOPopUpButton


  • Subject: Re: WOPopUpButton
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 22 Jun 2007 00:50:06 -0400

In the end, camel case isn't that bad, and it makes you a good citizen. Swallow your pride and getOverIt.

It's the other way around actually. CamelCase is spurned by typographers for good reason. I guess Lemmings must be really good citizens. I'd rather think different, nothing to do with swallowing pride. Pride is arrogantly sticking with something that is wrong.
I generally avoid these threads like the plague (I didn't even scream at Lachlan and his curly-less one liners even though I was screaming on the inside!), but my homey is caught up in it, so I feel obliged to comment :)

* "Wrong" is really bold choice for a very subjective topic

* Java is not a procedural (well .. ok, well, sort of) language and stringing together multiple calls in a single phrase of code is a very common idiom in Java. Underscores in this context have a different visual effect than when used in a purely procedural language like C. I personally find it harder to scan this type of code quickly and mentally group the identifiers relative to the method call dots when compared to camel case. But this is all totally personal preference and no battles will be won in this thread.

* While there is value typography, you can't completely discount the value of consistency. You have a typographic paradigm for the language that is fairly well entrenched, and I personally agree with Eric that any typographic benefit you may have gained with underscores is potentially squandered in both the reader's context switch as well as annoyance level. It's left up to the reader to determine which is the larger trade-off, but for my money, I prefer "plays well with others."

* You have an entire set of tools geared towards supporting these conventions that you're swimming upstream against. This is actually a problem I have with WO core as well. I have grown to accept the get- method without a "get" but it gets on my nerves precisely because it's not "normal" Java. Every time I perform a code generation on accessors inside a WOComponent and go back to remove the "get" to be a good WO naming-convention citizen, I die a little bit on the inside. But I do this because it's confusing for people to have to mix-and-match API styles.

* Maybe I'm just a troglodyte ... Heck, I still type two spaces after periods most of the time (Note: I went back and took them out on this post :) ).

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: WOPopUpButton
      • From: Ken Anderson <email@hidden>
    • Re: WOPopUpButton
      • From: Ian Joyner <email@hidden>
References: 
 >WOPopUpButton (From: "Sigurður E. Vilhelmsson" <email@hidden>)
 >Re: WOPopUpButton (From: David LeBer <email@hidden>)
 >Re: WOPopUpButton (From: Ian Joyner <email@hidden>)
 >Re: WOPopUpButton (From: Eric Robinson <email@hidden>)
 >Re: WOPopUpButton (From: Ian Joyner <email@hidden>)

  • Prev by Date: Re: WOPopUpButton
  • Next by Date: Re: WOPopUpButton
  • Previous by thread: Re: WOPopUpButton
  • Next by thread: Re: WOPopUpButton
  • Index(es):
    • Date
    • Thread