Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Events
oBFusCATed:
--- Quote from: Ceniza on November 10, 2011, 12:12:33 pm ---It also allows you to comment/uncomment by selecting something and typing either / or *.
--- End quote ---
This is pretty annoying feature. 50% of the time it was deleting my selection.
The C::B solution is definitely better here:
Ctrl+Shift+x = comment the seletion
Ctrl+Shift+c = uncomment the selection
Works 100% of the time and it is pretty predictable.
--- Quote from: smallB on November 10, 2011, 12:08:37 pm ---But "full configurability" should be a part of every feature not just this one.
--- End quote ---
This is definitely the wrong philosophy. Features should just work. Because it makes life easier.
We as developers should strive for this. Making it configurable is the easiest thing, most of the time, but not the best.
smallB:
@Obfuscated I strongly disagree with you on that one. Providing configurability of a feature allows every one to set it in a way that work best for them - in the spirit "What's good for you it doesn't mean it is good for me, and what you think is pretty to me seems awful". What you're saying is that there is one and correct/best way to suit everyone's needs and I'm saying that this isn't true and bad design practice.Just look around you, on most popular, successful software and think about it. The best way is to let everyone set the feature so it works the way suits the particular individual best, not the designer.
And at the end just to prove that what I'm saying is correct: you're saying something like:
"This is pretty annoying feature. 50% of the time it was deleting my selection." - It is not annoying to me. I love it. If I want to delete something I press either spacebar or backspace.
So you see, what's annoying for a one person may be of great help and usefulness for the other. There is no One Size Fits All. This approach is bad, and it doesn't work.
oBFusCATed:
But you've not understood what I've said.
There are plenty of approaches to implement a feature.
Some of the approaches, like the auto-commenting feature of V-Assists aren't robust and annoys some people.
The strive should be for non-annoying implementations of the features, like the manual commenting/uncommenting in C::B.
And I don't like to have to setup my C::B for 30 minutes every time I install new OS.
Most of the things I do is disable this, this, this and this.
smallB:
--- Quote from: oBFusCATed on November 11, 2011, 10:17:02 am ---
The strive should be for non-annoying implementations of the features, like the manual commenting/uncommenting in C::B.
--- End quote ---
But that's my point exactly - just because you think it is annoying or it indeed annoys you - fair enough - everyone has their own preferences, and likings, and here is the crux - everyone's preferences should be respected - not just yours. Because it is not annoying to me and I really like it. So what I'm saying is that everyone, you, me and other users should be able to set this feature the way suits them best. So it also means that you should be able to disable this if it does annoy you. It wouldn't be fair on you to not allow you to disable this, right? So why do you think it's fair on others not to be able to enable this? It's two way street. And that's good.
smallB:
--- Quote from: oBFusCATed on November 11, 2011, 10:17:02 am ---And I don't like to have to setup my C::B for 30 minutes every time I install new OS.
Most of the things I do is disable this, this, this and this.
--- End quote ---
I don't think anyone likes it. But, but, but, but:
1. You can always export cb's settings and after installing new OS you can simply import them ;).
2. How would you feel about it if you were robed from the privilege of disabling this, this and this? Because designer decided that disabling this is so annoying and it shouldn't be allowed. Would you agree with his approach/way of thinking?
3. There should be (and I'm going to add it as a my suggestion) option which would allow to choose (again you see? it should allow, to accommodate user like you - minimalist) how cb is set up.
What I mean by this is that there should be some kind of levels defined (which could also be edited) so for example user like you would pick:
Expert
someone else would pick:
Intermediate
and I would pick:
Novice
where everything would be set up as to ease my work as much as possible with this IDE. Default compiler, safest settings in it, every possible help when working with editor etc. etc etc.
But again, all this should be configurable so I with time with change my novice profile, and let's say remove some settings from compiler - or add them, but it still be my Novice profile.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version