Sorry for the thread hijack, folks. I promise I'll get off my soapbox in a minute.
Having spent almost 20 years managing corporate software engineering I think I have a pretty good idea of what design features constitute a waste of engineering time (anyone ever work with a marketing dept. before?
), but of course your mileage may vary.
Originally Posted by richlo
This will show you why it seems like your not calm..Its how you deliver the message in writing..
"If people can't figure out how to convert inches to centimeters they probably shouldn't be building a theater in the first place"
I think my initial statement was fair. If a person can't convert imperial to metric they really shouldn't
be trying to build a theater! Simple mathematics is a rather basic skill involved in construction. Let's break it down a little:
1. Let's start with the premise that it takes roughly 12 hours to add a single feature to an application (as per Metrics and Models in Software Quality Engineering (2nd Edition)
by Stephen H. Kan). That includes design time, coding, GUI redesign to support the feature and alpha testing. It does NOT include beta testing time since on AVSForum that's likely to be completed by users. It also doesn't include recoding time to correct bugs. After all, I know Chris' coding style and he doesn't write bugs.
2. I ran the app and using the very first
link that Google came up with (http://www.helpwithdiy.com/metric_co...alculator.html
) converted my metric room dimensions to imperial. Time: approximately 90 seconds to convert plus 2 seconds for the Google search.
3. I took the results the app provided and using the 1' grid approximated the locations of my panels. Time: approximately 2 minutes.
4. I took these results and using the same metric conversion tool converted these results from imperial to metric. Time: approximately 60 seconds.
Total time: 4 minutes 32 seconds.
I don't care WHERE you're from (I'm originally from Europe, then 21 years in Canada, a number in the U.S. and most recently Japan for 4 years), if you expect the programmer to spend at least
12 hours of his time implementing this feature to save you the 4 minutes and 32 seconds it'll take you to do the conversions yourself you should really examine your priorities, because I think they're a little messed up. Just my opinion, of course.
Its a very fair request to add for Metric, if Chris doesnt, then he doesnt, but I think ALL Europeans will love to see this feature added...
To you, I'm sure, but that doesn't mean it's worth the time it would take away from other features in the program that I think are more important.
Let me put it this way: which would you rather see:
o Cathedral Ceilings, or metric conversion?
o Ability to setup speakers off-center in the room x-axis, or metric conversion?
o Ability to setup listener zones off-center in the room x-axis, or metric conversion?
o Ability to selectively disable listener zones, or metric conversion?
o GUI redesigned to support these features, or metric conversion?
o Sound passing through listeners to back wall and reflecting, resulting in more reflections shown on back wall, or metric conversion?
I personally think it's much
more important for Chris to provide support for the above-mentioned features than to add metric support. As I said in my initial post, there are hundreds of thousands of Google hits on 'imperial metric calculator'. In my opinion that's FAR less important than the feature list Chris posted.
Anyway, I'm not going to get any further into a flame war. You're entitled to ask for metric support, and I'm entitled to reply that I think it's a waste of time to add it when there are more important features to consider (again, my opinion).
If I invoke Godwin now that should end this, right?