Re: VelocityResponseWriter's future

2011-12-27 Thread Jan Høydahl
Hi, I think a "/browse" type of experience is crucial for newcomers to quickly get familiar with Solr. Whether it's Velocity based, AJAX based or another technology is less important. I personally like VRW and frequently use it as the first step in prototyping in a project. I've also contributed

Re: VelocityResponseWriter's future

2011-12-10 Thread Paul Libbrecht
Le 10 déc. 2011 à 02:56, Erik Hatcher a écrit : >> It's fast and easy but its testing ability is simply... unpredictable. > > I'm not sure I get what you mean by the testability though. Could you > clarify? Taken a bit literally with the VRW, there's this in a test case: Feeling sure of wh

Re: VelocityResponseWriter's future

2011-12-10 Thread Erik Hatcher
Oh gosh... there's no "argument" at all. I dig Velocity (and other things), and I'm cool with folks not liking it or not (and you like it, so it seems). I'm not sure I get what you mean by the testability though. Could you clarify? Taken a bit literally with the VRW, there's this in a test

Re: VelocityResponseWriter's future

2011-12-09 Thread David Smiley (@MITRE.org)
Erik, The /browse UI pages have definitely gotten a bit long in the tooth, to the point that it's a maintenance nightmare IMO. Perhaps it was inevitable given the nature of the technology; it would be the same situation with JSP/ASP/PHP. FWIW, in my experience with Endeca (a Solr competitor) the

Re: VelocityResponseWriter's future

2011-12-09 Thread Paul Libbrecht
Erik, don't argue with me about Velocity, I'm using it several hours a day in XWiki. It's fast and easy but its testing ability is simply... unpredictable. I did not mean to say it is not documented enough but that it could be reformulated as a tutorial wiki page instead of an example software.

Re: VelocityResponseWriter's future

2011-12-09 Thread Erik Hatcher
s/choice templating languages/template language choices/ Also, meant to include * http://today.java.net/pub/a/today/2003/12/16/velocity.html On Dec 9, 2011, at 17:07 , Erik Hatcher wrote: > Paul - > > Thanks for your feedback. > > As for JSP... the problem with JSP's is that they must be ins

Re: VelocityResponseWriter's future

2011-12-09 Thread Erik Hatcher
Paul - Thanks for your feedback. As for JSP... the problem with JSP's is that they must be inside the .war file and that is prohibitive for the flexibility of adjusting the vm files to "create links to the right resource" easily. Certainly choice templating languages are an opinionated kind o

Re: VelocityResponseWriter's future

2011-12-09 Thread Paul Libbrecht
Erik, The VelocityResponseWriter has solved a need by me: provide an interface that shows off an amount of the solr capability with queries close to a developer and a UI that you can mail to colleagues. The out-of-the-box-ness is crucial here. Adjust the vm files was also crucial (e.g. to creat