Hi,
Matt Amos wrote:
> http://www.openstreetmap.org/browse/changeset/874667
> http://www.openstreetmap.org/browse/changeset/874868
> http://www.openstreetmap.org/browse/changeset/874786
> http://www.openstreetmap.org/browse/changeset/874869
> http://www.openstreetmap.org/browse/changeset/874960
>
> that guy seems to *really* not like putting comments in ;-)
It has been pointed out to me that JOSM should perhaps at least store
your previous comment and allow you to re-use it. That would make things
so much easier for this chap!
But honestly, what would you say from a user interface perspective;
should we try and keep changesets open? What JOSM currently does is open
changeset - upload - close, for each upoad action. Some people have a
habit of uploading once every five minutes and they are perhaps annoyed
to have to type in a comment each time (could be fixed by caching the
old comment), but thinking about later analysis of changesets it might
perhaps be desirable to add changes to an existing changeset.
Maybe so:
* user starts josm, edits
* uploads => gets asked for description => changeset created
* on next upload => JOSM makes GET request to see if changeset still
open on server => if yes, offers dialog box with radio buttons:
( ) continue existing edit session
commit message: [whatever was last typed, editable]
( ) start new edit session
commit message: [ ]
I see the possible problem of people always continuing the existing
session even if they are now doing something completely different...
Bye
Frederik
--
Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33"
_______________________________________________
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev
