Good to know, so I will patiently and persistently wait with my JSDoc 3 style to blossom with qooxdoo ;-)
thank you and all best with your future job Marcel Am 20.12.2013 13:06, schrieb thron7: > On Fri, Dec 20, 2013 at 12:57 PM, Marcel Ruff <[email protected]> wrote: >> According to >> >> http://usejsdoc.org/about-getting-started.html >> http://usejsdoc.org/tags-param.html >> >> @param { <type> } <name> [<description>] >> >> so >> /** >> * @param {String} text HTML formatted or plain >> */ >> >> is JSDoc 3 style. >> >> >> According to >> >> http://manual.qooxdoo.org/3.5/pages/development/api_jsdoc_ref.html >> >> @param <name> { <type> } [<description>] >> >> is qooxdoo style, as you pointed out. >> >> Is there a way to keep the two frameworks in harmonic coexistence >> (is there a syntax which both like)? > Currently not, I'm afraid. Although we have worked on the hints > syntaxes in the past, jsdoc3 and qooxdoo-style hints are still > different. I'm pretty sure that qooxdoo will re-converge to jsdoc3 > over the long run, but this might take a bit. > > T. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
