 | | | | | |
Looks great!
One bug and one suggestion:
(1) The bug is that there is a missing range indicator
at the top of a listing, e.g. go to
http://guide.lugnet.com/set/
and follow the quick link to trains.
The first screen is OK --- it has
"First 20 of 224 Set Matches". But then click on
the right arrow for the next page, and it shows
"21–40 of 224 Set Matches". I guess there is supposed
to be a dash there between the 21 and 40.
(2) Suggestion: Duplicate the left and right arrows
for going backward and forward at the bottom of the
page so that when a user scrolls down, there is an
arrow there, and one doesn't need to scroll back to
the top to go to the next page.
Thanks again!
/Eric McC/
| | | | | | | | | | | | | | | |
| |
|
In lugnet.admin.database, Charles Eric McCarthy writes:
> Looks great!
>
> One bug and one suggestion:
>
> (1) The bug is that there is a missing range indicator
> at the top of a listing, e.g. go to
> http://guide.lugnet.com/set/
> and follow the quick link to trains.
> The first screen is OK --- it has
> "First 20 of 224 Set Matches". But then click on
> the right arrow for the next page, and it shows
> "21–40 of 224 Set Matches". I guess there is supposed
> to be a dash there between the 21 and 40.
Hmm. I see an en-dash there (not a hyphen and not an em-dash but an en-dash).
That doesn't show up for you? What browser/OS were you viewing with?
It's using entity – there, which is kind of a Microsoft-ism in character
set terms, but I had previously thought that all browsers honored it anyway,
and converted it to a hyphen if the en-dash wasn't available. Hmm.
> (2) Suggestion: Duplicate the left and right arrows
> for going backward and forward at the bottom of the
> page so that when a user scrolls down, there is an
> arrow there, and one doesn't need to scroll back to
> the top to go to the next page.
Ya, sorry about that. We took it out last night because it was super-
confusing on short pages. We'll put it back after trimming it down in a
way which works great but isn't confusing.
--Todd
| | | | | | | | | | | | | | | | | |
| |
|
Todd Lehman wrote:
>
> In lugnet.admin.database, Charles Eric McCarthy writes:
> > Looks great!
> >
> > One bug and one suggestion:
> >
> > (1) The bug is that there is a missing range indicator
> > at the top of a listing, e.g. go to
> > http://guide.lugnet.com/set/
> > and follow the quick link to trains.
> > The first screen is OK --- it has
> > "First 20 of 224 Set Matches". But then click on
> > the right arrow for the next page, and it shows
> > "21–40 of 224 Set Matches". I guess there is supposed
> > to be a dash there between the 21 and 40.
>
> Hmm. I see an en-dash there (not a hyphen and not an em-dash but an en-dash).
> That doesn't show up for you? What browser/OS were you viewing with?
>
> It's using entity – there, which is kind of a Microsoft-ism in character
> set terms, but I had previously thought that all browsers honored it anyway,
> and converted it to a hyphen if the en-dash wasn't available. Hmm.
I could have sworn that when I looked at the page
source the first time, it was just "2140", but now
when I look it is "21㫀".
Yes, it doesn't come out on Netscape 3.01 on Solaris
(I know it's old, but our sysadmins always have
"more important" things to do) but I don't expect
anyone to care about such an old version anymore.
Note, it is unrelated to the boldification.
I tried taking out the <B> and </B> and the en-dash
is still missing.
> > (2) Suggestion: Duplicate the left and right arrows
[snip]
(3) Another Suggestion: enable search by multiple
keys at the same time.
I wanted to look at all 1980-1985 train sets
but couldn't figure out how.
I couldn't figure out how to look at only 1980 train sets, either.
Is there a way?
/Eric McC/
| | | | | | | | | | | | | | | | |
In lugnet.admin.database, Charles Eric McCarthy writes:
> I could have sworn that when I looked at the page
> source the first time, it was just "2140", but now
> when I look it is "21㫀".
Nope, it was always there (I just checked). BTW, are you sure you aren't
seeing "21–40" now? There should be a ";" after the "–", otherwise
it's grammatically incorrect HTML, and you'd probabaly see "20" followed by
a splotch character of some sort.
> (3) Another Suggestion: enable search by multiple keys at the same time.
> I wanted to look at all 1980-1985 train sets but couldn't figure out how.
> I couldn't figure out how to look at only 1980 train sets, either.
> Is there a way?
Not yet, no.
--Todd
| | | | | | | | | | | | | | | | |
Todd Lehman wrote:
>
> In lugnet.admin.database, Charles Eric McCarthy writes:
> > I could have sworn that when I looked at the page
> > source the first time, it was just "2140", but now
> > when I look it is "21㫀".
>
> Nope, it was always there (I just checked). BTW, are you sure you aren't
> seeing "21–40" now? There should be a ";" after the "–", otherwise
> it's grammatically incorrect HTML, and you'd probabaly see "20" followed by
> a splotch character of some sort.
Yes, there is a semicolon.
/Eric McC/
| | | | | | |
