Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

FullPage Chatterbox ... link?

by blackstarr (Pilgrim)
on Feb 02, 2003 at 22:01 UTC ( #232059=monkdiscuss: print w/ replies, xml ) Need Help??

Hi, so it's 23h00 my time, I'm waiting for my SQL server to respond & I decide to check the chatterbox out ... after reading afew post about different clients, I finally stumble across fullpage chat in this post: Re: Re: What other clients exist for the chatterbox?

Doing a search on "chatterbox" and "client" returned quite a few posts, but most of them were rather old, and the newer ones never offered much in the way of what is CURRENTLY available. The Chatterbox Information is rather old as well.

Trying out the different clients available for download seems to end up with connection problems every time (I'm behind a very strict firewall). So, I'd like to use fullpage chat as my default client, and this is where my questions/suggestions come in.

1.) How come is it so hard to find? ... I was LOOKING and only found it by accident. Is there some thing I'm missing?

2.) Couldn't a link be added to the bottom of the Frontpage Chatterbox Nodelet for relative newbies like myself to find it with ease?

3.) The Client itself is very easy to use, my one request (so far) is, Is it not possible to let the client keep track of the messages passing through (? logfile, perhaps ?), instead of wiping out the messages every refresh?

So Long
blackstarr

Comment on FullPage Chatterbox ... link?
Re: FullPage Chatterbox ... link?
by blackstarr (Pilgrim) on Feb 02, 2003 at 23:12 UTC
    After I submitted, I remembered Ques 4.) ... What does the "displaytype=raw" at the end of the fullpage chat URL mean/do? Are there other possible args? Are they documented anywhere?

    So Long
    blackstarr

      displaytype=raw prevents the display of the nodelets.

      Update: I stand corrected - theorbtwo++.

      Note to self: must grok Everything source


      If the information in this post is inaccurate, or just plain wrong, don't just downvote - please post explaining what's wrong.
      That way everyone learns.

        While that is true, it's woefuly incomplete, to the point of being misleading. Displaytype=raw not only disables the display of the nodelets, it disables the display of /everything/ except the actualy node contents. If you go to fullpage chat without the displaytype parameter, and view source, you'll notice where the content of the node would normaly be, there's a complete XHTML document. To be more exact, displaytype=raw tells the server to use the raw displaytype node, rather then the normal displaytype for that nodetype. Also avaliable is the edit displaytype (but not for that nodetype, for non-gods), the xml displaytype, and the print displaytype.


        Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

Re: FullPage Chatterbox ... link?
by BazB (Priest) on Feb 02, 2003 at 23:14 UTC
Re: FullPage Chatterbox ... link?
by Coruscate (Sexton) on Feb 02, 2003 at 23:45 UTC

    Yes, the documentation seems to be going out of date. I just typed in Chatterbox Clients and bam, just like that, I got the list of chatterbox clients. But fullpage chat is not listed there. A little more searching brings up Other CB Clients, which does list fullpage chat. The two lists differ in a couple ways as well.

    On a completelty related matter, why isn't the documentation kept as up-to-date as possible? If the answer is 'because there is too much to keep track of updating', then that tells me that the information isn't organized well-enough :) Considering that some information is posted in more than one place and each version is different leads to some disappointment...


          C:\>shutdown -s
          >> Could not shut down computer:
          >> Microsoft is logged in remotely.
        

      Part of the problem is that the people working on the documentation aren't the same people making the code changes (for the most part). Then there's also the fact that a lot of documentation is somewhat duplicated, and it requires that a member of the documentation clan see a change and remember which documentation it will affect, and then change it all. So far as I know there is no general outline of all documentation--something I'd especially like to see written (but note that I've been inactive for the last couple of months due to moving).

      Therefore, the best thing to do when you note some documentation which is out of date is to mention it to the site documentation clan. If you find that you're doing this a lot, you could request to join sdc.

Re: FullPage Chatterbox ... link?
by Louis_Wu (Chaplain) on Feb 03, 2003 at 00:12 UTC
    We're working on that. ...

    Sorry, I've always wanted to say that. But we are. The Site Documentation Clan is renewing efforts at maintaining the docs, and I'm working on the Chatterbox FAQs. Meanwhile, you might want to check out turnstep's Chatterbox FAQ++ and ybiC's CB links.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: monkdiscuss [id://232059]
Approved by wil
Front-paged by Tanalis
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (6)
As of 2014-10-02 05:01 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    What is your favourite meta-syntactic variable name?














    Results (49 votes), past polls