I think my love affair with icons is coming to an end.
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
I think you're missing the point. Icons should come with text and/or tooltips. Once the user has found out what they are, and used them a few times, then the icon is automatically a visual shortcut for them. Doesn't matter if a fire-breathing dinosaur means "save", it's only the association in the user's mind that matters. Of course continuity across apps is hugely important, for the same reason, so in fact a 3.5 inch floppy disk for "save" is of course easier (at the moment)....
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
I think icons are useful but the user should know in advance what the icons themselves represent, hence the more the symbol is universal the better the icon is (think about road signs). However, your test, in my opinion, is not that significant, because it was a 'first impact' one. I think we appreciate the application icons after a while we'are using them. My two cents.
Veni, vidi, vici.
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
I know I'm an old fart, but I've found that the increasing use of icons as an alternative to text labels has drastically diminished my ability to accomplish anything useful in a reasonable time. What is an obvious association with a useful function to a developer is a complete mystery to me. A pox on whoever invented the concept! Tooltips are an invaluable aid, but they often take next to forever to load and display. Let's go back to meaningfully labeled buttons, and drop this asinine icon concept forever!
Will Rogers never met me.
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
One of the big advantages of text is accelerator keys: putting an '&' in front of the character underlined it and told you what key combination would activate that function so you didn't have to use the button / menu / whatever. Now, with icons and the damn ribbon that is all gone, and I for one do miss it - it made it much easier to become a power user!
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I think you're missing the point. Icons should come with text and/or tooltips. Once the user has found out what they are, and used them a few times, then the icon is automatically a visual shortcut for them. Doesn't matter if a fire-breathing dinosaur means "save", it's only the association in the user's mind that matters. Of course continuity across apps is hugely important, for the same reason, so in fact a 3.5 inch floppy disk for "save" is of course easier (at the moment)....
effayqueue wrote:
Doesn't matter if a fire-breathing dinosaur means "save"
Don't be a wally. Everyone knows the fire-breathing one is delete. It's the smiling dino that means save.
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
seems like you are using the wrong icons. It's not easy to create a self explaining GUI. But it's possible. It needs to be one of the keys to go for during the complete development process.
regards Torsten When I'm not working
-
Your point being? Come on, talk about it, you know you want to.
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
-
Your point being? Come on, talk about it, you know you want to.
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
It's all about recognition. in one location the function comes with text and icon, in another icon only. Personally my attention for an option is often
colorandlocationbased. Icons are like shortcuts to me. eg. Save is a blue icon (a floppy) on the upper left side. Bold, underline, italic are smaller dark icons (the letters B U I) on the middle somewhere. Put two or three blue icons on the left side of the screen and the total point of using an icon is lost (on me in any case). Similar, put the save icon upper left in one screen and upper right in the other.V.
-
I think I love you.
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
You need to get together with your colleagues and finalize a set of standard icons. Not a "Oh I've found a 'save' icon that also has a floppy on it but mine's prettier so I'll use that." set but an actual Standard. With suitable punishments for abusers.
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
effayqueue wrote:
Doesn't matter if a fire-breathing dinosaur means "save"
Don't be a wally. Everyone knows the fire-breathing one is delete. It's the smiling dino that means save.
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
I think the main advantage of using icons instead of text is that it takes up less space. A smaller UI allows more space for the actual content (image/text/code/whatever) the user wants to work with. Users figure out what the icons mean after a while anyway and when they do, they don't care anymore if the button describes the action. Fast access to many options, without unnecesary hierarchy because it wouldn't fit else, becomes more important.
-
Congratulations! You have won a prize. You are the 10,000,000th member to have his url truncated by The Lounge HTML Eater.
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
Icons always need learning. In some cases there are standard cross-application icons (I'm thinking the NOSE – new, open, save, exit – set, copy and paste, print, undo/redo) which you can probably assume that users have already learnt, so using those is fine. But anything that is application specific means that you are asking the user to learn what that symbol means. You should always provide tooltip information to help users learn what the buttons do, for this reason. I'd also recommend always providing a text based way to get to the same functionality (e.g. a menubar).
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
People that insist on using only icons in an app should be dragged outside and shot.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
What's your general feeling about using icons in apps? I did a test of the app I'm working on to one of my colleagues in another department. I removed the text from the command buttons leaving only the icons and asked her to see if she could identify what a button might be used for. In only one case (the option to save a file) did she sort of intuitively "feel" that it was for that purpose. All other icons seemingly never complemented the app. She said if she had the option to hover the mouse over a button and see a tooltip that might help. She also agreed that if you have text on the button the icon would do no more than window dress it so why bother if the text alone describes the function? I'm not suggesting that icons have no value but right now as I look at VS's IDE I can't truly say that every icon suggests to me what its purpose is - thank heavens for keyboard shortcuts. Besides, if I remove the icons from my app it gives me more space for multi-language text which is the next major enhancement. We all recognise the icon to save a file for example; it resembles a blue stiffy disk used in the old days when that was a demonstrable use for them. DevExpress's checkbox can be configured to look like a rocker switch, something akin to the switches we use to turn lights on and off. That is, I'm beginning to recognise that an icon's success or failure to illustrate its purpose might be connected to its tactile usage we're familiar with. There are experts out there who know about the perceptions and psychological affinity of image connections and how they map to the societal expectations of a generic population and how the environment influences neuron transmissions and implied understanding of spatial image renditions (rolleyes). That sort of crap that they're paid a lot of money to do. Microsoft has apparently backed down on the awful colour scheme used in the new VS beta? I'll go back to my project and smoke some dope and see if the app makes sense. From where I sit, if the icon makes sense, use it. If it doesn't then don't use anything? What's that whiff in the air I smell. Mmmmmmmmmmmmmmm.:thumbsup::java: :)
"I do not have to forgive my enemies, I have had them all shot." — Ramón Maria Narváez (1800-68).
Icons (tiny, hard-to-see, very colorful) are absolutely essential to the future of the "Window" as is tooltip text to demystify the artful message in the image. And ergonomics kicks in after use so the image becomes less important while location can be paramount. Consider allowing your array of icons to be undocked, right? Aside: One of the greatest renditions of a help file, to supplement the tootip in the case that tooltips were turned off, was the image of the interface in various panels and zooms, that employed "hotspot" definitions for the sub-image cooresponding to the icon face.
