Am 16.01.2010 05:38, schrieb Ævar Arnfjörð Bjarmason: >> >> Avar was the first one I've seen to come up with "show me stuff from >> user xy in a special way". I'm unsure if this is really a common use case. > > FWIW potlatch does this every day by rendering things differently if > user == the guy who uploaded tiger&& tiger:reviewed == ....
tiger has special tags that are easy to display, JOSM renders: <condition k="tiger:reviewed" v="no"/> already for quite a while in a special way. I can't see why a special "user condition" is needed here. >> Personally, I'd like to keep things simple here - so even none >> developers have at least a chance to write their own rendering rules. >> >> Otherwise complexity grows and grows and ends up like the mapnik >> rendering rules with embedded SQL statements - the learning curve is now >> really high :-( > > Sure, but<condition user="foo" /> isn't that much harder than > <condition k="" v=""/> :) Exercise: Can you tell - not looking at the help - what's the difference between the two search expressions: type=* foot: ... I'm pretty sure very few people can. The JOSM search box help lists 21 conditions, offers case (in)sensitiveness and optional regular expressions, still misses a simple logical AND and offers a myriad of possible combinations. In contrast, we currently have four different conditions that are easy to grasp: <condition k="key" v="value"/> <condition k="key" b="yes"/> <condition k="key" b="no"/> <condition k="key"/> I do see a clear difference between how hard it is to learn one of the two approaches. Regards, ULFL _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/josm-dev
