From: <ee...@tn...> - 2007-09-04 03:06:32
|
> From: "Reini Urban" <ru...@x-...> > Sent: Monday, September 03, 2007 10:23 AM > > 2007/9/2, Eep² <ee...@tn...>: > > You guys must've missed my post days ago about this (and I've now disabled SMW because DPL can do everything it can--and more): > > > > I just came up with an example where DPL replaces SMW while trying to figure out how to display the same page as 2 different > > things > > (like an action vs. object). Using DPL, I can simply create lists of which pages in a category link to page/subpage > > ("property/value") or namespace (or not):page ("property:value"). So, using this design, I can embed a DPL query to list all > > pages > > in the "Games" category that link to the current page as a subpage (or page in a namespace) that links to an action, effect, > > object, > > etc--and all on the same page. > > > > {{#dpl: > > category=Games > > |linksto=action/{{PAGENAME}} <!-- or action:{{PAGENAME}} --> > > |redirects=include > > |resultsheader=<h2>Games (%PAGES%)</h2> > > |noresultsheader=<h2>Games (0)</h2>''No games have this action.'' > > }} > > > > {{#dpl: > > category=Games > > |namespace=Action > > |linksto={{PAGENAME}} > > |redirects=include > > |resultsheader=<h2>Games (%PAGES%)</h2> > > |noresultsheader=<h2>Games (0)</h2>''No games have this action.'' > > }} > > > > The only problem is DPL doesn't handle redirects seamlessly (like MediaWiki's Special:Whatlinkshere page does) and requires > > obscure > > nested queries (and yet another template--DPL is a template abuser/whore, as is Semantic Forms). > > > > No silly link syntax and no excessive server hits with SMW having to figure out all those relations (since DPL doesn't require > > an > > extra database table). SMW's "facts" about section is replaced with DPL's list ouput which can be configured to be ANYWHERE on > > the > > page, ordered however, and as a table, list, etc, thus not forcing a specific ordering/layout method. > > > > Tell me, what is the point of SMW again? > > > > Time to stop reinventing the wheel and work together, DPL/SMW devs... > > I believe you missed the point completely. > Simple dynamic database queries to filter pagelists are not the Semantic Web. > > * Attributes are unified and can be calculated with, > {{#dpl-not: > category=Games > price < 100€ > |linksto=action/{{PAGENAME}} <!-- or action:{{PAGENAME}} --> > }} So DPL is limited in performing less-/greater-than queries, but that's not a difficult thing to add with a math function via a nested DPL statement. Perhaps Gero (DPL's current dev) can provide an example of how this would be done, but I'm sure it's possible with DPL. > * An extra relation link table is a huge performance plus, You have an odd definition of "huge performance plus" then because I don't consider excessive server calls (thus making pages load slower and longer) a "huge performance plus"... > * Inference. Only the simpliest queries can be done with such dynamic pagelists. Not quite; try actually using DPL before making such an ignorant statement. > dpl layout rambazamba is a completely different topic and cannot be compared to > SMW. SMW should really use some fancy layout backend for result lists. > Such as DPL's for example. But the DPL API is silly in my eyes. There must > be something better around. Actually, anything can be compared to/with anything else. Comparison is not limited to just similarities but also includes differences. |