I was also annoyed by the need to describe the changesets. Especially yesterday, when I had to do 5 attempts to upload a changeset - and every time I had to type in a description. So remembering the last description would make things easier.
And about the interface - I think it would be more logical to move the comment field to the upload window, where the added/changed/removed things are shown. First - it just economises time, as you have one "OK" button less in the upload dialog. Second - the changes are seen right away, so you can describe them more precisely. Best regards, Eugen > Date: Tue, 21 Apr 2009 22:27:55 +0100 > From: Matt Amos <zerebub...@gmail.com> > Subject: Re: [josm-dev] Commit message not empty > To: Pieren <pier...@gmail.com> > Cc: josm-dev <josm-dev@openstreetmap.org> > Message-ID: > <79d9e4e90904211427h33f0a904xd915acaddede4...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Apr 21, 2009 at 10:15 PM, Pieren <pier...@gmail.com> wrote: >> Forcing people to type a text in the commit message does not help OSM >> at all. It only generates such comments: >> >> >> ?#886027 ? ? ? ? (still editing) ? ? ? ? frolty ? ? ? ? ?bla bla >> >> Very helpful. >> Will JOSM be the only editor making this restriction ? > > or > 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 ;-) > > cheers, > > matt > > > > ------------------------------ > > Message: 12 > Date: Wed, 22 Apr 2009 01:20:20 +0200 > From: Frederik Ramm <frede...@remote.org> > Subject: Re: [josm-dev] Commit message not empty > To: Matt Amos <zerebub...@gmail.com> > Cc: josm-dev <josm-dev@openstreetmap.org> > Message-ID: <49ee54b4.2010...@remote.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 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 _______________________________________________ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev