2013/7/8 Thomas Neidhart
> On 07/04/2013 10:20 PM, Benedikt Ritter wrote:
> > Hi,
> >
> > we had this discussion lately where we talked about attracting new
> > contributors for commons [1]. Over the past few days I've been thinking
> > about this topic again and I've come to the conclusion that
Hello,
it would also be nice to see in once glance what is the current latest
version of each component.
For example, in the current listing of proper components, a column
'Latest version' would be very nice, as well as a short summary of
latest released components in the commons home page.
My 2
I wonder what conditions justify the use of protected / public fields?
I can see how protected fields make more sense for a single user code
because it is easier to not have all those getter/setter methods. But
perhaps for an API with a wide audience, the commitment of providing a
field is a big
Hi all ognl devs,
I'm writing to you because I developed an extra component for OGNL for
which I wanted you to know about.
Unfortunately I wasn't able to take this code off of ognl library so I had
to include OGNL in my code and modify some classes (mainly a non-intrusive
change to OgnlRuntime.jav
On 12 July 2013 15:39, Ajo Fod wrote:
> I wonder what conditions justify the use of protected / public fields?
>
> I can see how protected fields make more sense for a single user code
> because it is easier to not have all those getter/setter methods. But
> perhaps for an API with a wide audien
I like the last few arguments about multi threaded environments. That makes
the getter/setter paradigm desirable even in single user environments.
Thanks for the thoughtful arguments.
On Fri, Jul 12, 2013 at 8:01 AM, sebb wrote:
> On 12 July 2013 15:39, Ajo Fod wrote:
> > I wonder what condi
Ciao Alessandro,
thanks for your interest for OGNL and for letting us know about your component.
Just a couple of question:
Why did you need to copy the whole code of OGNL and just not fork it?
It could be hard to recognize your changes.
Can you point us a test/code example that illustrates how yo
On Fri, 12 Jul 2013 16:01:30 +0100, sebb wrote:
On 12 July 2013 15:39, Ajo Fod wrote:
I wonder what conditions justify the use of protected / public
fields?
I can see how protected fields make more sense for a single user
code
because it is easier to not have all those getter/setter method
> 1. I'd like to make it easier for users to identify which components may
be
> of interest for them. One way to accomplish this would be to introduce
> categories like they did in the wikipedia article about commons [1]
+1
Would be way easier to find tickets to start with.
> [1] http://en.wiki
