I do not know if you have seen the update, as opposed to the one
originally attached to an earlier JIRA issue, but this one should
include every attribute in a field or fieldtype -- the "attributes"
table should contain every attribute of the node.  Also, I included
(via cut-and-paste) the basic analysis form, so that it shows for each
field (and submits to analysis.jsp) as well.  If these do not fit what
you need, and do not have time to take a further look, I would be
happy to take suggestions for tweaks.

I thought about doing the transformation server-side as well, but I
stuck client-side because other admin pages rely on client-side
transformation.  I can rework it as a server-side transformation, if
that is preferable.  The only downsides to server-side approach would
be the extra (likely insignificant) burden on the server, and the size
of the page -- the transformed HTML will be an order of magnitude
larger than the XML.

As for the licensing, I did modify the code from an article, but it is
still largely intact.  I could easily write javascript that is
entirely free of the original article code, and/or contact the
original author for explicit permission.  As for the icons -- I am not
much of a graphic artist.  I could also rewrite the tree to use
characters instead, unless somebody can locate license free icons, or
perhaps the people redoing SOLR-76 could also create new icons of that
size?  (The XSL in this issue shares the base admin.css, so we may
have to rework the XSL to take SOLR-76 into account.)  If it is
permissible, I think it would be better to use the original code and
credit the author, both to give the original author deserved credit
for his idea and to minimize duplication of work on our parts :)

-Greg

On 12/6/06, Hoss Man (JIRA) <[EMAIL PROTECTED]> wrote:
    [ 
http://issues.apache.org/jira/browse/SOLR-75?page=comments#action_12456253 ]

Hoss Man commented on SOLR-75:
------------------------------

I really haven't had the time to play with this that i hoped i would (i was 
really hoping to try and tweak it to add some logic to pull all of the 
fieldtype attributes into the field, and add some links from this tool out to 
the analysis page as well) but I just wanted to go on record that i think it's 
really cool.

Greg: if you are interested, one way to avoid the issues with get-files and the 
stylesheet hearder would be to write a new JSP and/or servlet just for powering 
the schema explorer that applies the transformation on the server side -- it 
should be fairly easy with the XSL Transform utility methods Bertrand added to 
support the XSLTResponseWriter. ... then we don't have to require the files 
have the correct stylesheet declaration, or inject the one we want, or rely on 
the browser to apply it properly.

As for the license issues ... i don't think we can use those images *or* any 
javascript you cut/paste from the article ... but i could be wrong.  if there 
are similar methods you can find that have an Apache compatible license, we 
should definitely be able to use those.

> XSLT-based "Schema Browser" in admin view
> -----------------------------------------
>
>                 Key: SOLR-75
>                 URL: http://issues.apache.org/jira/browse/SOLR-75
>             Project: Solr
>          Issue Type: New Feature
>          Components: web gui
>         Environment: any
>            Reporter: Greg Ludington
>            Priority: Minor
>         Attachments: closed.gif, open.gif, solr75v1.diff
>
>
> The files in this upcoming patch create a simple "schema browser" for the 
admin tool.  It serves schema.xml along with a stylesheet that in compliant browsers creates 
a page with a tree widget to show the fieldtypes and fields, as well as their uses and cross 
references.  This is similar to the schemaxsl.zip originally attached to SOLR-58, but a few 
features have been added, and the look and feel has been changed to fit in better with the 
rest of the admin tool.
> Note that it does *not* work against the live IndexSchema -- it merely 
transforms schema.xml.  There is probably not a significant difference now, but it 
is worth raising the issue in case there are future administration capabilities in 
mind (i.e. on http://wiki.apache.org/solr/MakeSolrMoreSelfService ) that might 
require a schema browser to be talking to the live values.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



Reply via email to