On Sep 21, 2009, at 4:42 PM, Vincent Massol wrote:
>
> On Sep 21, 2009, at 4:33 PM, Asiri Rathnayake wrote:
>
>> Hi,
>>
>> On Mon, Sep 21, 2009 at 6:07 PM, Vincent Massol
>> <[email protected]> wrote:
>>
>>> I'd also like to know if we can support the use case of having a
>>> normal table for which we'd like to do filtering/sorting.
>>>
>>> Could that be a special {{table}} macro that would use the
>>> {{livetable}} macro with a special source that takes the content of
>>> the {{table}} macro as the content to be displayed and extract
>>> from it
>>> both the content and the table definition?
>>>
>>
>> I think it's better to keep the livetable macro as I defined earlier
>> (dynamically fetch json...). This way it will have a specific
>> meaning. If we
>> are to make livetable macro support this usecase, we have to either:
>>
>> 1. Make livetable macro even more generic.
>
>> 2. Stuff up livetable macro which will enable this usecase.
>
>>
>> I can't think of a reasonable approach to achieve 1) and 2) is bad.
>
> My though was that the implementation of {{table}} would generate 2
> things:
> - a {{livetable}} macro with the content being the definition of
> columns extracted from the {{table}} contnet
> - calls a generic special JSON source that knows how to extract data
> from a given document and a given table id (that's relatively easy
> using the XDOM information)
or pass the full {{table}} macro content to the special JSON source
which is better since we don't need to use table ids.
-Vincent
>> What we need for this usecase is may be a {{dynamictable}} macro like
>> http://confluence.atlassian.com/display/CONFEXT/Dynamic+Table+Macro
>>
>> Thanks.
>>
>> - Asiri
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
