18 Aug
2016
18 Aug
'16
3:19 p.m.
On Thu, Aug 18, 2016 at 3:15 PM, Vincent Massol <vincent(a)massol.net> wrote:
Each output filter can expose various properties (like macros) so it's
possible to customize a lot of things without special UI for a first
version. If we go for a UI extension point system then each output
filter will also have to provide a UI extension.
On 18 Aug 2016, at 15:12, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
On Thu, Aug 18, 2016 at 2:43 PM, Vincent Massol <vincent(a)massol.net> wrote:
Yes this may or may not be needed. The reason I mentioned is because each export type may
want to offer a custom UI. Hi devs (especially Thomas),
Just making sure we agree about the future of exports:
* Rewrite our various Exports (PDF, HTML, etc) code to use the FilterStream Module
* Modify the Page Export UI to use the
FilterStream API/script service + and add an extension point (or an XClass) so that
extension can contribute new Export types in the UI
This is not really needed. We could simply list all the output filter
streams we can find with compatible properties (i.e. a "target"
property compatible with OutputStreamOutputTarget type).
Thanks
-Vincent
--
Thomas Mortagne
* Modify the Admin Export UI to do the same
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs * Register the PDF, HTML, XAR, etc exports to
register against those extension points
* Modify the XFF extension to do the same
Do we agree?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs