Hi,
> I think it may be better to include it into OJ 1.3.1 / 1.4 - because I
> would like to avoid to add new translation strings to the core now.
>
That's OK. Let's see after 1.3 and let's focus on bugs and translation
(you already did a great work in this direction!).
Michaël
> Only bug fix
Hei Michael,
thank you for improving it.
I think it may be better to include it into OJ 1.3.1 / 1.4 - because I
would like to avoid to add new translation strings to the core now.
Only bug fixing should be done now. However, I don't even find now bugs
that are fast to do for me (except the selec
Hi,
I made some improvements in v 0.2
(http://geo.michaelm.free.fr/OpenJUMP/resources/)
I added minority, majority, median, and tried to improve the user
interface by adding some icons and examples.
I also changed its place, putting it in the tools menu, along with the
other.
I'm still not in
Hei Michael,
a long answer
I) Minority/Majority/Median:
they are only applicable to integer or string values - end return the
value that occurs the most = majority, or the least = minority* (i.e. by
counting the occurence). The median is the value right in the middle if
we build an ordered set
Stefan Steiniger a écrit :
> Hei Michael and others,
>
> I had a look on your aggregation plugin. It is a bit more advanced than
> my one. If we would add Minority/Majority/Median and try to get the
> "query" message fixed so that it doesn't exceed the box,
Hey, I did not notice that. I'll have
Hei Michael and others,
I had a look on your aggregation plugin. It is a bit more advanced than
my one. If we would add Minority/Majority/Median and try to get the
"query" message fixed so that it doesn't exceed the box, then I think we
rather should use your plugin. Or we add both, calling my
