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

use Perl Log In

Log In

[ Create a new account ]

pudge (1)

pudge
  (email not shown publicly)
http://pudge.net/
AOL IM: Crimethnk (Add Buddy, Send Message)
I run this joint, see?

Journal of pudge (1)

Thursday March 20, 2008
01:20 PM

Oooo Sexy: Inline Comments

[ #35947 ]

Comment replies in Slash, on use Perl and soon on Slashdot, if you have "D2"/"Dynamic Discussions" enabled, will now be inline, on the same page. Ajaxy goodness. Never leave the page to reply to an article or journal or comment. Click Reply, box loads in, type your reply, hit preview, then see preview, then hit submit, then new comment magically appears on the page.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Oooo Sexy: Inline Comments 23 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Being able to see what you're replying to is a massive advantage.

    Thanks.

  • The use.perl server really needs to get more reliable before this ajax stuff will be usable. The frequent connection timeouts make it impractical.
    • Maybe it's you? I have very rare timeouts.
        • Those connection issues were two months ago. I know the site can be slow occasionally, and during code refreshes we can be down of course, but I've noticed no significant connection issues recently.
          • The connection issues have been less frequent but certainly haven't gone away. If the downtime is caused by code refreshes, I wouldn't know. Perhaps I'll email you next time it happens.

          • What irks me personally is that the entire eight hundred sixty kilobytes YUI albatross is loaded every other time I visit even though I have disabled the Slash Ajax stuff in my prefs.

            I know I can check the box to enable the Ajax UI on any page I look at, should I ever change my mind, and that the Ajax UI then immediately starts working, which means some Javascript is needed. But you’re loading jQuery as well anwyay, which is tiny and perfectly servicable for loading extra libraries on demand. It sho

            • What irks me personally is that the entire eight hundred sixty kilobytes YUI albatross is loaded every other time I visit ...

              Then stop clearing your cache! And use a browser that handles compression.

              ... even though I have disabled the Slash Ajax stuff in my prefs

              No, you don't. You have Discussion 2 disabled. That's only one specific thing that uses Ajax on the site

              ... you're loading jQuery as well anwyay ...

              As of a couple of weeks ago.

              It should be easy to load YUI via jQuery, and to make that conditional on whether the Ajax UI is enabled.

              We don't use YUI for Ajax.

              Actually, we don't even use YUI for any of Discussion 2.

              You make some valid points, but you really don't know the code nearly well enough to be making the assertions you do.

              • I may not know how Slashcode works, but I am no web dev greenhorn. I know what can be done in HTML with and without Javascript, and the interface I do actually use is trivial to implement without any use of Javascript whatsoever, let alone Ajax. If there are still Ajax features somewhere, they are utterly wasted on me, and so is the site’s bandwidth and mine.

                As for the browser cache:

                1. Sorry, but it’s finite. I would like to increase it since I have disk space to spare, but disk cache lookup

                • I am no web dev greenhorn

                  I didn't imply otherwise. Indeed, I directly limited my claim of what you don't know to Slash, and I noted that you made valid points, but that they didn't apply as you asserted.

                  If there are still Ajax features somewhere, they are utterly wasted on me

                  Of course, you don't actually know that. And again, you also don't understand YUI very well since you seem to think it is primarily about Ajax. As to what YOU think is trivial to implement, I am uninterested in knowing.

                  I would like to increase it since I have disk space to spare ...

                  That is your choice.

                  There's no Expires header in sight when I request those URIs

                  Yes. There doesn't need to be. We use Cache-Control/max-age. Now, that is not there e

                  • So how about giving an example of how a feature I use requires YUI stuff, instead of skirting the matter with “you don’t know what it’s for” hints?

                    Here’s a summary of how I use the site: I read the site mainly via several search.pl feeds, and hit the site in the browser only to read comments, which I’ve set to nested mode, and to leave comments, which I do via the Reply links that lead me to a page with a very plain HTML form. None of these interactions happen without a

                    • So how about giving an example of how a feature I use requires YUI stuff
                      /me mumbles something about pearls before swine

                    • Right, I shouldn’t have expected an actual, straight answer. So, I’ve blocked images.use.perl.org and cleared my cache. Nothing appears to have broken, other than missing stylesheet.

                      But I’m sure there’s something I need YUI for that I don’t know anything about.

                    • Right, I shouldn’t have expected an actual, straight answer
                      Correct. When you act like I owe you something, you get nothing.

                    • Well, use.perl is where the community is, so I have to put up with Slashcode. I suppose that given sufficient effort, the resultant complaints can be interpreted as a sense of entitlement; refusing to address any of the actual issues is then a reasonable response.

                    • Well, use.perl is where the community is, so I have to put up with Slashcode
                      And I have to put up with you. I think I got the worse of the bargain.

                    • Such is the curse of success.

              • Hi Chris,

                I've been fighting the same problems on a website I'm working on (using scriptaculous instead of YUI, but the same issues with large JS). I've got a couple of easy tricks to get huge compression.

                I use yuicompressor to squish my JS and then gzip it. Simple .gz content works smoothly on all browsers except Safari. To make it work with Safari too, all you have to do is name your file .jsgz instead of .js.gz and then do the following in your apache conf:

                    <files *.jsgz>
                 

  • Is there an option I can change so that Score:1 comments will not be hidden by default? I looked in the D2 Prefs link and the standard user Preferences but couldn't find it. --thanks.
    • Maybe it is not score:1 that is the problem so here is an example. On this journal below, there is a comment titled "nearlyfreespeech.net" but it does not show up. Not even with a "1 hidden comment" link.

      http://use.perl.org/~renodino/journal/35971 [perl.org]
      • See that widget thingy with the white and dark grey slider bars? Drag those around. This changes your thresholds.
        • Ah, I probably moved those around not realizing it was doing anything. Also, it doesn't quite work. If I move the slider to 0 Hidden all this blank space opens up where the comments should be but they are still not visible. If I reload the page, they are now visible so it is not really a problem.

          Also, I am using Firefox 3 B4, in case that is the problem.
          • This should be fixed now. Did a major overhaul and upgrade of a lot of the D2 stuff for this week.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.