From: Mike O. <ir...@ms...> - 2001-04-17 03:35:56
|
On Mon, Apr 16, 2001 at 11:12:39PM -0400, Chuck Esterbrook wrote: > Ideally, we can come up with a crumb code that works in a variety of > situations. For example, we could ask the page for the crumbs. Sites could > then have each page specify crumbs: > > def crumbs(self): > return SitePage.crumbs(self) + [(link, text)] That would be a great idea, and quite Webware-style compatible. Or crumbs() could be a superclass method that read instance attributes for the links. Then simple sites could just provide the attributes, and more complicated sites can override crumbs(). > BTW a refinement to the earlier algorithm I had would be for each Page to > advertise his potential parents. We walk backwards through the trail until > we found a potential parent and then splice in from there. What's a "potential parent"? Wouldn't a page either (1) know what its parents are, or (2) be so ignorant that it can't even guess what its parents are? -- -Mike (Iron) Orr, ir...@ms... (if mail problems: ms...@ji...) http://mso.oz.net/ English * Esperanto * Russkiy * Deutsch * Espan~ol |