Martijn van Oosterhout wrote:
In my opinion it is extremely bad form for your first email about a
project to be let's refactor the codebase.
Can you quote an example of where someone has actually done that? (As
opposed to, say, I tried to implement this feature but I found it
really difficult.
On Sun, Aug 24, 2008 at 3:26 PM, Gervase Markham [EMAIL PROTECTED] wrote:
Martijn van Oosterhout wrote:
In my opinion it is extremely bad form for your first email about a
project to be let's refactor the codebase.
Can you quote an example of where someone has actually done that? (As
opposed
On Sat, Aug 23, 2008 at 4:37 AM, Gervase Markham [EMAIL PROTECTED] wrote:
It seems as if someone who comes along and says I'm an experienced Java
programmer, and want to improve JOSM in this way is less trusted and
accepted than someone who comes along and says I know nothing about
Frederik Ramm wrote:
I have had many unhappy encounters with over-engineered Java code where
I had to dig through byzantine arrays of classes, most of which did
nothing but delegate something to some other class - you were at A and
wanted to pass a message to B, requiring you to change
Ulf,
Frederik, by simply ignoring the obvious demands of many of the
interested developers, IMHO you're simply doing a bad job in maintaining
JOSM :-(
If there is great demand from the community (and there obviously is),
you as a project develop lead shouldn't simply say I don't like it
Hi,
Frederik Ramm schrieb:
Given that you never simply change the coordinates of a node without
having a proper change command, it should be quite uncomplicated to
have that command change the node's index value as well when required.
And even if you found you had to encapsulate the node's
Brent,
This statement pretty much sums up my experience with OSM in general and is
the reason I no longer contribute. The project leads pretty much do what
they want and pour scorn onto anyone who doesn't agree with their point of
view. It's not just JOSM, it seems to be the standard OSM
Frederik Ramm schrieb:
All I ever hear is once we have a proper design, we will... (be able
to improve performance, attract more developers, whatever), and I simply
don't believe these claims. As I said before, where are all the Java
experts flocking to JOSM-NG because of its clean design?
Frederik Ramm schrieb:
The reason I don't work with JOSM-NG myself, and the reason I came to
JOSM in the first place, is that I am result oriented.
I guess this happens to be the reason for everybody else (excluding
Petr) as well.
I don't care for
Java. I want the editor to be usable to
Hi,
it seems like this is a recurring topic on this mailing list, but this
only goes to show that there is an issue burning many people: the JOSM
architecture and design has countless deficits, but there is little hope
of fixing them while the Plugin-API consists of tons of public fields.
In know
Dirk Stöcker wrote:
On Mon, 18 Aug 2008, J.H. wrote:
[..]
- Identify plugins which might just as well be moved into the JOSM code
base (I'm sure there's plenty of code which doesn't have to be a plugin).
Unglue is the only candidate ATM.
Add the AgPhoto plugin, as it is way
J.H. schrieb:
- Introduce an API version management for plugins (let a plugin return
its expected API version. Assume pre-version-management version on
NoSuchMethodError).
- Make it easy for refactorers to run a workspace with all the
(critical) plugins checked out.
- By the way of
Hi,
Add the AgPhoto plugin, as it is way more memory efficient than the
builtin photo linking.
Frederik?
I do not use photos, so I'm not the right contact here.
I don't either but I have heard a number of reports that Agpifoj was
indeed better than what we have built in, so throw out the
Robin Rattay napsal(a):
J.H. schrieb:
- Introduce an API version management for plugins (let a plugin return
its expected API version. Assume pre-version-management version on
NoSuchMethodError).
- Make it easy for refactorers to run a workspace with all the
(critical) plugins checked out.
Frederik Ramm schrieb:
I don't see that NG or NG-2 would fly at this point.
I don't see why not.
Well, I hope you actually *do* see the point - as I know personally that
you're really not an ignorant :-)
I'm astonished why everybody is so eager about
fussing around with a piece of
15 matches
Mail list logo
