You can have your buttons, just don't take away my syntax! It's easier for me to keep typing inline rather than have to highlight a phrase and click a button.
-wraith808
I don't think that's a true statement. You are more COMFORTABLE typing inline, or you PREFER to type like that. But it's not easier by any means for you, him, or any other person. There's no argument you can make to convince me that it's easier to type a word with brackets or whatever vs. clicking a single button.
At the risk of sounding rude, I've heard from programmers that they use all this text editing stuff because it's easier for them. This is not true. you can't say that because the alternative (buttons) doesn't even exist! You can't say one way is easier or better when the other way is not even available! So, in my opinion, the programmers sort of lie to themselves by saying it's better this way, but it's not. What they are really saying is that it's not worth the trouble to create a button, which is true in a lot of ways. It is easier to write code (if you know it) than it is to create a button, which is essentially writing a LOT of code and going through the whole troubleshooting of it, etc. So yes, text-editing is easier compared to writing the code for a button.
But text-editing is definitely NOT easier than clicking a button. Two different things.
-superboyac
*You* can say what's easier for *you*. If I'm in a text box typing, it's much easier for me to put the tags
inline than to go to the bar. I say easier, and I mean easier. When I code, it's easier for me to click a - sign on my number pad than to highlight the line and press a button to cut the line. And I do say easier, because what is easier? Clicking one key? Or moving my hands from the keyboard, highlighting a line, then pressing a button in a totally different place. You might say that you have to learn the syntax. True. But once learned, which way will be easier for you? I'm not sure, but for me, it's the keyboard.
Recent Posts
sorry...
