Opened 11 years ago
Closed 10 years ago
#9907 closed enhancement (fixed)
When using remote control on osm.org download also note(s) if URL contains "/note/123456" or "&layers=N"
Reported by: | skyper | Owned by: | ToeBee |
---|---|---|---|
Priority: | normal | Milestone: | 15.04 |
Component: | Core notes | Version: | |
Keywords: | github | Cc: | iandees |
Attachments (0)
Change History (22)
comment:1 by , 11 years ago
Cc: | added |
---|
follow-up: 3 comment:2 by , 11 years ago
comment:3 by , 11 years ago
Replying to Don-vip:
Please create directly notes defect on Github.
The best would be to have them interact (e.g. https://stackoverflow.com/questions/6671584/how-to-export-trac-to-github-issues).
This solution could work for every maintainer interested in using github instead of trac.
follow-up: 5 comment:4 by , 11 years ago
Most of github josm plugins are either dead either very slowly updated. I won't waste my time to implement an automatic solution.
Hence I close those tickets from unaware users and switch them to github with a little hope that they may be fixed some day. I expect active users like you to directly create tickets there to minimize work for josm team.
Thanks for your comprehension.
comment:5 by , 11 years ago
Replying to Don-vip:
Most of github josm plugins are either dead either very slowly updated. I won't waste my time to implement an automatic solution.
Hence I close those tickets from unaware users and switch them to github with a little hope that they may be fixed some day. I expect active users like you to directly create tickets there to minimize work for josm team.
Thanks for your comprehension.
Hey, the solution I mentioned is using Trac's XML-RPC interface and I expected the plugin maintainers to run a cron job to get their issues. Likewise they could have some script to make a Trac comment linking to the new created issue and close the ticket in the same run they close their issues. Did not want to spend your time.
comment:6 by , 11 years ago
Keywords: | github added |
---|---|
Resolution: | → othersoftware |
Status: | new → closed |
I know :) but the point is, the simple presence of these tickets here causes a workload for us, so I'd prefer not to see them here in the first place.
=> upstream ticket: https://github.com/iandees/josm-notes/issues/23
comment:7 by , 10 years ago
Resolution: | othersoftware |
---|---|
Status: | closed → reopened |
This would be still an enhancement.
Not sure where it belongs to now as pasted into DownloadDialog below mentioned URLs behave the same atm
In fact, the note is not downloaded at all even with checkbox checked.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2014-12-11 02:33:43 Last Changed Author: Don-vip Revision: 7787 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Relative URL: ^/trunk URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2014-12-11 00:15:17 +0100 (Thu, 11 Dec 2014) Last Changed Rev: 7787 Identification: JOSM/1.5 (7787 en) Linux Debian GNU/Linux 7.7 (wheezy) Memory Usage: 344 MB / 882 MB (216 MB allocated, but free) Java version: 1.7.0_65, Oracle Corporation, OpenJDK 64-Bit Server VM Java package: openjdk-7-jre:amd64-7u71-2.5.3-2~deb7u1 VM arguments: [-Djosm.home=$HOME/.josm_notes] Program arguments: [--language=en, test.osn] Dataset consistency test: No problems found
comment:9 by , 10 years ago
Summary: | Download specific note → When using remote control on osm.org download also note(s) if URL contains "/note/123456" or "&layers=N" |
---|
follow-up: 21 comment:10 by , 10 years ago
Not sure if remote control is the only solution. Still prefer a solution to simply type/paste the note id like it is working with object ids.
comment:13 by , 10 years ago
Milestone: | → 15.04 |
---|
comment:16 by , 10 years ago
Remote control (the edit button on osm.org).
(I just tried open locaction, which works for me.)
Revision: 8199 Repository Root: http://josm.openstreetmap.de/svn Relative URL: ^/trunk Last Changed Author: simon04 Last Changed Date: 2015-04-15 23:51:33 +0200 (Wed, 15 Apr 2015) Build-Date: 2015-04-16 01:31:12 URL: http://josm.openstreetmap.de/svn/trunk Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last Changed Rev: 8199 Identification: JOSM/1.5 (8199 en) Windows 7 32-Bit Memory Usage: 742 MB / 742 MB (145 MB allocated, but free) Java version: 1.8.0_31, Oracle Corporation, Java HotSpot(TM) Client VM VM arguments: [-Djava.security.manager, -Djava.security.policy=file:C:\Program Files\Java\jre1.8.0_31\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=C:\Program Files\josm-latest-bla.jnlp, -Djnlpx.remove=true, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.heapsize=256m,768m, -Djnlpx.splashport=61388, -Djnlpx.jvm=<java.home>\bin\javaw.exe, -Djnlpx.vmargs=LURqYXZhLnV0aWwuQXJyYXlzLnVzZUxlZ2FjeU1lcmdlU29ydD10cnVlAA==] Dataset consistency test: No problems found
comment:17 by , 10 years ago
Concerning the edit button @osm.org: This calls http://127.0.0.1:8111/load_and_zoom?left=1&top=2&right=3&bottom=4 without any information about the active layers. So this would require a modification there (→ https://github.com/openstreetmap/openstreetmap-website/) plus an adoption of the /load_and_zoom
handler (this currently calls the standard DownloadOsmTask
in any case).
comment:19 by , 10 years ago
I created an issue https://github.com/openstreetmap/openstreetmap-website/issues/957
comment:21 by , 10 years ago
comment:22 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
The outstanding part is split to #11367, so this ticket is fixed. :)
Please create directly notes defect on Github.