Hi,
> 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.
>
Sounds good. This way we can treat {{table}} macro as an extension of
{{livetable}} macro and keep the {{livetable}} macro definition simple.
Thanks.
- Asiri
>
> -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
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
