A matter of style
-
This was discussed here in the recent past but I have no idea what the consensus was if any. So here's YAP. (Yet another opinion.) There needs to be some form of visual separation between the "Customer Name" etc. and the Values. If the values are also labels, it might be done with colons or spacing. If the values are in text boxes or similar, the colons would not be extraneous. Did your CIO say why not to use colons? Seems a bit drastic. I mean, where would be without our colons? :laugh: Edit: struck not :-O
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
Big Daddy Farang wrote:
I mean, where would be without our colons? :laugh:
Constipated?
-
Why should you use colon????? I think MS uses those since it looked good in DOS ( as a visual separator). It seems to have carried the tradition. Today if you have a label and a textbox that look different, I dont think colon is of much use. As an end user, I dont even notice the difference. Is there any scientific reason for using that?
It's not all about the UI; it's also about reflecting real world use of the colon: as an introductory break.
-
sorry? i have never been fond of using colons in forms. i think it get messier and clutters things up when for the most party, all my textboxes have a space between the header and it is clearly defined by the structure more than some colon.
----------------------------------------------------------- "When I first saw it, I just thought that you really, really enjoyed programming in java." - Leslie Sanford
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
Mark Nischalke wrote:
I've always used a colon but have recently been told by our CIO to not use them.
If you're using a C syntax like language, then the only thing you need to worry about is when he tries to remove your semi-colons.
Deja View - the feeling that you've seen this post before.
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
Show him, oh, I don't know, just about every dialog in Windows!
DoEvents: Generating unexpected recursion since 1991
-
Show him, oh, I don't know, just about every dialog in Windows!
DoEvents: Generating unexpected recursion since 1991
Impirical proof does not stop zealots.
Deja View - the feeling that you've seen this post before.
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
Labels on labels get colons labels on actionable elements do not. However, I try to be consistent. Personally, instead of a colon I prefer to use strong.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
I always have used colons after the labels... Just my preference. I resisted any anatomical wise-cracks (it was tough). ;)
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated. There are 10 kinds of people in the world: People who know binary and people who don't.
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
For me, it depends upon the layout. If the label is above the control it applies to, I don't use a colon. If the label is to the left of the control, I use a colon. I stick to one layout in a given application (labels above or labels left). I don't know where I got this convention. Now that's just scary :sigh:.
Software Zen:
delete this;
Fold With Us![^] -
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
I've always been lavish in my use of separators for clarity, and the colon was a favorite. But since having one-third of my colon removed I've become much more conservation minded, switching instead to semi-colons.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
So he's a colon control freak? X| :laugh:
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
Aint that a PITA
Never underestimate the power of human stupidity RAH
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
Your app must have nothing to improve on to notice such things... :-D I must admit I can be meticulous in how my app looks.
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
If it is a localized app the developer might want to leave the colons out - something else might be more appropriate for other languages.
Idaho Edokpayi
-
Big Daddy Farang wrote:
Did your CIO say why not to use colons? Seems a bit drastic.
No reason given. Guess its just a means of exercising control where he can and where he shouldn't be.
only two letters away from being an asset
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
Colons. (Your CIO bored?)
cheers, Paul M. Watson.
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
-
So whats the consensus around here? When creating an app do you place a colon after your labels or not? i.e. Customer Name: [label] or Customer Name [label] I've always used a colon but have recently been told by our CIO to not use them. I think it just makes everything bleed together and looks terrible.
only two letters away from being an asset
I personally think using a colon is preferable, but if it's not allowed, at the very least I think a good way to delineate the title from the label is to Bold the title and leave the label normal. At least then, you have clear separation.
========================= ~Events occur in real time~
-
Sounds like he's just pissing on everything to mark his territory. Common behavior for corporate climbers. To a man, that type of person should be fired with extreme prejudice.
-
One must be able to control ones colon.
only two letters away from being an asset
-
This was discussed here in the recent past but I have no idea what the consensus was if any. So here's YAP. (Yet another opinion.) There needs to be some form of visual separation between the "Customer Name" etc. and the Values. If the values are also labels, it might be done with colons or spacing. If the values are in text boxes or similar, the colons would not be extraneous. Did your CIO say why not to use colons? Seems a bit drastic. I mean, where would be without our colons? :laugh: Edit: struck not :-O
BDF A learned fool is more a fool than an ignorant fool. -- Moliere
Big Daddy Farang wrote:
So here's YAP. (Yet another opinion.)
Wouldn't that be YAO? :) I prefer colons, and right justified, so the label is almost touching the control (appropriate whitespace). When I was first introduced to this, I didn't like it, but our user testing showed most people are able to track from label to control better with less space between label and control (on forms with many label/textbox combinations, so not much vertical space between each element, and very heavy on text). --G