Hi Matthias:
Glad to hear of your efforts. A couple of initial comments...
I'm cautious about your decision to build on top of jQuery.
My understanding is that you're planning to build a set of client-side
widgets that would be easily embeddable in an existing web-site.
Building on a library like jQuery (which is a great lib) opens the
door to some hairy namespacing conflicts with existing libraries
(prototype and moo, for instance), or handcoded javascript that may
exist on the current site.
If the users of your widgets also use jQuery, they will still have to
wrestle with versioning conflicts as jQuery offers new versions, and
they want to upgrade on one side or the other.
I would consider, as one alternative, packaging a small, self-
contained, and clearly namespaced version of the jQuery routines you
need (assuming jQ licence permits this).
I think the idea of utilizing the jSONwriter I'd perfect. This is a
very efficient payload for javascript.
From the design-side, unfortunately the demo was down when I visited
it.
I'm quite curious about your comment about the manager object
approach. Is there someplace I could see the demo today and review
the approach?
Thanks, and good luck!
.
-----Original Message-----
From: Matthias Epheser [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 25, 2008 2:28 PM
To: solr-user@lucene.apache.org
Subject: Announcement of Solr Javascript Client
Hi users,
As initially described in this thread [1] I am currently working on a
javascript client library for solr. The idea is based on a demo [2]
that
introduces a reusable javascript widget client.
I spent the last weeks evaluating the best fitting technologies that
ensure
a clean generic port of the demo into the solr project. The goal is
to make
it easy to use and include in webpages on the one hand, and creating
a clean
interface to the solr server on the other hand.
With this announcement, I want to ask the community for their
experience
with solr and javascript and would appreciate feedback about this
proposal:
- javascript toolkit: JQuery, because it is already shipped with the
solr
webapp
- Using a manager object on the client that holds all widgets and
takes care
of the communication to the solr server.
- Using the JSONResponsewriter to get the data to the widgets so
they could
update their ui.
These technologies seem to be the currently best ones IMHO, any
feedback/experiences welcome.
Regards,
matthias
[1]
http://www.nabble.com/-GSOC-proposal-%3A-Solr-javascript-client-library-to16
422808.html#a16430329
[2] http://lovo.test.dev.indoqa.com/mepheser/moobrowser/
