@David,
Quote from: davidm at Jul 19, 2006, 11:44 AM
I noticed one thing that was not mentionned in the Beta1 doc, the ability to pass data field with #:data_field# (it seems to be like "data placeholders", isn’t it ?)
Yes, we could refer to them as data placeholder. It’s in the doc for beta1 as field/column tags.
Now your example is pretty amazing if all it takes is creating a TV with an @SELECT binding and then retrieve data field as easily, it’s amazing 
Yep that’s all it takes
Hopefully when I get some time I’ll be able to do a few more live-tutorials on how to you can use a TV and the data repeater tag to generate a dynamic excel document that can be downloaded from your website.
Would that work with any field, even custom fields created by a user in the DB, given with a proper MySQL query ?
Yes it will certainly work. Just add the #:fieldname# to the template and it’s good to go.
(Noticed in the demo you run MODx 0.9.1, any particular reason ?)
lol - That’s from my old lab where I play around with MODx codes. It’s a customized version of MODx that I’ve code named GreenToken.
The parser updates should work with any version of MODx .
@Ryan,
Raymond... is there a way to do pagination with this for really long result sets?
Yes and no. No in that there’s no built-in support direct pagination but you can use the &offset and &pop features and a litle JS to simulate such features:
[[:REPEAT-WHILE? &source=`[[*pages]]`
&tpl=`#:id# #:pagetitle#`
&pop=`3`
&offset=`[[:REQUEST? &name=`offset`]]`]]
<a href="index.php?id=1&offset=6">Page 2</a>
Where &offset = page number * &pop value
Other than that I can easily add such features. What do you think?
MODX Staff
