in reply to Make linking to your own scratch pad easier

i don't like the implementation of the scratchpad idea. it's not much more than another homenode, albeit without clutter. it's view-only, and there is no link (conveniently placed) to edit a scratchpad, even if it's mine. it's contents are not fixed in time, so if i were to refer to it in a post, i'm not guaranteed the info will be there when another user goes looking there. also, it's functionally the same to update a scratchpad as it is to update a homenode. go_to_homenode->go_to_edit_user_information->edit_text_box(). so it doesn't make it any easier to update than a homenode is.

therefore it's good mostly for chatterbox use. i don't chat much, and if i have a question, i'll post a node. that way, not only do i not need to be there to get an answer, but i can refer to the posted answers later, too.

there are some favorite links listed on particle's scratchpad, (notice my workaround for the default behaviour) mostly because my personal nodelet was too cluttered, and i haven't taken the time to organize them for placement on my homenode. whenever i get around to that task, my scratchpad will again remain unused.

that said, i agree that demerphq's usability suggestion would make posting a link to view a scratchpad easier.

~Particle ;Þ

Replies are listed 'Best First'.
Re: Re: Optimizing for the common case...
by belg4mit (Prior) on Apr 23, 2002 at 19:40 UTC
    If you missed it, I think dark place addresses some of your issues with the scratch pad.

    --
    perl -pew "s/\b;([mnst])/'$1/g"