On 07/18/2010 02:04 PM, Andreas Volz wrote: > Am Fri, 16 Jul 2010 15:10:56 +0200 schrieb dhp_...@doublehp.org: > >> To Andreas: >> >> After long reflexion, about my TB issue, I think that you broke the >> Remember-size fatures. >> >> Because the issue is very recent: end of june or begin july. >> >> Please fix it ASAP, it has many consequencies. It's breaking 3 years >> old scripts, and that put's me on nerves to see them fail. I have to >> modify them NOW to calm down NOW (yes I have scripts that depends on >> window size), and need to change my desktop configuration (including >> hardware layout ... to adapt to this). > > I was some days offline. I'll do some tests and see if I really broke > window remember feature. > > And this thread shows me that E is a hard maintainable monster! > Indeed :)
> I've really analysed the border code before I changed something and I > wrote around 20 test cases and requirements to analyse the situation > before I started. > > But no matter what I change there's always a stone with someone below > that has a strange use cases that doesn't longer work. > Sure, that's how it goes w/ code but one man's strange is another man's common :) > The E philosophy to make all strange use case owners happy and all other > "normal" users not is not a good decision in my eyes! Well, the problem here is, who decides what "normal" is ?? Again, one man's strange is another man's common. For example the > problem to have a configuration option for each and every stupid stuff. > I think this philosophy is on of the reasons for the "no release since > 10 years problem". But who asks me... > > I'm personally not sure if I'll ever change E code again in future! > I've to sleep about it! > > Sentences from you like above sounds like you're paying me money! > That's nerving me! > Yea, could have been said in a nicer way. > And yes, Gustavo was asking for help with fixing E bugs. And even if > you don't believe it, because it doesn't fit your use cases, the bugs I > try to fix are really nerving me! Sure, and that's why we as developers work on things ... to scratch our own itches :) You had some bugs that were nerving you, so you fixed them which is good :) The problem(s) come from in that process, other things broke :( Now, I am not saying one way is better than the other ! Each of us does things different than others. The issue is how do you define what a "normal" use case is ?? Someone else may have a different opinion about what is "normal". That being said, yes it's very difficult to make everyone happy in all situations but I believe that handling "most" cases is the best way to go. Don't let things like this discourage you from coding, just try your best to handle most use cases, and you'll be fine. Like a wise man once told me, "Around here, you have to develop a thick skin when coding" :) (eg: don't let the haters bother you) :) dh > > regards > Andreas > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
