[josm-dev] Common presets for OSM editors?
Dirk Stöcker
openstreetmap at dstoecker.de
Tue Jun 23 15:23:21 UTC 2015
On Tue, 23 Jun 2015, Paul Hartmann wrote:
> We already have a mechanism to include previously defined "chunks" by
> reference in the defaultpresets.xml file. This could be used to include
> presets from the editor-presets.xml file at the correct place (or not).
> Preferably, when we make the includes, the result should be unchanged or an
> improvement.
That is unlikely. When the result is the same then it's a license
violation. And to have a start from scratch improve JOSM presets
everywhere which have many man-months work included is impossible.
And a "do the same but slightly modified" I would reject, because that
would invalidate all translators work for nothing.
> Given all that, I see no major reason to block this initiative. We would not
> drop what we have, but slowly migrating to something else.
You (all) know my opinion about this approach and I promised not to voice
it too often too loud, so I wont do it again.
I do propose another approach:
- We use the current JOSM internal presets as a common source for JOSM and
iD editor.
- We integrate anything necessary in the format to allow iD and JOSM to
use it (e.g. some keys to disable certain high-level stuff for iD,
something like id=yes/no, but probably with better semantics like
expert=true or similar - probably some fine tuning which also could
help JOSM users)
- We add any improvements which iD may want to the format definition even
if JOSM does not want or use these (like we did for maps file format)
- Converter tools reduce/convert to the final formats used by iD (and/or
JOSM, stripping of unneeded stuff when necessary) althought directly
reading the XML source file is the best way in my eyes.
This procedure should include the translations and icons.
- iD developers caring for preset definitions get SVN access for JOSM SVN
or we move the development of the internal presets file to the Wiki with
restricted access to a trustworthy group.
To make this approach more helpful we could split our preset into an
unified and a JOSM specific part and step by step move the interest parts
into the unified one.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
More information about the josm-dev
mailing list