in reply to A non-voteable, user-updateable node?

I'm still struggling to sort out the distinctions among note, scratchpad and superdoc -- among other things. (Though I was inducted to pmdev quite a long time ago, I've been able to contribute very little there, not entirely because of focusing on SiteDocClan matters ... and on actually learning enough about Perl to actually be a useful devil.} Can you help us there?

So --     :-{)     -- even a coherent, concise and comprehensive response runs the risk of becoming part of another doc.

OTOH, perhaps the light will dawn tonite (it's now sundown, localtime) as I burn some more lamps in search of illumination.

tye has recognized -- with highly complimentary comments in another thread ( Process for Site Improvement ) -- that your extraordinary (yep, another compliment) efforts as a dev are above and beyond what we see from members of the hoi poli (like /me). Perhaps others are likewise befuddled.

  • Comment on Re: A non-voteable, user-updateable node?

Replies are listed 'Best First'.
Re^2: A non-voteable, user-updateable node? (nodetypes)
by tye (Sage) on Mar 12, 2009 at 00:38 UTC

    Only gods may modify superdocs (usually by applying patches) and that is because a superdoc can run arbitrary Perl code. Whoever "owns" the superdoc determines who can view it (and thus cause the page to be rendered, running any Perl code embedded in it).

    A note is a generic "reply" node. It is mostly a document plus a pointer to the node that it is in reply to and a pointer to the root node of its thread. How a note is displayed incorporates that extra information in the heading (plus you can vote a note up/down).

    A scratchpad is two chnks of text (public and private) with some special association with the owner. Converting last hour of cb to a scratchpad would require SQL work and might produce interesting results for things like [pad://janitors] (or whoever was declared the owner), neither of which seems like a show-stopper.

    Perhaps last hour of cb should just become a document (a basic node type that we have not recently created examples of but that many other node types are based off of). Note that a document would not be found by super search (at this time), which is probably a big draw-back to that otherwise simple proposal.

    So, of those, scratchpad seems the least problematic (other than the initial conversion work -- but it may be that the public part of a scratchpad is actually housed in the document table and so conversion isn't even a problem).

    (stream of consciousness)++; minor parts left as exercises for pmdevils intentionally

    - tye        

[reply]
[d/l]
      it may be that the public part of a scratchpad is actually housed in the document table and so conversion isn't even a problem).

      That is precisely the situation; so converting a note to a scratchpad would be trivial.

      However, it does seem like making last hour of cb a document, rather than a scratchpad, makes some sense. I don't see any features of scratchpad which would bring any benefit in this case.
      And converting a note to a document is dead trivial: simply change its type from 11 to 3. (Yeah, we'd orphan a row in the note table, but that's probably not worth worrying about one time.)

      Between the mind which plans and the hands which build, there must be a mediator... and this mediator must be the heart.
[reply]

        Who do you want to own it? (Either you or a group, though an AccessRule probably works also.)

        - tye        

[reply]

In Section Inner Scriptorium