Opened 7 years ago
Closed 7 years ago
#12344 closed enhancement (othersoftware)
session support for todo plugin
Reported by: | naoliv | Owned by: | Gnonthgol |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin todo | Version: | |
Keywords: | session github | Cc: |
Description
Sometimes I am editing some data with pending tasks in TODO and some commented or "closed" notes (not yet sent, since the data isn't uploaded).
Then, I need to locally save what I am doing and close JOSM, but with one problem: every pending task is lost and every pending note is also lost.
Could we have some way to save the status of some plugins together with the osm file, so the user could continue the tasks and notes from where he has stopped, without needing to find them again or upload some incomplete objects, please?
Attachments (0)
Change History (4)
comment:1 follow-up: 3 Changed 7 years ago by
Component: | Core → Plugin todo |
---|---|
Keywords: | session added |
Owner: | changed from team to Gnonthgol |
Summary: | Save plugins state together with the osm file → session support for todo plugin |
comment:2 Changed 7 years ago by
Keywords: | github added |
---|
TODO plugin is unmaintained, see https://github.com/Gnonthgol/JOSM-todo
Creating tickets on Trac is useless, can you please file a Github issue instead?
comment:3 Changed 7 years ago by
Replying to bastiK:
Please make only requests for one plugin / component per ticket!
I thought that saving all the session info/data was something internal to JOSM (and that is why I did open it against JOSM itself, and not individually for each component).
I will open an issue in JOSM-todo's github and another one against Core notes
later.
comment:4 Changed 7 years ago by
Resolution: | → othersoftware |
---|---|
Status: | new → closed |
Please make only requests for one plugin / component per ticket! We have a system in JOSM to save and reopen the entire editing session. Currently this feature mainly focuses on layers. Saving the todo list would be in that spirit, but will probably require some extensions in JOSM core.
A session file is a zip archive with one "bookkeeping" file (session.jos) and several data files in it. What will be required for this, is a way to export the todo list to a data file and load it back from file (since large amounts of data should not be stored in the main "bookkeeping" xml file).