Hi Jonathan,<br><br>The plugins are all linked in using SVN externals. Which means, the code isn't there until you do a checkout. As soon you do a checkout the SVN client will pull in the data from the external repo. When you do an svn update, SVN will also update your externals. The reason I'm doing it this way is because we're really heavy in development right now, and if I'm working on Blacklight, but need to make a change to the externalized Flare code, I can make a change, but commit it back into Flare. This will probably change once we start to solidify the code/API. Like, right now the Flare and Blacklight demos are most certainly broken, because I've made so many changes to the Flare core this week. I'll see if I can get them both running again today or Monday.<br>
<br>Does that help?<br><br>Matt<br><br><div class="gmail_quote">On Thu, Apr 3, 2008 at 4:47 PM, Jonathan Rochkind <<a href="mailto:rochkind@jhu.edu">rochkind@jhu.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Awesome, thanks for the update. I'm still a bit confused about the relationship between Blacklight and Flare. If I svn up my Blacklight stuff, will I get the new Flare stuff too (perhaps through svn externals), or do I need to do something else to install the new Flare stuff? Or is blacklight still using it's own seperate code and not the actual trunk Flare?<br>
<br>
Jonathan<br>
<br>
Matt Mitchell wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
I just deployed another version of UVA Blacklight as well as a hefty update<br>
to Flare.<br>
<br>
Flare: <a href="http://blacklight.rubyforge.org/svn/rails-plugins/flare/trunk/" target="_blank">http://blacklight.rubyforge.org/svn/rails-plugins/flare/trunk/</a><br>
A lot of the library has been simplified. Some classes and modules merged<br>
into a singe file.<br>
In the last release, "text filter" meant "query" (like in the Solr world).<br>
"facet filter" was actually a "filter query", using *_facet fields. These<br>
have changed to "query" and "filter", respectively.<br>
The url param name "ff" (facet filter) has changed to just "f" (filter).<br>
The url param name "tf" (text filter) has changed to "q" (query).<br>
The url param for filter fields now require the full field name. For example<br>
in the last release, a facet filter for "composition_era_facet" would be<br>
"composition_era". It now needs to be the full "composition_era_facet". This<br>
allows Flare to build query filters on any field. Not just *_facet fields.<br>
Pagination of facet values now working!<br>
There are a few new tests<br>
<br>
UVA Blacklight:<br>
<a href="http://blacklight.rubyforge.org/svn/branches/uva_lib/trunk/rails/" target="_blank">http://blacklight.rubyforge.org/svn/branches/uva_lib/trunk/rails/</a><br>
The search query handlers are all using Dismax. Each UI tab (catalog, music<br>
and semester at sea) has it's own Solr request handler with boosting on the<br>
title_text field. We'll tweak this according to usability/user requirements.<br>
The Z3950 availability requests are now "on click" driven.<br>
The glob of code that was in the Z3950 controller has been extracted into a<br>
neat little class<br>
Fielded searches are working! These are actually filter queries, not "q"<br>
queries.<br>
The RSS result sets are ordered by a Solr auto generated timestamp field<br>
We've switched from Mongrel Cluster to Thin:<br>
<a href="http://code.macournoyer.com/thin/" target="_blank">http://code.macournoyer.com/thin/</a> - just experimenting<br>
Now using a very recent "nightly build" of Solr<br>
<br>
I've had thoughts of turning Flare into a framework agnostic gem library.<br>
Wrappers for the url generation helpers would be the hardest part. Wouldn't<br>
it be cool to have Flare running in Merb: <a href="http://merbivore.com" target="_blank">http://merbivore.com</a>, or Camping:<br>
<a href="http://code.whytheluckystiff.net/camping" target="_blank">http://code.whytheluckystiff.net/camping</a> - any thoughts on this?<br>
<br>
Matt<br>
<br></div></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Blacklight-development mailing list<br>
<a href="mailto:Blacklight-development@rubyforge.org" target="_blank">Blacklight-development@rubyforge.org</a><br>
<a href="http://rubyforge.org/mailman/listinfo/blacklight-development" target="_blank">http://rubyforge.org/mailman/listinfo/blacklight-development</a><br>
<br>
</blockquote>
<br>
-- <br>
Jonathan Rochkind<br>
Digital Services Software Engineer<br>
The Sheridan Libraries<br>
Johns Hopkins University<br>
410.516.8886 rochkind (at) <a href="http://jhu.edu" target="_blank">jhu.edu</a><br>
<br>
</blockquote></div><br>