Hi
I'm thrilled developement goes on in good speed and central issues
like conflict resolution have been already touched.
Unfortunatelly end user documentation stays far behind. While simpler
functions can be documented by experienced users, I fear the field of
conflict resolution in JOSM is a
Hi Rolf,
point taken, it's indeed necessary to get the documentation updated.
But please also keep the actual users in mind when designing the UI, at
least give the buttons some meaningful tooltips.
Suggestions would be welcome. Which buttons should have better tooltip
texts? What texts?
On Sun, 4 Oct 2009, Rolf Bode-Meyer wrote:
There was a post just yesterday where some people agree that they just
push the buttons at random until the conflict is either resolved or the
changes completely messed up.
Users always request better documentation, but when there is a good
2009/10/4 Dirk Stöcker openstreet...@dstoecker.de:
Asking specific questions here like what does that button do can help to
solve troubles and the explanations can be copied into a doc.
What does the 'Reload' button in the selection side dialogue do?
Ciao André
It resets the list of objects displayed in the Selection Toggle Dialog to the
list of currently selected objects,
although the Selection Toggle Dialog is supposed to always display the list
of currently selected objects.
We should remove the button, it looks silly.
-- Karl
On Sun, Oct 4, 2009 at 9:18 AM, Dirk Stöcker openstreet...@dstoecker.de wrote:
On Sun, 4 Oct 2009, Rolf Bode-Meyer wrote:
There was a post just yesterday where some people agree that they just
push the buttons at random until the conflict is either resolved or the
changes completely messed
On Sun, 4 Oct 2009, Karl Guggisberg wrote:
It resets the list of objects displayed in the Selection Toggle Dialog to
the list of currently selected objects,
although the Selection Toggle Dialog is supposed to always display the list
of currently selected objects.
We should remove the
On Sun, 4 Oct 2009, Ævar Arnfjörð Bjarmason wrote:
Perhaps it would help if there was a way in JOSM to link from each
dialog / logical part of the UI to the associated documentation page.
Then you could always click Help (for this dialog) to get at the
documentation.
Press F1 above a feature
Dirk Stöcker schrieb:
On Sun, 4 Oct 2009, Ævar Arnfjörð Bjarmason wrote:
Perhaps it would help if there was a way in JOSM to link from each
dialog / logical part of the UI to the associated documentation page.
Then you could always click Help (for this dialog) to get at the
documentation.
On 04/10/2009 10:18, Dirk Stöcker wrote:
Till now I was not able to convince one single person to really update
JOSM online docs (with more than typos), so it seems doing that work is
not worth the effort.
I documented the whole of Audio mapping in detail for the JOSM help (and
in passing
I've fixed #2480 by replacing LinkedList with ConcurrentLinkedQueue
(or at least I hope so, I don't have gps device with me to test it).
Just a few thoughs about threading issues...
Making data structures thread safe does not necessary mean big
synchronization overhead. For example
On Sun, 4 Oct 2009, Ulf Lamping wrote:
JOSM translation shows that users are taking care if the hurdle for a
first start isn't too high. Me feeling is that the help system
The number of translators is so low, that I fear that does not qualify as
real good example of user help. Also only about
This is like the improvements in history dialog. One trac ticket with a
simple suggestion caused Karl to make
the history dialog much more understandable. It's not always that easy,
but sometimes such hints can do miracles.
Agree completely. We benefit from as precise suggestions as possible.
2009/10/4 Martin Koppenhoefer dieterdre...@gmail.com:
2009/10/4 André Riedel riedel.an...@gmail.com:
2009/10/4 Martin Koppenhoefer dieterdre...@gmail.com:
there is also these 2 empty layers (czech hiking and another useless
data one) that clutter the layer-section for some time now.
That is
On Sun, 4 Oct 2009, Karl Guggisberg wrote:
No. All my experience shows that this is untrue. People either help or
they don't help.
This goes along with my experience but the interesting point is how to find
those who want to help. What do you have to do to attract people who would
like to
Josm Docu isn't really important. most functions are self explaining.
What we really need is to understand what Josm does with the data and how
this working with the API and the whole OSM database. Conflict resolution or
history functionality are such topics where good docu or tutorials can help.
On 04/10/2009 18:39, Apollinaris Schoell wrote:
Josm Docu isn't really important. most functions are self explaining.
Absolute nonsense. Just look at the comments new people make - they are
overwhelmed and confused by JOSM. It's only self explaining if either
you already know what you're doing
On Sun, 4 Oct 2009, Rolf Bode-Meyer wrote:
So please would those people who implemented conflict handling give
detailed explanations in [[Help/Dialog/Conflict]] which currently is
simply not helpful?
You really need no programmer to write documentation.
A good way to reach that goal would
On Sun, 4 Oct 2009, David Earl wrote:
Josm Docu isn't really important. most functions are self explaining.
Absolute nonsense. Just look at the comments new people make - they are
overwhelmed and confused by JOSM. It's only self explaining if either
you already know what you're doing or if
On Sun, 4 Oct 2009, Apollinaris Schoell wrote:
But as said before this is NOT a task for the developers. It's not even a
Josm problem.
My problem in the last months was that the development was too fast to even
catch up with the idea how things work. With a couple of bugs impossible.
The
Dirk Stöcker schrieb:
On Sun, 4 Oct 2009, Rolf Bode-Meyer wrote:
So please would those people who implemented conflict handling give
detailed explanations in [[Help/Dialog/Conflict]] which currently is
simply not helpful?
You really need no programmer to write documentation.
A good way to
Karl could simply write down in a few sentences how the common workflows
are to be done. No fancy screenshots
or text formatting, so it can be done in less than 10mins. BTW: When you
try to write it down, you'll probably
already found some design mistakes :-)
Sure. I today dig into the
22 matches
Mail list logo
