On Thu, 15 May 2003, Bill Seitz wrote: (01)
> For the wicket/fuzzy/exploratory mode, would you agree that refactoring
> a wiki becomes more important? And that such refactoring probably
> includes renaming and/or splitting nodes? (02)
I'd say that refactoring and exploration are almost synonymous.
Exploration is refactoring in the head. (03)
In a wiki context I do think that refactoring leads to renames
and node splits. From a retrieval standpoint this is not so good,
but from a human reader's standpoint it is good; especially for
RecentChanges junkies. (04)
> This gets nasty as a wiki gets bigger, because if you explode a page
> into multiple pages, it's hard to go back through all the BackLinks and
> point them at the new pages. (05)
My approach to this is to use some indirection: don't correct the
BackLinks, just point forward from the original page. (06)
> PurpleNumbers could help, except that they are page-specific. (07)
Not anymore! (08)
Actually not quite yet, but my current experiments with
PurpleWiki and PurpleNumbers create document indepedent node IDs.
While I've not integrated the functionality into PurpleWiki yet,
I've developed techniques that will allow the parser to do the
following: (09)
- create a link into another page by just node id (you don't need
the page name) (010)
- trancslude a node from another page into a page by node id (011)
Some of this is described in (012)
http://www.burningchrome.com:8000/~cdent/wiki.cgi?SpaceCGI (013)
and its BackLinks. SpaceCGI is a prototype hack to do the
linking behavior. (014)
> This is what led to my NodeWeb thinking, which could be in retrospect be
> interpreted as copying chunks of the OHS design.
>
> http://webseitz.fluxent.com/wiki/NodeWeb (015)
You and I very much want to achieve the same thing. We need a
handy pot of money. (016)
> <incoherent>It would be cool to be able to hack wiki enough to support
> some level of transclusion and outlining so that the back end would be
> node-level granularity, and node-level linking would be encouraged, but
> it would maybe not feel too "choppy".</incoherent> (017)
This is sort of what I'm after with long term versions of
PurpleWiki. The shorter term stuff that might lead there are
described in part here: (018)
http://www.burningchrome.com:8000/~cdent/wiki.cgi?PurpleWikiScratchpad (019)
--
Chris Dent
cdent@blueoxen.org (020)
--
This message is archived at: (021)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=tools-yak&i=Pine.LNX.4.30.0305151324330.7252-100000@hot.burningchrome.com (022)
|