Thomas Mortagne a écrit : > On Mon, May 4, 2009 at 13:49, Jerome Velociter <[email protected]> wrote: > >> Thomas Mortagne wrote: >> >>> On Mon, May 4, 2009 at 13:15, Vincent Massol <[email protected]> wrote: >>> >>>> On May 4, 2009, at 12:46 PM, Jean-Vincent Drean wrote: >>>> >>>> >>>>> On Mon, May 4, 2009 at 11:29 AM, Thomas Mortagne >>>>> <[email protected]> wrote: >>>>> >>>>>> Hi devs, >>>>>> >>>>>> In 2.0 architecture we have no way currently to print a strongly >>>>>> formatted text (like JSON) or simply a plain text without XHTML which >>>>>> we are doing generally using xpage=plain in XWiki 1.0 >>>>>> >>>>> With the 1.0 syntax xpage=plain was mainly used to: >>>>> 1/ Output data in special format (JSON, xls, etc). In those cases >>>>> {pre} was used to avoid xhtml transformations. >>>>> 2/ Output xhtml content without the XWiki UI, I can think of one use >>>>> case where this content was put in ajax tooltips. >>>>> >>>>> Is 2/ covered ? Do we need a xpage=xhtml for it ? >>>>> Note that xpage=xpart&vm=contentview.vm can be used as a workaround. >>>>> >>>> If you we want to have something clean for the future it seems to me >>>> that having a parameter called outputType (or simply output, or type, >>>> or contentType) which can take all renderer values would be best. >>>> >>>> For ex outputType=xhtml, xwiki, text, pdf, rtf, etc >>>> >>>> And when not specified it would default to outputType=xhtml. >>>> >>>> For removing the UI I'd use another parameter since it's orthogonal. >>>> Something like showUI=true|false >>>> >>> As i said this mail is about finding what to do with xpage=plain and >>> not find the way to call the plain text renderer. I just want to know >>> if we try to be able to use xpage=plain with 2.0 content or if we >>> don't do anything an say that you have to do this another way for 2.0. >>> >> I think it's better to do it another way in 2.0 and keep xpage=plain >> compatible, so that pages that are called with this parameter (from AJAX >> requests for example) can be converted and keep offering their service. >> If we use a plain text renderer, it will break functionalities if/when >> converting to 2.0 (for example UI displayed in lightboxes, ajax >> updaters, etc) >> > > I breaks anyway, if you use plain text renderer it breaks lightboxes > and if it use xhtml renderer it break JSON... >
I'm for keeping xpage=plain for lightboxes and other HTML usages (the content in HTML without the skin) and we create other template for plain text output type. Ludovic > >> Jerome. >> >>>> Thanks >>>> -Vincent >>>> _______________________________________________ >>>> devs mailing list >>>> [email protected] >>>> http://lists.xwiki.org/mailman/listinfo/devs >>>> >>>> >>> >>> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> >> > > > > -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
