#18845 closed enhancement (fixed)
reorganization of data(_nodist), images(_nodist), styles(_nodist), IDE and native files in a more practical file tree
Reported by: | simon04 | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | 20.03 |
Component: | Core | Version: | |
Keywords: | repository resources | Cc: | Don-vip, skyper, stoecker, Klumbumbus, leni, DiGro |
Description
Replying to Don-vip:
In 16006/josm:
see #18140 - reorganization of data(_nodist), images(_nodist), styles(_nodist), IDE and native files in a more practical file tree.
- Everything belonging to the jar is now in resources (data, images, styles)
- Everything not belonging to the jar is now in nodist (data, images, styles)
- Everything related to OS native functions is now in native (linux, macosx, windows)
- Everything related to an IDE is now in ide (eclipse, netbeans)
Attachments (1)
Change History (109)
comment:1 by , 5 years ago
follow-up: 4 comment:2 by , 5 years ago
Keywords: | repository resources added |
---|
Since we have to update the i18n process (i18n.install.dir
in i18n/build.xml) anyways, should we move the .lang
files to a separate directory, such as resources/data/i18n
?
follow-ups: 5 20 comment:3 by , 5 years ago
skyper in 18140#comment:36:
So all icon pathes in the wiki need to be adjusted.
stoecker in 18140#comment:37:
We probably can do this semi-automatic.
Also, the Trac logo URL needs to be updated.
follow-up: 21 comment:4 by , 5 years ago
Replying to simon04:
Since we have to update the i18n process (
i18n.install.dir
in i18n/build.xml) anyways, should we move the.lang
files to a separate directory, such asresources/data/i18n
?
That would be bad as it would affects all plugins.
follow-ups: 14 15 16 comment:5 by , 5 years ago
Cc: | added |
---|
Replying to simon04:
skyper in 18140#comment:36:
So all icon pathes in the wiki need to be adjusted.
stoecker in 18140#comment:37:
We probably can do this semi-automatic.
Question is: Do we want to take that chance to replace the image macro with an JOSM specific one, so that it auto-detects PNG/SVG and references directly to the JOSM image dir?
Also, the Trac logo URL needs to be updated.
Done.
comment:7 by , 5 years ago
Cc: | added |
---|
comment:8 by , 5 years ago
Main logo on front page is currently 404.
Fixed.
@Vincent: I hope you know what a can of worms you opened with the reorganisation?
comment:9 by , 5 years ago
@leni: Please use tickets and not the SPAM report feature to report issues with the wiki.
follow-up: 11 comment:10 by , 5 years ago
@stoecker someone told me to use SPAM report for image... when to use it? only for attachments?
comment:11 by , 5 years ago
Replying to leni:
@stoecker someone told me to use SPAM report for image... when to use it? only for attachments?
SPAM report should be used when the result is an admin deleting the "offending" stuff (i.e. you may also use it e.g. for accidentially created pages or obsolete images to get rid off or alike). Deleting is the only possible action. Everything else which may need feedback is better done via ticket.
follow-up: 22 comment:12 by , 5 years ago
@Dirk yes I know. This is something I wanted to do for a long time and never did because of fear of the worms. I have found enough courage to do it now Did I broke the i18n or not? I forgot about it yesterday.
follow-up: 34 comment:13 by , 5 years ago
The command
ant clean dist
no longer works with r16010 or newer, probably one of the recent changes made for this ticket.
epsg-compile: [mkdir] Created dir: C:\josm\core\build2 [javac] Compiling 1 source file to C:\josm\core\build2 epsg: [touch] Creating C:\josm\core\resources\data\projection\custom-epsg [java] Exception in thread "main" java.lang.ExceptionInInitializerError [java] at BuildProjectionDefinitions.initMap(BuildProjectionDefinitions.java:91) [java] at BuildProjectionDefinitions.buildList(BuildProjectionDefinitions.java:109) [java] at BuildProjectionDefinitions.main(BuildProjectionDefinitions.java:77) [java] Caused by: org.openstreetmap.josm.tools.JosmRuntimeException: java.io.IOException: Failed to open input stream for resource 'resource://data/projection/custom-epsg' [java] at org.openstreetmap.josm.data.projection.Projections.<clinit>(Projections.java:175) [java] ... 3 more [java] Caused by: java.io.IOException: Failed to open input stream for resource 'resource://data/projection/custom-epsg' [java] at org.openstreetmap.josm.io.CachedFile.lambda$getInputStream$0(CachedFile.java:231) [java] at java.util.Optional.orElseThrow(Optional.java:290) [java] at org.openstreetmap.josm.io.CachedFile.getInputStream(CachedFile.java:231) [java] at org.openstreetmap.josm.io.CachedFile.getContentReader(CachedFile.java:258) [java] at org.openstreetmap.josm.data.projection.Projections.loadProjectionDefinitions(Projections.java:301) [java] at org.openstreetmap.josm.data.projection.Projections.<clinit>(Projections.java:170) [java] ... 3 more BUILD FAILED C:\josm\core\build.xml:1046: Java returned: 1
comment:14 by , 5 years ago
Question is: Do we want to take that chance to replace the image macro with an JOSM specific one, so that it auto-detects PNG/SVG and references directly to the JOSM image dir?
comments?
follow-up: 18 comment:15 by , 5 years ago
Replying to stoecker:
Question is: Do we want to take that chance to replace the image macro with an JOSM specific one, so that it auto-detects PNG/SVG and references directly to the JOSM image dir?
+1
- there is no image dir but some within trunk, some in the wiki like (external) presets and many elsewhere, including (external) presets and plugins.
- personally the name of the icon is my major problem when searching, the path is only minor priority.
follow-up: 17 comment:16 by , 5 years ago
Replying to stoecker:
Question is: Do we want to take that chance to replace the image macro with an JOSM specific one, so that it auto-detects PNG/SVG and references directly to the JOSM image dir?
Yes, that would definitely reduce work load after changes of #15240.
Would the internal help browser manage it well? Would it create lots of more work if we leave trac one day?
follow-up: 19 comment:17 by , 5 years ago
Replying to Klumbumbus:
Replying to stoecker:
Question is: Do we want to take that chance to replace the image macro with an JOSM specific one, so that it auto-detects PNG/SVG and references directly to the JOSM image dir?
Yes, that would definitely reduce work load after changes of #15240.
I'll have a look then.
Would the internal help browser manage it well?
Yes. It does not know of the wiki language, it reads HTML.
Would it create lots of more work if we leave trac one day?
Well, that would be so much work, that I don't consider it at all. Staying on an old trac version is the much easier choice.
comment:18 by , 5 years ago
Replying to skyper:
Replying to stoecker:
Question is: Do we want to take that chance to replace the image macro with an JOSM specific one, so that it auto-detects PNG/SVG and references directly to the JOSM image dir?
+1
- there is no image dir but some within trunk, some in the wiki like (external) presets and many elsewhere, including (external) presets and plugins.
This is only for JOSM images, i.e. these which are accessed with "source:...". The main idea is to make them behave like JOSM does with auto-detection of image extension. Everything else will be unchanged.
comment:19 by , 5 years ago
Replying to stoecker:
Would it create lots of more work if we leave trac one day?
Well, that would be so much work, that I don't consider it at all. Staying on an old trac version is the much easier choice.
OK (I thought if we switch from svn to git we would leave trac entirely.)
follow-up: 27 comment:20 by , 5 years ago
stoecker in 18140#comment:37:
We probably can do this semi-automatic.
Rather are forced to as updating the links is not doable manually https://josm.openstreetmap.de/search?q=Image%28source%3Atrunk%2Fimages
1k pages, so probably 10k links :)
follow-up: 23 comment:21 by , 5 years ago
Replying to stoecker:
Replying to simon04:
Since we have to update the i18n process (
i18n.install.dir
in i18n/build.xml) anyways, should we move the.lang
files to a separate directory, such asresources/data/i18n
?
That would be bad as it would affects all plugins.
The Ant task plugintrans
runs i18n.pl [...] --basedir=${plugin.dir}/${dir}/data/
, thus, plugins are unaffected from changing ${i18n.install.dir}
which is only used in the task coretrans
.
follow-up: 40 comment:22 by , 5 years ago
Replying to Don-vip:
Did I broke the i18n or not?
What do you think?
[o35345:35346]
I forgot about it yesterday.
And many many more... :-)
follow-up: 26 comment:23 by , 5 years ago
Replying to simon04:
Replying to stoecker:
Replying to simon04:
Since we have to update the i18n process (
i18n.install.dir
in i18n/build.xml) anyways, should we move the.lang
files to a separate directory, such asresources/data/i18n
?
That would be bad as it would affects all plugins.
The Ant task
plugintrans
runsi18n.pl [...] --basedir=${plugin.dir}/${dir}/data/
, thus, plugins are unaffected from changing${i18n.install.dir}
which is only used in the taskcoretrans
.
Please stop thinking only from source side. If we change the directory where translations are stored then we also need to do this for the plugins, as core and plugins use the same mechanisms. And having different places for source and final jar would actually be opposite to what is the goal of this directory change so that's also no option.
follow-up: 35 comment:26 by , 5 years ago
Replying to stoecker:
Please stop thinking only from source side.
Ups, I was just preparing my commits and overlooked your reply…
If we change the directory where translations are stored then we also need to do this for the plugins, as core and plugins use the same mechanisms.
Actually not, see https://josm.openstreetmap.de/changeset/16012/josm/trunk/src/org/openstreetmap/josm/tools/I18n.java
If the move to resources/data/trans/
is not an option, I'm going to revert my changes.
For i18n: [o35347], [o35348].
follow-ups: 49 50 comment:27 by , 5 years ago
Replying to Klumbumbus:
stoecker in 18140#comment:37:
We probably can do this semi-automatic.
Rather are forced to as updating the links is not doable manually https://josm.openstreetmap.de/search?q=Image%28source%3Atrunk%2Fimages
1k pages, so probably 10k links :)
Another thing to consider: even if all image paths were updated semi automatic then the revision of all translated pages will be outdated. In best case the revision of the translated page would be increased by one during the image path update in case the translated page was up to date before. And do not increase if the page was outdated already before. Not sure if this is possible.
follow-up: 31 comment:30 by , 5 years ago
JOSM imagery pages can't be edited.
Warnung: Ungültige Wiki-Seite: XML validation for map failed: [Errno 2] No such file or directory: '/home/josm/auto/svn_josm/core/data/maps.xsd'
follow-up: 37 comment:31 by , 5 years ago
Replying to Klumbumbus:
JOSM imagery pages can't be edited.
Warnung: Ungültige Wiki-Seite: XML validation for map failed: [Errno 2] No such file or directory: '/home/josm/auto/svn_josm/core/data/maps.xsd'
Yes. Found it a few seconds ago. Fixed?
comment:32 by , 5 years ago
I think the important parts on the server side should be fixed now. We'll see tomorrow when latest is built.
comment:34 by , 5 years ago
Replying to GerdP:
The command
ant clean distno longer works with r16010 or newer, probably one of the recent changes made for this ticket.
epsg-compile: [mkdir] Created dir: C:\josm\core\build2 [javac] Compiling 1 source file to C:\josm\core\build2 epsg: [touch] Creating C:\josm\core\resources\data\projection\custom-epsg [java] Exception in thread "main" java.lang.ExceptionInInitializerError [java] at BuildProjectionDefinitions.initMap(BuildProjectionDefinitions.java:91) [java] at BuildProjectionDefinitions.buildList(BuildProjectionDefinitions.java:109) [java] at BuildProjectionDefinitions.main(BuildProjectionDefinitions.java:77) [java] Caused by: org.openstreetmap.josm.tools.JosmRuntimeException: java.io.IOException: Failed to open input stream for resource 'resource://data/projection/custom-epsg' [java] at org.openstreetmap.josm.data.projection.Projections.<clinit>(Projections.java:175) [java] ... 3 more [java] Caused by: java.io.IOException: Failed to open input stream for resource 'resource://data/projection/custom-epsg' [java] at org.openstreetmap.josm.io.CachedFile.lambda$getInputStream$0(CachedFile.java:231) [java] at java.util.Optional.orElseThrow(Optional.java:290) [java] at org.openstreetmap.josm.io.CachedFile.getInputStream(CachedFile.java:231) [java] at org.openstreetmap.josm.io.CachedFile.getContentReader(CachedFile.java:258) [java] at org.openstreetmap.josm.data.projection.Projections.loadProjectionDefinitions(Projections.java:301) [java] at org.openstreetmap.josm.data.projection.Projections.<clinit>(Projections.java:170) [java] ... 3 more BUILD FAILED C:\josm\core\build.xml:1046: Java returned: 1
Probably caused by me: I've manually removed \data\projection\custom-epsg
With a clean checkout you should see the same problem.
comment:35 by , 5 years ago
Replying to simon04:
Replying to stoecker:
Please stop thinking only from source side.
Ups, I was just preparing my commits and overlooked your reply…
@stoecker, I didn't mean to overrule you. After investigating comment:21, I was preparing my commits and didn't check for new comments on this issue. Only after committing, I've read your reply.
follow-up: 41 comment:36 by , 5 years ago
@Vincent: Most of the big worm are back inside, happy hunting for the smaller ones ;-)
comment:37 by , 5 years ago
Replying to stoecker:
Replying to Klumbumbus:
JOSM imagery pages can't be edited.
Warnung: Ungültige Wiki-Seite: XML validation for map failed: [Errno 2] No such file or directory: '/home/josm/auto/svn_josm/core/data/maps.xsd'
Yes. Found it a few seconds ago. Fixed?
Yes.
comment:40 by , 5 years ago
Replying to stoecker:
Replying to Don-vip:
Did I broke the i18n or not?
What do you think?
By "broken" I was afraid to have uploaded to Launchpad incomplete translations, thus deleting thousands of translated strings. I'm relieved it didn't happen this way.
And many many more... :-)
Thanks for the help! :)
comment:41 by , 5 years ago
Replying to stoecker:
@Vincent: Most of the big worm are back inside, happy hunting for the smaller ones ;-)
Thanks! I'm on it :)
follow-up: 45 comment:42 by , 5 years ago
There are two failing tests, https://josm.openstreetmap.de/jenkins/job/JOSM/lastCompletedBuild/testReport/:
- org.openstreetmap.josm.data.VersionTest.testGetAgentString
- org.openstreetmap.josm.data.validation.tests.MapCSSTagCheckerTest.testPreprocessing
follow-up: 47 comment:45 by , 5 years ago
Replying to simon04:
- org.openstreetmap.josm.data.VersionTest.testGetAgentString
Fixed, my fault.
- org.openstreetmap.josm.data.validation.tests.MapCSSTagCheckerTest.testPreprocessing
This one I don't understand. The test is OK for me. Do you have an idea?
comment:46 by , 5 years ago
comment:47 by , 5 years ago
Replying to Don-vip:
Replying to simon04:
- org.openstreetmap.josm.data.VersionTest.testGetAgentString
Fixed, my fault.
- org.openstreetmap.josm.data.validation.tests.MapCSSTagCheckerTest.testPreprocessing
This one I don't understand. The test is OK for me. Do you have an idea?
IIGTR target test is missing a dependency on create-revision.
I can reproduce the problem with a clean checkout and
ant compile-test ant -Ddefault-junit-includes="**/**/MapCSSTag*Test.class" test
After this the needed file REVISION is missing in the build directory.
comment:49 by , 5 years ago
Replying to
stoecker: ... replace the image macro with an JOSM specific on ?
Replying to Klumbumbus:
1k pages, so probably 10k links :)
if all image paths were updated semi automatic, then the revision of all translated pages will be outdated. ...
A semiautomated solution for the wiki image source links seems fine. The active translators can handle this. For the non active it is unimportant if a page is 20 or 21 versions behind.
Please inform how the decision is. If it is still open, please give notice too.
comment:50 by , 5 years ago
My plan currently is:
- Get the new link-variant working for tests (today)
- extract the what-to-change list from the SQL directly
- update my "automatically overflood trac with hundred requests script" to change the pages accordingly (As requested updating the translated pages revsion by one when applicable)
- start the script
- present all the broken links found during this process for manual fixing.
follow-ups: 56 59 61 comment:51 by , 5 years ago
Please try:
[[JOSMImage(openlocation)]] [[JOSMImage(audio-fwd)]]
See docs at WikiMacros#JOSMImage-macro
Please test.
comment:52 by , 5 years ago
Replying to GerdP:
In 16028/josm:
I removed the test-compile dependency on "dist" especially to avoid the call to create-revision, as it causes problems with the server Makefile. I will try to see why this test needs the REVISION file, it's strange.
follow-up: 57 comment:56 by , 5 years ago
Replying to stoecker:
Please test.
inline
seems to not work:
heading
text
heading
text
Can't really test @rev
as all images were moved, however I think there is not a single usage of that code in the wiki anyway.
comment:57 by , 5 years ago
Replying to Klumbumbus:
Replying to stoecker:
Please test.
inline
seems to not work:
heading
text
heading
text
Really :-)
Can't really test
@rev
as all images were moved, however I think there is not a single usage of that code in the wiki anyway.
That makes no sense anyway. If you have a specific revision you can use the normal macro, as this revision will never change.
follow-up: 60 comment:59 by , 5 years ago
Replying to stoecker:
The png is fine, but the svg image audio-fwd is not shown in JOSM Help browser, neither as block nor inline. But this may be related to the help system and not to the new macro.
comment:60 by , 5 years ago
follow-up: 62 comment:61 by , 5 years ago
Replying to stoecker:
...
Please test.
Mmh, should [[JOSMImage(relation)]]
work () or only
[[JOSMImage(data/relation)]]
() ?
follow-up: 63 comment:62 by , 5 years ago
Replying to skyper:
Mmh, should
[[JOSMImage(relation)]]
work () or only
[[JOSMImage(data/relation)]]
() ?
See docs: WikiMacros#JOSMImage-macro: The first parameter is a path inside trunk/resources/images/ without the extension. So the first can't work, as there is no relation.xxx inside the path.
follow-up: 64 comment:63 by , 5 years ago
Replying to Klumbumbus:
All image types are fine after updating to 1.8.0_242-b08, AdoptOpenJDK, OpenJDK 64-Bit Server VM.
Replying to stoecker:
The first parameter is a path inside trunk/resources/images/ without the extension.
I chocked on that sentence too. Suggestion:
The first parameter is a file path starting at trunk/resources/images/ without the extension.
follow-up: 74 comment:64 by , 5 years ago
Replying to Hb---:
The first parameter is a file path starting at trunk/resources/images/ without the extension.
Well, saying "file path" is same for me as saying "female woman". That's implied. I changed the inside: The first parameter is a path in the directory
follow-up: 66 comment:65 by , 5 years ago
We should probably not change image links like in https://josm.openstreetmap.de/wiki/Help/Menu/Help?action=diff&version=38 and https://josm.openstreetmap.de/wiki/De%3AHelp/Menu/Help?action=diff&version=23 as this might complicate the planned semiautomatic update. The goal is anyway not [[Image(source:/trunk/resources/images/dialogs/search.png)]]
but
[[JOSMImage(dialogs/search)]]
Dirk?
comment:66 by , 5 years ago
Replying to Klumbumbus:
We should probably not change image links like in https://josm.openstreetmap.de/wiki/Help/Menu/Help?action=diff&version=38 and https://josm.openstreetmap.de/wiki/De%3AHelp/Menu/Help?action=diff&version=23 as this might complicate the planned semiautomatic update.
I have no issue with that. Manual fixes simply mean that the script has to do less ;-)
The goal is anyway not
[[Image(source:/trunk/resources/images/dialogs/search.png)]]
These case will also be converted to JOSMImage macro when found.
but
![]()
[[JOSMImage(dialogs/search)]]
Dirk?
I hope I find time this weekend for this task.
follow-up: 71 comment:67 by , 5 years ago
I get Warnung: Ungültige Wiki-Seite: XML validation for style failed: [Errno 2] No such file or directory: '/home/josm/auto/svn_josm/core/resources/data/mappaint-style.xsd'
when trying to edit wiki:/Styles/LegacyStandard
comment:71 by , 5 years ago
Replying to Klumbumbus:
I get
Warnung: Ungültige Wiki-Seite: XML validation for style failed: [Errno 2] No such file or directory: '/home/josm/auto/svn_josm/core/resources/data/mappaint-style.xsd'
when trying to edit wiki:/Styles/LegacyStandard
Oh, that bug must be there for a long time. Fixed it.
comment:73 by , 5 years ago
there are two different images for the validator: in dialogs directory and in preferences directory
I modified https://josm.openstreetmap.de/wiki/Rules by changing the macro for the Validator image; I replaced the "image" macro by the "JOSMImage" macro without modifying either the directory or the original parameters:
at the top of the page from dialogs directory with parameter (dialogs/validator,middle,margin-right=20)
and after the table from preferences directory with parameter (preferences/validator,15)
but the display is different between wiki and JOSM Help browser :
in the wiki page the result is as above; when in JOSM Help browser first image is smaller than the second one.
I use W10 and Firefox
comment:74 by , 5 years ago
Replying to leni:
On the Rules page the first occurrence of the image had no width attribute.
But it did have a style attribute (middle) which the second has not. This may be the cause. Additionally the image resizing in the Help browser has at least one bug #15864.
Replying to stoecker:
... saying "file path" is same for me as saying "female woman". That's implied.
Well, that Redmond OS had blown this fact away from me.
by , 5 years ago
Attachment: | wiki_HelpWindow.png added |
---|
differents Rules Validator - wiki and JOSM Help browser
comment:75 by , 5 years ago
Replying to Hb---:
Replying to leni:
On the Rules page the first occurrence of the image had no width attribute.
But it did have a style attribute (middle) which the second has not. This may be the cause.
The change you made in the rules page didn't change anything, it wasn't meant to be that.
Additionally the image resizing in the Help browser has at least one bug #15864.
Sorry, it must be a duplicate with #15864 (I joined image)
comment:76 by , 5 years ago
Cc: | added |
---|
follow-up: 79 comment:77 by , 5 years ago
@ Dirk:
Sorry, totally forgot about it but it would be nice if link=
could be automatically set and be overridden with a value if needed. Also middle
would be nice as default. Right now, you have to added it to almost every image.
follow-up: 82 comment:79 by , 5 years ago
Replying to skyper:
@ Dirk:
Sorry, totally forgot about it but it would be nice if
link=
could be automatically set and be overridden with a value if needed. Alsomiddle
would be nice as default. Right now, you have to added it to almost every image.
I'm no magician. I can do straightforward changes with such a script, but no complicated argument handling. Now it's to late anyway.
follow-up: 96 comment:80 by , 5 years ago
Either my script had an error in the detection or there are really no dead image links anywhere (any png/svg issue was fixed automatically).
follow-up: 83 comment:81 by , 5 years ago
Replying to stoecker:
Hah, even that 1430 points cheat code didn't bring you the first place at https://josm.openstreetmap.de/stats/wiki#EditsByAuthor ;)
follow-up: 84 comment:82 by , 5 years ago
Replying to stoecker:
Replying to skyper:
@ Dirk:
Sorry, totally forgot about it but it would be nice if
link=
could be automatically set and be overridden with a value if needed. Alsomiddle
would be nice as default. Right now, you have to added it to almost every image.
I'm no magician. I can do straightforward changes with such a script, but no complicated argument handling. Now it's to late anyway.
I can add "middle,link=" as default argument to JOSMImage() when no arguments are given. Would that be fine? Klumbumbus?
follow-up: 86 comment:83 by , 5 years ago
Replying to Klumbumbus:
Replying to stoecker:
Hah, even that 1430 points cheat code didn't bring you the first place at https://josm.openstreetmap.de/stats/wiki#EditsByAuthor ;)
Well, in the second column I am :-)
follow-up: 85 comment:84 by , 5 years ago
Replying to stoecker:
I can add "middle,link=" as default argument to JOSMImage() when no arguments are given. Would that be fine? Klumbumbus?
I think so.
follow-up: 87 comment:85 by , 5 years ago
Replying to Klumbumbus:
Replying to stoecker:
I can add "middle,link=" as default argument to JOSMImage() when no arguments are given. Would that be fine? Klumbumbus?
I think so.
That is what I had in mind.
comment:86 by , 5 years ago
Replying to stoecker:
Replying to Klumbumbus:
Replying to stoecker:
Hah, even that 1430 points cheat code didn't bring you the first place at https://josm.openstreetmap.de/stats/wiki#EditsByAuthor ;)
Well, in the second column I am :-)
Would you mind, to give me the user right to view the stats, again. Thanks
comment:87 by , 5 years ago
Replying to skyper:
Replying to Klumbumbus:
Replying to stoecker:
I can add "middle,link=" as default argument to JOSMImage() when no arguments are given. Would that be fine? Klumbumbus?
I think so.
That is what I had in mind.
Done.
comment:91 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
follow-up: 94 comment:93 by , 5 years ago
follow-up: 95 comment:94 by , 5 years ago
Replying to skyper:
@Dirk:
The defaults for[[JOSMImage()]]
are lost, if you add another option.
As documented, read WikiMacros#JOSMImage-macro.
![]()
[[JOSMImage(dialogs/delete,64)]]
should be the same as![]()
[[JOSMImage(dialogs/delete,64,middle,link=)]]
but it is not.
No, as it would be impossible to get rid of the two options if needed.
comment:95 by , 5 years ago
Replying to stoecker:
No, as it would be impossible to get rid of the two options if needed.
I see, thanks. Might need to set a default size once we have more bigger .svg icons.
follow-ups: 97 102 comment:96 by , 5 years ago
Replying to stoecker:
Either my script had an error in the detection or there are really no dead image links anywhere
I just noticed a broken image link on wiki:/Help/Action/About and its translated pages. (No big deal to fix this by hand though. Just in case you want to investigate.)
follow-up: 98 comment:97 by , 5 years ago
Replying to Klumbumbus:
Replying to stoecker:
Either my script had an error in the detection or there are really no dead image links anywhere
I just noticed a broken image link on wiki:/Help/Action/About and its translated pages. (No big deal to fix this by hand though. Just in case you want to investigate.)
This is one rare special case. In general, everything went smooth. Found more broken links to source than images. Thanks
comment:98 by , 5 years ago
Replying to skyper:
Replying to Klumbumbus:
Replying to stoecker:
Either my script had an error in the detection or there are really no dead image links anywhere
I just noticed a broken image link on wiki:/Help/Action/About and its translated pages. (No big deal to fix this by hand though. Just in case you want to investigate.)
This is one rare special case. In general, everything went smooth. Found more broken links to source than images. Thanks
Probably because of the "josm" at the beginning of the link. I'll have to rerun the script to fix these cases as well. I'll try tomorrow, don't have the necessary software here ATM.
follow-up: 100 comment:99 by , 5 years ago
If rerun, please:
- remove default values from
[[JOSMImage()]]
if no other option is present. That are most changes regarding images, atm. - additionally, look for
^source:
in links and adjust them.
follow-up: 101 comment:100 by , 5 years ago
Replying to skyper:
If rerun, please:
- remove default values from
[[JOSMImage()]]
if no other option is present. That are most changes regarding images, atm.
I'll only change links I forgot, not the ones I already changed. But I'll keep this in mind.
- additionally, look for
^source:
in links and adjust them.
I have no idea what that means.
comment:101 by , 5 years ago
Replying to stoecker:
Replying to skyper:
If rerun, please:
- remove default values from
[[JOSMImage()]]
if no other option is present. That are most changes regarding images, atm.I'll only change links I forgot, not the ones I already changed. But I'll keep this in mind.
Ok.
- additionally, look for
^source:
in links and adjust them.I have no idea what that means.
See search and the first change in Styles, e.g. [source:trunk/styles/standard/elemstyles.mapcss JOSM standard]
to [source:/trunk/resources/styles/standard/elemstyles.mapcss JOSM standard]
comment:102 by , 5 years ago
Replying to Klumbumbus:
Replying to stoecker:
Either my script had an error in the detection or there are really no dead image links anywhere
I just noticed a broken image link on wiki:/Help/Action/About and its translated pages. (No big deal to fix this by hand though. Just in case you want to investigate.)
Search for source links results in following remaining errors:
- Error with src/org/openstreetmap/josm/data/SelectionChangedListener.java in DevelopersGuide/DevelopingPlugins
- Error with src/org/openstreetmap/josm/layer/OsmDataLayer.java in DevelopersGuide/DevelopingPlugins
- Error with src/org/openstreetmap/josm/plugin/Plugin.java in DevelopersGuide/DevelopingPlugins
- Error with data/validator/words.cfg in Help/Preferences/Validator
- Error with data/words.cfg in wiki:Ja:Help/Preferences/Validator
- Error with images_nodist/misc/gray_check.svg in wiki:Nl:Help/Plugin/Wikipedia
- Error with data/validator/words.cfg in wiki:Nl:Help/Preferences/Validator
- Error with src/org/openstreetmap/josm/resources/data/validation/tests in wiki:Nl:Help/Validator/MapCSSTagChecker
- Error with data/validator/words.cfg in wiki:Ru:Help/Preferences/Validator
- Error with data/tagging-preset.xsd in wiki:Ru:TaggingPresets
- Error with data/tagging-preset.xsd in wiki:Ru:TaggingPresets
- Error with data/words.cfg in wiki:Uk:Help/Preferences/Validator
They are not easily fixed, but need updates of the texts.
comment:106 by , 5 years ago
Replying to GerdP:
I've fixed the words.cfg problems
Hmm, I was SURE this file was gone. Probably mass-edits after a long work-day are a bit sub-optimal :-)
Awesome! This layout is imposed by Maven or Gradle and makes setting up an IDE much easier. Thank you!