Can you give me exactly what you have in mind Linly? How the stored
data would be stored, and the syntax with which it would be retrieved.
For an info var you would have to specify page, field, and position.
Can't just use {d1}, etc.
I'm sure we could work up an info extension function if needed.
Cheers,
Dan
2009/3/26 Linly <[email protected]>:
>
> This looks interesting. Some times ago I've suggest that the info vars
> supporting the format data1.data2.data3...
>
> So we can specify the certain position, say, {d1}, {d2}, {d3}... Just
> like {p1}, {p2}, {p3}...
>
> Cheers, linly
>
> On 3月27日, 上午2時03分, Martin <[email protected]> wrote:
>> I switched to the faboulous csv plugin, which gives way more
>> flexibility to store content bits than info (if you do not want to
>> count or sum).
>> And it is still utf-ready.
>>
>> There is even a trick to get specific columns out of a csv table by
>> using a dot that simulates a page name.
>>
>> A csv list like:
>> Name.,Name,Country,etc
>> Bond.,Bond,GB,...
>> Soros.,Soros,US,...
>>
>> returns the whole first column with:
>> [(list page=... fmt='{+p1}')]
>>
>> Makes a nice select pull down in a form. Just for info.
>>
>> Greetings, Martin
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
