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.
  • F1rst P0st! (Score:1, Interesting)

    Wooooo!
  • Thoughts (Score:1, Interesting)

    Someone asked me for a statement of purpose about this site. Well, it is for disseimination of information about what is going on in the world of Perl, and discussion about said information. That is about it so far. I welcome suggestions on refinement of that statement. :-) Oh, I also turned off anonymous coward postings. This is open to debate, but I frankly don't like anonymous cowards, and would prefer that accountability play a role in keeping this site civil and fun instead of the pit of despair t
  • Beta Hook (Score:1, Interesting)

    Looks good. Keep it up! I'll heckle more later when I've got more free time. :-)
  • I've noticed a generous use of FONT SIZE = "1" in the various pages, and not for legal stuff that noone is really interested in. If you're going to write lots of stuff that you don't want people to read, why bother putting it on the page at all? FONT SIZE = "1" is just an alias for "UNREADABLE". -- Abigail
  • Hmmm, the previous posting was submitted with "HTML Formatted", but it didn't use the HTML tags.

    -- Abigail

  • If this is to be a discussion site about Perl, one would expect code to be posted here every now and then. Or at least, I would. (They still do that on Usenet - remember Usenet? It's like a big pile of webpages glued together.)

    However, the list of allowed HTML doesn't allow PRE. But I guess we could (mis)use UL for indented code.

    -- Abigail

  • We can change that, but it is part of the default Slash design, and I have not changed the default design (much). It would be a big job to change, and I ain't gonna do it right now. Help is welcome.

    If you want to discuss the merits of this as the default design, well, we have a whole site devoted to the Slash code [slashcode.com] that you can go to.

    And which tags did you have that didn't get used? FONT tags are not allowed, if that is what you tried.
  • And which tags did you have that didn't get used? FONT tags are not allowed, if that is what you tried.

    All I used were simple P tags.

    -- Abigail

  • Actually,
            indents just work when not using HTML formatted.

    And if you use extrans, you can even use < and > and & without manually encoding them.

    I wonder if maybe using Extrans should automatically wrap the post in <TT>, so it will be monospaced? What do you think?
  • P tags appear to work fine for me, using HTML Formatted.

    *shrug*

  • Actually, P tags seem to be failing if there is anything else in the tag, like <P ALIGN="CENTER"> or something. On my list of fixes.
  • Blah, blah, blah, blah.

    Yeay! It works. :-)
  • I like the design - it's clean and simple. From a cosmetic point of view I could live without the slashdot candy (pointless polls, the 'from the xxx department taglines', the 'this page generated by xxx' line).

    However, the slashboxes for perlmonth and perl.com are very good, as is the CPAN and site searches (well, assuming they work they're good - I've not tried).

    Groovy.
  • Site looks good (and the slashdot-isms are fine with me).
    Have you thought of providing a /favicon.ico file for IE5 users ? When IE5 bookmarks a site, it silently asks for a /favicon.ico file to use to decorate the link in the menus/links bar/desktop (you can point to a different icon by adding a <link rel="SHORTCUT ICON" href="..."> tag in the HEAD section.
    .ico is the old microsoft icon file format (holds 32 by 32 and/or 16 by 16 images).
    Adding a favicon.ico doesn't hurt non-IE5 users, but makes
  • Re:Hmmm - nice! (Score:1, Interesting)

    Well, the poll and dept. lines could actually be useful. At the least, they don't hurt. The generated by xxx line is kinda silly, and might be removed.
  • Module discussions? (Score:1, Interesting)

    by KM (4)
    Will there be a place to discuss/show modules people are working on to get comments?
  • I wasn't planning on it. I dunno, thoughts from the peanut gallery?
  • We can change that, but it is part of the default Slash design, and I have not changed the default design (much).

    The odd thing is, when I go to slashdot.org, I don't see the tiny letters all over like I see here. But maybe they don't use the same code as they released....

    Another thing. If you go to a page with comments, on the top, at the right, there are two boxes one with a link to your preferences, the other to "related links". The font is way to small to be useful, but what is far worse, those two

  • Well, Slashdot does not use the same Perl code exactly (that is being changed soon), but that is not the difference; it uses a different HTML design.

    The Related Links box is only shown when the story is shown. When you click "Change", the article disappears, only showing comments. Hence, no box. Is it a waste of real estate? I dunno, maybe. We could consider putting the Related Links box under the story instead of next to it. Or we could get rid of it entirely.

    As to caching, yeah, I am not sure wh
  • Fixed. Thanks.
  • Slashdot has a section for things like Book Reviews which remain persistant as a right-side box. Module discussions could be put in there if there aren't too many of them.

    However, the slashdot model isn't really well suited for long running discussions anyway. Once things fall off the front page, no-one cares.

  • Yes, this is the Slash concept of "sections", where we can have stuff that goes onto only one section, or show up in separate sections AND the main index page.

    As to long-running discussions, well, that is sometimes true, but the separate sections helps with that because, like you said, we can have a separate box for each section that is on the side. We can have home page links to anything we want. I think the fact that most Slashdot users do not care about those "old" discussions says more about the use
  • This sounds like a very good idea.

    use Perl; seems like the most obvious place to centralize a lot of these discussions. It's better than subscribing to 5-20 different developer lists for things like Event, LWP, etc. just because you have a passing interest.

    Of course, that begs the question, do we need yet another freshmeat? Does the module discussion area simply become "CGI.pm v2.87 released; discuss" type area?

  • Of course, that begs the question, do we need yet another freshmeat? Does the module discussion area simply become "CGI.pm v2.87 released; discuss" type area?
    Or even indeed do we need another comp.lang.perl.modules ? The list of recent module releases is nice but is it pertinent to have discussion about modules on a forum which the authors of those might not read ? /J\
  • Why does it matter if module authors don't read it?

    How many module authors read clp.modules? I sure don't.