http://www.perlmonks.org?node_id=319186


in reply to Re: [CSS] Re: Let's discuss Podmaster's Signature
in thread Let's discuss Podmaster's Signature

yeah, i use my sig area to keep oft-used tags like blockquote, code, paragraph, etc. since the patch that wraps sigs in div tags was installed, i haven't modified my behavior, and now all my posts are wrapped in the sig div tags. oh well.

~Particle *accelerates*

Replies are listed 'Best First'.
Re: Re^2: [CSS] Re: Let's discuss Podmaster's Signature
by demerphq (Chancellor) on Jan 09, 2004 at 03:50 UTC

    Actually all you have to do is add the appropriate tags to your signature yourself and PM won't do it automatically for you. They look like

    <div class="pmsig"><div class="pmsig-USERID"> </div></div>

    Note: Its important that the two are not seperated with whitespace and contain no excess whitespace (ie are _exactly_ as above, with the user id substituted in) and that the user id (home node id) is correct. The match is NOT done with a regex for speed reasons

    The outer allows user to turn off ALL signatures, the inner allows users to disable specific annoying signatures. So this entire thread is a waste of time. Princepawn could have easily disabled Podmasters sig, which frankly was one of the sigs people had in mind when this functionality and the tags were added. Personally i find the "retardo" mildly irritating, but have much less of a problem with it than I do with its horrible size and colouring.

    Oh, as a last comment when I patched the original patch for adding this behaviour it added a comment to the html telling you how to do this yourself. The gods thought it was unnecessary and removed it.


    ---
    demerphq

      First they ignore you, then they laugh at you, then they fight you, then you win.
      -- Gandhi


      The explanatory text was removed because two of us felt that the manner in which it was given to the user was quite annoying (pre-pasted into the message composition window such that every user with a signature would have to delete the lengthy text every time they replied until they took the time to update their signature).

      It would have been nice if an alternate manner would have been provided to point users to an explanation, such as the patch author or applier describing it in a reply in the PMD thread that spawned the idea and adding a link to that reply in the patch (which could later be transposed into a sitedocclan node).

      But I didn't write nor apply any of these patches and so was not much involved with the whole thing other than kibitzing from the sidelines.

                      - tye

        The explanatory text was removed because two of us felt that the manner in which it was given to the user was quite annoying (pre-pasted into the message composition window such that every user with a signature would have to delete the lengthy text every time they replied until they took the time to update their signature).

        Oh dear. It seems my comment was interpreted as being a negative one. Not my intention.

        But it is true that I do disagree with the decision. I see the message my original patch would have provided as being signifigantly less annoying than simply having the new tags added without any explanation.

        But as I feel a touch of responsibility for the present state of affairs Ill look into a patch along the lines you've suggested. Perhaps when the form is constructed a note could be added underneath if the tags have been automatically added pointing to the documentation of the feature?


        ---
        demerphq

          First they ignore you, then they laugh at you, then they fight you, then you win.
          -- Gandhi


      thanks for the tip! i've changed it successfully.

      damn the gods! how was i supposed to know it worked this way unless somebody told me, or i could read it myself? i guess sometimes they forget their own omniscience :-) wait... is that even possible? oh well....

      as Aristotle commented, this can be done with multiple classes in one tag, but i don't know how older browsers handle that.

      ~Particle *accelerates*