Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • First let me congratulate you on your courage. I think it is brave that you have the guts to post a graphical presentation/mock-up and opening the discussion of it's contents. Where I come from everybody has an opinion on layout and this can generate immensely disproportionate discussions on details.

    So even I have an opinion on your mock-up as well and some feedback, which I hope you will find constructive.

    1. Headings for the columns would be nice, it is always a good idea to tag your data with some sort of identification of what they are and represent, ahref= []> is not just used by CPAN regulars and PAUSE users, this can be expected to be many Perl users first interface to CPAN and therefor, googling distribution names at least give results leading to ahref= []>

    2. Sortable search results, based on headings, all should of course be reversible. We have this in the author page: []

    Where you can sort on distribution and release date, both ascending and descending.

    Well the columns you list, could have the following sort behaviour:

            - name (alphabetical sort)

            - distribution (alphabetical sort)

            - release date (newest first)

            - author (alphabetical sort)

            - review (by score)

    3. Your example shows a search done in the context of 'All', your example is from this perspective not the best for another example:

    See: []

    The included example shows a result set including different result types, such as scripts, modules/packages and distributions.

    It would be nice if search results could be tagged with an icon indicating their type since a search with the context of 'All' could yield a result set containing varies items as the times I mentioned above.

    In addition it would be nice if the following files could be searched: README, Changes and tests and could be included in search results, but that is not what you attempt to address with your mock-up and should probably be addressed elsewhere.

    4. In addition to the data you have in your search results page, perhaps additional data could be included, such as: License

    I think that was about my 2 cents, for now.

    And to get back to the topic on guts, I guess we all would love so see and hack on the guts of [], but since this is apparently never going to happen and alternative open sourced implementation might the way to go.