From: Martin S <shi...@gm...> - 2008-07-09 14:02:11
|
I've been looking at the online docs, but fail to find how to format the tabular cell size of the out put. To understand the mess go to http://www.theoldecookerybook.com/index.php/Recipes which gives a good example of what I hope to avoid. There surely must be a document on how to get standard, consistent cell widths? Regards, Martin S |
From: Markus N. <ni...@on...> - 2008-07-09 16:40:02
|
Hi everyone, I'm trying to achieve something like "automatic annotation", where the change of a property value in article A would also trigger a change of a property value in article B. As an example: I have a set of pages which is connected via the property "has predecessor". In this way, I can tell which article is the "current" one, namely the one which is not referenced by another page via this property. This would look somehow like that: {{#if: {{#ask:[[has predecessor::{{PAGENAME}}]] }} | [[is current::false]] | [[is current::true]] }} So if the page has no successor, it is marked as current. This works for the very first article "A". If I now create an article B with [[has predecessor:A]], then B should be the current. If I _look_ at A, it seems OK since the query is re-evaluated and the annotation is changed correctly. However, it is of course not consistent in the database, since the value would only be saved in the database upon re-saving article A. Therefore, querying for [[is current::true]] gives me B _and_ A. Long talk, short question: Is there any way how I can change the property on a page A depending on a property on page B _without_ having to re-save A??? Maybe there's an easy solution for this, but I'm stuck. Cheers, Markus |
From: Sergey C. <sem...@an...> - 2008-07-16 16:43:00
|
My understanding of the situation is that there is no current solution to this - I hope that query "Concepts" and other query cache-ing functions in the future will be able to invalidate query cache similar to how MediaWiki Template inclusion works, but I can consider it being quite challenging task. Maybe it makes sense to create some sort of extension to SMW that will allow you to implicitly specify pages that must be refreshed when specific property on specific page changes, but it'll also solve just part of the problem, I believe, plus it might trigger some chain reactions in the system which might be dangerous. Sergey On Wed, Jul 9, 2008 at 12:39 PM, Markus Nitsche <ni...@on...> wrote: > Hi everyone, > > > > I'm trying to achieve something like „automatic annotation", where the > change of a property value in article A would also trigger a change of a > property value in article B. As an example: > > > > I have a set of pages which is connected via the property "has > predecessor". In this way, I can tell which article is the "current" one, > namely the one which is not referenced by another page via this property. > This would look somehow like that: > > > > {{#if: {{#ask:[[has predecessor::{{PAGENAME}}]] }} | [[is current::false]] > | [[is current::true]] }} > > > > So if the page has no successor, it is marked as current. This works for > the very first article "A". > > > > If I now create an article B with [[has predecessor:A]], then B should be > the current. If I _*look*_ at A, it seems OK since the query is > re-evaluated and the annotation is changed correctly. However, it is of > course not consistent in the database, since the value would only be saved > in the database upon re-saving article A. Therefore, querying for [[is > current::true]] gives me B _*and*_ A. > > > > Long talk, short question: Is there any way how I can change the property > on a page A depending on a property on page B _*without*_ having to > re-save A??? > > > > Maybe there's an easy solution for this, but I'm stuck… > > > > > > Cheers, > > Markus > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Markus K. <ma...@se...> - 2008-07-10 06:31:43
|
On Mittwoch, 9. Juli 2008, Martin S wrote: > I've been looking at the online docs, but fail to find how to format the > tabular cell size of the out put. To understand the mess go to > http://www.theoldecookerybook.com/index.php/Recipes which gives a good > example of what I hope to avoid. > > There surely must be a document on how to get standard, consistent cell > widths? There is nothing to make fixed width cells, but you can use format=broadtable to get fixed width tables for a start. To make custom tables with control over all details, you may use format=template. An example for such a table is at http://semantic-web-grundlagen.de/wiki/SWebT1_WS07/08 (German). The query is {{Vorlesungsliste-Kopf}} {{#ask:[[Datum::+]] [[Serie::SWebT1 WS07/08]]| ?Datum| ?Titel| ?Dozent| ?Kategorie| ?Unterlagen| ?Unterlagen (Druckversion)| sort=Datum| format=template| template=Vorlesungsliste2| link=none }} |} Where {{Vorlesungsliste-Kopf}} starts a table that |} ends. The #ask just fills in the rows, using Template:Vorlesungsliste2. This has no fixed width tables, but anything can be done in such a template. Regards, Markus -- Markus Krötzsch Semantic MediaWiki http://semantic-mediawiki.org http://korrekt.org ma...@se... |
From: Martin S <shi...@gm...> - 2008-07-10 07:10:20
|
2008/7/10, Markus Krötzsch <ma...@se...>: > > On Mittwoch, 9. Juli 2008, Martin S wrote: > > I've been looking at the online docs, but fail to find how to format the > > tabular cell size of the out put. To understand the mess go to > > http://www.theoldecookerybook.com/index.php/Recipes which gives a good > > example of what I hope to avoid. > > > > There surely must be a document on how to get standard, consistent cell > > widths? > > > There is nothing to make fixed width cells, but you can use > format=broadtable > to get fixed width tables for a start. To make custom tables with control > over all details, you may use format=template. An example for such a table > is > > at http://semantic-web-grundlagen.de/wiki/SWebT1_WS07/08 (German). > > Thanks, that's more what I had in mind. I'll go and play with that. I found out (or infered from the docs) that there wasn't anything explicit for specifing cell/column width. Regards, Martin S |
From: Martin S <shi...@gm...> - 2008-07-10 07:28:56
|
I tried using "format=broadtable" as a temporary measure to fix the layout. And while it actually uses the entire width of the available screen, the rendering of the column width seems to be goverened by something not controllable. See current state of http://www.theoldecookerybook.com/index.php/Recipes Especially the first two sections. It there isn't a way of controlling column width I would like to put that in a wishlist. Much "easier" to use than a template (at least) prototyping. Methinks I'll have to use a template of some sort, but would hate to lose the sorting facility available in the standard output. I'll give it some thought and play around some more. Regards, Martin S |