Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Too wide for my typical browser window. I think the current design is easier to scan.
    • The search results contained a very, very long module name that stretched everything out (i.e., an edge case). What do you think now that I've commented it out?
      • I think it looks nice but I still prefer the traditional style. I like that I can scan straight down and see all the details without looking right/left.

        Spreading it out does have its virtues, though. However, there are long-named modules in CPAN and the design need to account for that without screwing up the whole page.
        • Yeah, I just wrote some Perl to deal with that. Of course, the search.cpan code isn't public, so I don't even know what templating language I could offer it in....
        • I like that I can scan straight down and see all the details without looking right/left.

          Same here. Lining columns up horizontally would be nice, but spreading the whole thing over the entire page width is a no-no.

          • How wide works for you?
            • Works in what sense? I’d prefer the data arranged primarily vertically, in a table something like this:

              +-----------------------+----+-------+------------+
              |                            |                    |
              | Module::Name               | xxxoo (1 review)   |
              +-----------------------+----+-------+------------+
              | short description blurb