Hi, Thanks but we rather would try to avoid having any heavy programming logic within templates. Your proposal might be a viable solution for certain type of tasks but since this wouldn't be a native implementation it will influence performance and require additional logic within a template.
Cheers On Wed, Nov 30, 2011 at 5:37 AM, Van de Bugger <van.de.bug...@gmail.com> wrote: > Try to use variables, e. g.: > > <!-- Template `X' --> > {{ #vardefine: # > | {{ #expr: {{ #var: # | 0 }} + 1 > }} > }}<dws/> > {{ #subobject: {{ #var: # }} > | property = value... > }}<dws/> > > <!-- In a page: --> > {{ X | ... }} <!-- Will genertae subobject `1'. --> > {{ X | ... }} <!-- Will genertae subobject `2'. --> > etc. > > > On Tue, 2011-11-29 at 23:17 +0900, James Hong Kong wrote: >> Hi Markus, >> >> While testing #subobjects on MW 1.18 (on SMW 1.7alpha), we started to >> convert our SIO objects into SMW-subobjects (we hope that with this we >> can avoid double entries that now and then appear due to problems in >> SIO ). One advantage of SIO is that its assigns individual object-ids >> (#1... etc.) but for #subobjects we have to state explicitly the >> object id, considering only one or two objects then this procedure >> just works fine. For a larger set of objects per page (some of our >> pages contain a data set of 100-200 numerical statistics) we would >> wish #subobject would identify that no object identifier is present >> and than it would automatically assign a number (such as #1 ) so any >> object can be identified individually. >> >> Cheers, >> >> MWJames >> >> On Mon, Oct 3, 2011 at 6:02 PM, Markus Krötzsch >> <mar...@semantic-mediawiki.org> wrote: >> > Following up the discussions we had at SMWCon in Berlin, we have now >> > implemented a new feature for "internal objects" in SMW. This email >> > explains this feature and starts the discussion on some open questions >> > for it to become stable. >> > >> > >> > == Goal == >> > >> > Allow SMW annotations to refer to objects that have their own >> > property-value pairs just like wiki pages, but that do not actually have >> > an article in the wiki. This can be used to "group" property-value pairs >> > given on one page without requiring new auxiliary pages to be created. >> > It also integrates the main functionality of the Semantic Internal >> > Objects (SIO) extension into SMW. >> > >> > >> >> ... >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Semediawiki-user mailing list >> semediawiki-u...@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel