[ 
https://issues.apache.org/jira/browse/SOLR-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Smiley updated SOLR-3317:
-------------------------------

    Attachment: SOLR-3317.patch

Looks good.  I am supplying an updated patch with other changes/cleanup and 
some questions for you:
* Some <div class="fieldset"> tags were not closed so I closed them.
* Some id="..." attributes were not unique notably dismax & edismax since they 
share many parameters. So I added a differentiating prefix to keep them unique.
* I added title="..." tags to _some_ of the input elements to offer basic 
tooltip help.  I didn't do all of them -- I'm getting tired ;-)

Question:
* Why surround the labels to these fields in anchor tags when the label tag 
alone will work; right?  Notice 'q' is done this way, unlike most fields.  And 
*if* the anchor tags serve a useful purpose, then what does rel="help" add?

                
> Admin UI: Improve request handler / qt in query form
> ----------------------------------------------------
>
>                 Key: SOLR-3317
>                 URL: https://issues.apache.org/jira/browse/SOLR-3317
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>            Reporter: David Smiley
>            Assignee: Stefan Matheis (steffkes)
>             Fix For: 4.0
>
>         Attachments: SOLR-3317.patch, SOLR-3317.patch
>
>
> The query form in the admin UI could use an improvement regarding how the 
> request handler is chosen; presently all there is is a text input for 'qt'. 
> The first choice to make in the form above the query should really be the 
> request handler since it actually handles the request before any other 
> parameters do anything.  I think it'd be nice if it was filled with "/select" 
> by default to make it very clear what's there, although I realize most of 
> this query form seems to prefer blank values as defaults.  When the form 
> creates the URL to submit to Solr for the search, it needs to do something 
> different depending on wether this value starts with a '/'.  If it does, this 
> goes where "/select" goes in the URL normally (i.e. it's the tail end of the 
> path after the core).  If it doesn't then it goes into the 'qt' URL parameter.
> I did something similar to the old 3x UI in SOLR-3161 that got committed to 
> 3.6.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to