[
https://issues.apache.org/jira/browse/SOLR-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399286#comment-13399286
]
Erick Erickson commented on SOLR-3529:
--------------------------------------
OK, I _will_ make a comment or two... But understand that my UI design skills
are legendary... legendarily bad.
> Let's not default to verbose. That's real intimidating for someone seeing it
> for the first time.
> Let's remove one of the entry fields. 99% of the time I really _want_ to see
> the same input go through at least the index and query chains. I'd rather put
> different text in a single entry field on those rare occasions when I want
> different index and query terms analyzed than copy all the time.
> I think it's _extremely_ valuable to have side-by-side display. When someone
> just starting looks at, say, WDFF on a side-by-side screen, it gives them
> information that they'd never notice otherwise. If this is only in
> non-verbose mode, fine.
> I think that having the sliders for long input when side-by-side is
> preferable to stacking anything vertically. Most of the time, I'm only
> worried about a few terms anyway and the usually fit side-by-side.
> Putting on my newbie hat, it's not obvious that the really cool display of
> the class when you hover over the abbreviations for the tokenizers/filters is
> available. Perhaps a note somewhere "hover over abbreviations to see the
> definition"? What'd be really cool is to show the complete definition in the
> hover box (e.g. the catenateWords, catenateNumbers from WDFF). Don't quite
> know how to get it to the UI, but.. <G>....
> I thought a bit about MultiTermAware stuff, and it's a sticky wicket for the
> same reasons it's always been one, this bypasses parsing. Can we cheat here?
> I have in mind some weird bit where we detect wildcards on input, and somehow
> send all the wildcard terms through the multiterm chain and put them back in
> the display in place of the wildcards that went through the whole chain. I
> _like_ making Stefan work hard <G>... OK, maybe I can help. Perhaps we can
> colorize this switch with a note about it somehow to signal that "something
> you may not have expected happened".
> clarify distnction between index & query tables on analysis debug pages
> -----------------------------------------------------------------------
>
> Key: SOLR-3529
> URL: https://issues.apache.org/jira/browse/SOLR-3529
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Reporter: Hoss Man
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3529.patch, SOLR-3529.patch,
> long-side-by-side-below-fold.png, long-side-by-side.png, med-just-index.png,
> med-query-only.png, med-side-by-side-below-fold.png, med-side-by-side.png,
> short-side-by-side.png
>
>
> Working on the tutorial, i noticed that the analysis debug page is a little
> hard to read when specifying both index and query values
> * if the inputs are short, it's not entirely obvious that you are looking at
> two tables (especially compared to how the page looks using only the "index"
> textbox)
> * if the inputs are longer, the "query" table shifts down below the fold
> where users may not even be aware of it.
> Screenshots and ideas for improvement to follow
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
