On 12/18/09 4:39 PM, Sergiu Dumitriu wrote: > On 12/18/2009 12:39 PM, Marius Dumitru Florea wrote: > >> Jerome Velociter wrote: >> >>> +0.5 to add "currentPage", since it's obviously missing with regard to >>> the other current* APIs. >>> >>> Now in the future I think we should define cleaner APIs for retrieving >>> infos about the model. >>> I propose that we wait for the discussion about new Java APIs of >>> xwiki-model to be a bit more advanced, then based on that see what's the >>> good way to have this in JS. >>> >> I fill the same way. The JavaScript API should be more object oriented >> (e.g. have some of the objects available in velocity context, like $doc, >> "available" also in the JavaScript context, in a XWiki namespace to >> avoid collisions). For now, the currentPage information needs to be >> added to the XWiki object. >> >> > +1 for having a JS clone of the Java model after the Java model is close > to being finalized. >
Should it be an exact clone ? > -1 for deprecating the meta information. > Agreed. > +0 for temporarily adding a currentDocument property in the XWiki global > object. > > +1 for deprecating the inline code from javascript.vm > Agreed too, but I'd say we should do that at the same time we introduce the new model. Jerome. > To explain the last point: inline javascript is bad. The more stuff we > put in there, the larger the response size, the more the parsing and > processing time, the lower the throughput, and the lower the SEO score > (since the real content starts somewhere deep in the response). Since > the information is already available in the meta fields, we should > populate the JS object using it. > > >> >>> Jerome. >>> >>> On 12/18/09 11:58 AM, Anca Luca wrote: >>> >>>> Hi devs, >>>> >>>> right now we have 2 ways to get (some) information about the current >>>> document in >>>> javascript: >>>> >>>> * the meta tags (which store the page, the space, the wiki, version, etc) >>>> -- set >>>> in htmlheader.vm >>>> * the XWiki object set in xwiki.js and filled in with info in javascript.vm >>>> which contains currentWiki, mainWiki, currentSpace, action, etc, but *not* >>>> the >>>> currentPage. >>>> >>>> Between the two, I propose to use the second as the 'recommended' way to >>>> get >>>> information about XWiki in some javascript in a document (the action, the >>>> wiki, >>>> the space, etc) and, to make it complete, to add a currentPage to it. >>>> >>>> WDYT? >>>> >>>> Thanks, >>>> Anca >>>> > > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
