Oliver,
On Wednesday, 2016-11-23 18:52:35 +0100, you wrote:
> ...
> Right. The core idea and expectation of open source is that the users
> find the bug, fix it and send a patch. But personally I wouldn't go that
> far.
Wrong. While I'm accepting that you "wouldn't go that far", I heartily
disagree with your statement that "the users find the bug, fix it and
send a patch" is the "core idea and expectation of open source".
Whatever open source product we are taking, you'll always find plenty of
users which are familiar with the application area (for instance GPS,
maps, tracks, and routes) but at the same time only few of these will be
familiar with whatever programming language you used to implement your
product. In other words: Whatever you do, there will only be few users
that measure up to YOUR expectations of what open source is all about.
We won't settle this argument, though. Either of us will have to live
with the other having a different opinion here due to different personal
experience.
> ...
> Try to request a feature at the GDAL and Proj4 projects.
My personal experience with both projects, Gdal and Proj, is quite diff-
erent from what you describe here. Its more like the experience I'm al-
so having with Mercurial.
Anyway, this fruitless debate about what is and what isn't the core idea
behind open source is totally distracting us from improving QMapShack.
Here's a (possibly incomplete) list of the things we did NOT discuss in
the recent past:
1. The "Points" tab in a track's "edit" view is a remnant from the old
"QLandkarte" software and does neither have any function nor does it
provide any information not also povided otherwise.
Therefore I suggested to completely drop the "Points" tab.
And in addition to currently providing this information above the
graphs in the Edit View I suggested to also provide it as balloon
help in the Map View when the mouse is hovering above a trackpoint.
2. With respect to globally assigning a color to an activity I asked you
to clarify what precisely "global" as implemented with, for instance,
the width specification CURRENTLY means:
* all existing tracks of the same project
* all tracks of the same project, including new ones
* all tracks, including new ones
And what precisely happens, when I specify a track width for "all"
tracks?
* Is it understood as a default
- just for new tracks?
- for all tracks which don't explicitly specify otherwise?
* Or does it override older track specific specifications?
Sincerely,
Rainer
------------------------------------------------------------------------------
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
