Oliver, On Tuesday, 2016-11-22 18:24:29 +0100, you wrote:
> ... > First, QMS is open source licensed under GPL3. This is not public domain > at all. You're perfectly right. Being in this software business for umpteen years now I do in fact know the difference, even if I off and on happen to use an incorrect term. > And open source does not mean: Everybody wishes and one has to > implement the stuff. You're perfectly right again. But as well "open source" does not mean: The developers develop software just for their own purposes and the sole task of the users downloading the software is to find the bugs the dev- elopers failed to prevent in the first place. Just take the list of QMapShack's prerequisites: NetCDF, Proj, Gdal, or Mercurial. These all are prospering open source projects with strong communities consisting of at least core developers, occasional develop- ers, and plain users. And it's mainly these plain users which give the necessary feedback about features not applicable in the wild, unergonom- ic features, and also missing features. That way they help honing rough edges of the product and thus they help improving it. Sure, the plain users directly benefit from missing features being added, but so do the developers by being able to provide a better product. Thus, feed-back in the form of bug reports, comments on the usability of certain features, or enhancement requests is as valuable a contribution to an open source product as code lines are. If you just want a product for your own purpose, if you feel annoyed when someone is suggesting a new feature, why did you start your product as open source at all? I'm sure you, too, wanted to have a good, a us- able product. And that's something you are needing the plain users for. > > When I ran into this trackpoint list for the first time, I too was ask- > > ing myself, what the heck is that list good for. > > ... > > It's there because if it wouldn't be there everyone would ask why it is > missing. ;) That's not an answer. At least not if you want a sincere discussion. > ... > Let's look at the information you usually select a range: > ... > * Elevation. I use the range selection to measure slopes. Instead of > finding the local extrema in a list I simply select two points in the > profile. It's way easier. > > * Speed. This is often used when selecting activities. Again it's much > easier for me to find that stuff in the speed graph than in some endless > list. > > If I would really miss that selection via list I would have already > implemented it. I'm under the strong impression that you're completely missing my point. I suggested to DROP this list! I pointed out that this information is already displayed above the graphs for the trackpoint the mouse is hov- ering over. I only suggested to also display this information as ball- oon help when the mouse is hovering over some track point in the map view. Sincerely, Rainer ------------------------------------------------------------------------------ _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
