> > > People who don't contribute to Velocity, really > > > don't have a right to complain about anything... > > > > What about people who are using Velocity? I have asked about > > map support in VTL. I can live without it, but it would be > > certainly nice to have a map support as there is already a > > collection support in VTL. I can enhance Velocity with Java > > beans as much as I like, so I don't really complain. > > Can you not add this support yourself and submit as a patch? > I don't see the problem. If you need it and it ain't there... > add it!
Come 'on, we are talking about templating language here. Or did you ask me this question as a Java developer? Then sure I can submit the patch, but I still think that it would be easier to write by people who already knows Velocity and it's source code. What, I did was asking someone to implement it. No one was willing to do it. Then I had three choices: a. Implement it myself b. Live without the feature c. Change templating engine > If you can't do it yourself, ask/pay someone to > do it for you! That's what I did! The feature was not that important to me after I build an utility class that generates those maps, so I decided to go with choice b. That doesn't mean that I'm not willing to see that feature in VTL anymore. > But, I stand by my statement that those who don't > contribute to Velocity, really don't have a right > to complain... I can see the philosophical meaning behind that statement and I agree. But I have to ask you: "Is writing the code the only way to contribute?" I'm not defending Jon here. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
