You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: dan[at]karran.net [Submitted to the original trac issue database at 12.32pm, Sunday, 5th July 2009]
It'd be nice to be able to edit tags when viewing objects in the data browser, allowing users to make quick changes to tags when they spot mistakes, add new tags, or remove erroneous ones.
An edit button could switch the list of tags to be form fields, with a button to save changes to a currently open changeset (started on a user's first edit through the site, added to with subsequent ones within the allowed time period). When saved, the page should refresh to show the latest version of the object per their changes.
Perhaps we could also allow the editing of node locations in a similar fashion.
The text was updated successfully, but these errors were encountered:
Author: tom[at]compton.nu [Added to the original trac issue at 11.10pm, Sunday, 5th July 2009]
I'm not sure we really want to start getting into providing an HTML/JS editor by the back door like this. I'd rather leave that to somebody to develop as a project than start introducing it incrementally by the back door.
Reporter: dan[at]karran.net
[Submitted to the original trac issue database at 12.32pm, Sunday, 5th July 2009]
It'd be nice to be able to edit tags when viewing objects in the data browser, allowing users to make quick changes to tags when they spot mistakes, add new tags, or remove erroneous ones.
An edit button could switch the list of tags to be form fields, with a button to save changes to a currently open changeset (started on a user's first edit through the site, added to with subsequent ones within the allowed time period). When saved, the page should refresh to show the latest version of the object per their changes.
Perhaps we could also allow the editing of node locations in a similar fashion.
The text was updated successfully, but these errors were encountered: