Hi folks,
changing package names : +1
changing project name : no opinion about - "Commons Sanselan" or
"Commons Image (Sanselan)" is fine for my
Cheers,
Siegfried Goeschl
Charles Matthew Chen wrote:
> +1 To changing package names. It will be an easy update for Sanselan
> and the project's use
Hi Christian.
Thanks for your interest and advices. :)
>>>is it possible to enhance Chain1 with RobustTask features instead of a
complete replacement?
Yes, It`s a possible job.
>>> All is very similar, and sometimes even Chain1
looks better to my eyes than RobustTask (for example i don't think
Hi Edward. Thanks for your interest.
>>> They both seems have the same fundamental goal.
Original Chain focuses on organizing the execution of complex or long flows.
On the other hand, Chain2 focuses on providing readable notation for complex
or long flows. These are similar but not same. As time
I'm against forcing a name change on an existing project without any
other argument other than "functional names". So +1 to what Charles
says.
Niall
On Tue, Apr 28, 2009 at 9:37 PM, Charles Matthew Chen
wrote:
> +1 To changing package names. It will be an easy update for Sanselan
> and the proj
On Apr 28, 2009, at 2:22 PM, Gary Gregory wrote:
I like:
Commons Image
Not as good as any of the following:
Commons Image (Sanselan)
Commons Image "Sanselan"
Commons Image - Sanselan
The idea is that the name is Commons Image + something Sanselan.
I'm fine with any of the above that con
I think adding generics would be great. Even if the next version only adds
generics, that is reason enough for me to help and upgrade our apps. Release
early, release often.
Gary
> -Original Message-
> From: Dave Meikle [mailto:loo...@gmail.com]
> Sent: Tuesday, April 28, 2009 11:09 AM
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Tuesday, April 28, 2009 5:08 AM
> To: Commons Developers List
> Subject: Re: [sanselan] Next steps
>
> On 28/04/2009, luc.maison...@free.fr wrote:
> >
> > - "Phil Steitz" a écrit :
> >
> >
> > > We have voted to ac
luc.maison...@free.fr wrote:
> -1 to changing names. Names are part of the social link that build
> communities, changing them would appear to me as if we were stealing the
> project from both its promoters and users. All the work done on having a
> brand known would be lost.
>
Yupp, I totally
Absolutely.
On Tue, Apr 28, 2009 at 2:10 PM, Gilles Sadowski <
gil...@harfang.homelinux.org> wrote:
> > I'll guess for 3D vector the L2-norm is the more useful as it is
> > invariant when physical orthonormal frames are changed.
> > I'll check in the variant you prefer.
>
> [Cf. my other reply.]
> > L1 norm: equals(a, b, tolerance) = sum(abs(a-b)) < tolerance
> > L2 norm: equals(a, b, tolerance) = sqrt(sum((a-b)^2)) < tolerance
> > L-infinity norm: equals(a, b, tolerance) = max(abs(a-b)) < tolerance
> >
> > All are useful.
>
> I'll guess for 3D vector the L2-norm is the more useful as it
How about:
Vector3D {
...
enum Norm { L_0, L_1, L_2, L_infinity};
static double distance(Vector3D a, Vector3D b, Norm n);
...
}
?
You can then use distance(a, b, Vector3D.Norm.L_infinity) < epsilon
It gives you what you want and it should be very recognizable to the reader
o
> Among the definitions that are commonly used, you will find:
>
> L1 norm: equals(a, b, tolerance) = sum(abs(a-b)) < tolerance
> L2 norm: equals(a, b, tolerance) = sqrt(sum((a-b)^2)) < tolerance
> L-infinity norm: equals(a, b, tolerance) = max(abs(a-b)) < tolerance
+1 To changing package names. It will be an easy update for Sanselan
and the project's users.
+1 to keeping the name Sanselan. The name is of no particular
significance, but users have known the project by that name for a few
years.
Charles Matthew Chen
On Tue, Apr 28, 2009 at 8:43 AM, wr
That sounds very reasonable, but I wasn't the person with the need.
Also, for equality checking, especially in 3D, all of these will be very,
very close to the same. For very high numbers of dimensions, the
differences between boxes and balls becomes fairly extreme. In particular,
the corners of
I'm so close to releasing DbUtils 1.2 I can taste it!
http://commons.apache.org/downloads/download_dbutils.cgi
This page only shows the 1.1 release, even though 1.2 is available in
archives and on the mirrors.
http://archive.apache.org/dist/commons/dbutils/binaries/
What has to happen to fi
Ted Dunning a écrit :
> This is a generally useful thing to have, but there are multiple definitions
> for how you apply the tolerance. You should file a JIRA and add a patch!
>
> Among the definitions that are commonly used, you will find:
>
> L1 norm: equals(a, b, tolerance) = sum(abs(a-b)) <
Hi,
I know late last year Henri spoke about doing a 3.3 release of Collections
but I assume other commitments took over - this certainly keeps happening to
me just now.
I see there are some new tickets that need some minor work, so was wondering
what are the current plans?
Apologises if I have m
This should do the trick:
dev-subscr...@commons.apache.org
The Commons project has voted to accept sanselan and there is a
discussion going on about the topics I raised earlier (project name,
package name, mailing list protocols, etc.) that everyone in sanselan
should be involved in.
Than
This is a generally useful thing to have, but there are multiple definitions
for how you apply the tolerance. You should file a JIRA and add a patch!
Among the definitions that are commonly used, you will find:
L1 norm: equals(a, b, tolerance) = sum(abs(a-b)) < tolerance
L2 norm: equals(a, b, to
No we can't be sure. But your point about re-use leading to objects that
could be stack allocated being moved to long-lived storage and thus
triggering full GC's is a strong hint.
For small vectors like this, it is also worth pointing out that accessing
one element is barely faster than allocatin
Hello,
Trying to remove an annoying warning from maven, I noticed that commons-parent
11 now uses old versions and deprecated configuration for some plugins.
The things I noticed are the following ones:
version changes:
maven-gpg-plugin 1.0-alpha-4
maven-install-plugin
Hello.
Could we have a
boolean equals(Vector3D other,
double tolerance)
method?
Or even
static boolean equals(Vector3D v1,
Vector3D v2,
double tolerance)
that would return true if the components are equal within the given
toler
Hi.
> > Would you consider implementing a _mutable_ 3D-vector class?
>
> 3D vectors have been changed from mutable to immutable for both robustness
> and efficiency reasons ...
I'm all convinced that immutability makes for cleaner, and safer code.
The question is: Can we be sure that programmi
- "sebb" a écrit :
> On 28/04/2009, luc.maison...@free.fr wrote:
> >
> > - "Phil Steitz" a écrit :
> >
> >
> > > We have voted to accept sanselan as a commons component [1].
> > > Welcome!
> > >
> >
> > > We now need to settle the administrative questions raised in [2]:
> > >
> >
On 28/04/2009, luc.maison...@free.fr wrote:
>
> - "Phil Steitz" a écrit :
>
>
> > We have voted to accept sanselan as a commons component [1].
> > Welcome!
> >
>
> > We now need to settle the administrative questions raised in [2]:
> >
> > 2. Most commons components have a "functional"
> Oh, BTW, I don't see any other issues preventing the 1.0 release.
thanks all, that was quick!
I already read the releases wiki site and will dive into it a bit more
now. I am quite sure I will need help :-)
Cheers,
Christian
-
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
Hi Min Cha,
is it possible to enhance Chain1 with RobustTask features instead of a
complete replacement? All is very similar, and sometimes even Chain1
looks better to my eyes than RobustTask (for example i don't think
that throwing with RuntimExceptions is a very good idea). But there
are some co
There are enough projects for which a "fun name" works just fine.
Usually they are bigger though. *shrug* No strong opinion on this one.
I do have a strong opinion on the package name though. Definitely
should live in our package space. After all it's just a right click on
"refactor".
cheers
--
T
- "Phil Steitz" a écrit :
> We have voted to accept sanselan as a commons component [1].
> Welcome!
>
> We now need to settle the administrative questions raised in [2]:
>
> 2. Most commons components have a "functional" name instead of a "fun"
>
> name. Would Sanselan need to be renamed
Hi there,
According to my understanding, they both seems have the same
fundamental goal. Then, I wonder whether there is a way to improve
commons chain with your suggestions.
On Sun, Apr 26, 2009 at 4:57 PM, Min Cha wrote:
> Hi all,
>
> I suggested the ideas for Chain2 incubation to Commons mail
31 matches
Mail list logo
