<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> <link href="chrome://translator/skin/floatingPanel.css" type="text/css" rel="stylesheet"> </head> <body text="#000000" bgcolor="#ffffff"> On 08/30/2011 08:00 PM, Rainer Bielefeld wrote: <blockquote cite="mid:4E5D2541.5080104@bielefeldundbuss.de" type="cite">Loic Dachary schrieb: <blockquote type="cite">I hacked two scripts </blockquote> Hi, cool! For me your code in linked in the mail is not useful, I can't read/understand it. </blockquote> Let's forget about it for now then. They extract whatever is needed from the two relevant pages. <blockquote cite="mid:4E5D2541.5080104@bielefeldundbuss.de" type="cite"> <blockquote type="cite">I made it so the comment (the same that shows in bugzilla) is displayed in the page when the component is selected, because that's what I had. </blockquote> That's the thing we need. <blockquote type="cite">Could you explain what you mean by "a short Wiki Template text" ? Do you mean that Wiki Pages should be created with the more elaborated explanation ? Or such pages already exist ? </blockquote> I am thinking about a short Wikipage containing something like tat 2 lines. The Wiki-URL might be <a class="moz-txt-link-rfc2396E" href="http://wiki.documentfoundation.org/Template:FdoCompChart"><http://wiki.documentfoundation.org/Template:FdoCompChart></a> The structure of that page follows a defined plan so that it can be read easily by a script. This Template would be used instead of the manually texts for the Compoents on <a class="moz-txt-link-rfc2396E" href="http://wiki.documentfoundation.org/index.php?title=BugReport_Details"><http://wiki.documentfoundation.org/index.php?title=BugReport_Details></a> or wherever needed, for you only the template page is interesting. We can protect such relevant so that only Wiki admins can modify them. </blockquote> Understood. <blockquote cite="mid:4E5D2541.5080104@bielefeldundbuss.de" type="cite">Additionally there might be a reason to have some more elaborated explication. That would have URL <a class="moz-txt-link-rfc2396E" href="http://wiki.documentfoundation.org/FdoCompChart_long"><http://wiki.documentfoundation.org/FdoCompChart_long></a> The heading of that page would be the Template text, and who ever thinks that it's useful, he can add some more information without destroying the template text that will be used in your Frontend. In your frontend every component help text should end with a "read more ... " hint with a link to the elaborated explication in the wiki (here: <a class="moz-txt-link-rfc2396E" href="http://wiki.documentfoundation.org/FdoCompChart_long"><http://wiki.documentfoundation.org/FdoCompChart_long></a>). </blockquote> That makes sense. <blockquote cite="mid:4E5D2541.5080104@bielefeldundbuss.de" type="cite"> I believe such a pattern also could work for other Help texts, for example Subcomponents. </blockquote> Yes. <blockquote cite="mid:4E5D2541.5080104@bielefeldundbuss.de" type="cite">I will try to get an example for Component Chart ready in the wiki tomorrow in the evening, and if that works we should use that for most of such Help texts / hints in your Frontend. </blockquote> Let me know when this page is ready and I'll use its content instead of digging in bugzilla for the comment. <blockquote cite="mid:4E5D2541.5080104@bielefeldundbuss.de" type="cite"> That can we do based on a test you do with my Chart text example. </blockquote> If you just enclose the relevant text in the template with <div class="comment">bla bla</div> (which is mediawiki compatible and invisible) it's all I need. Cheers <div style="bottom: auto; left: 540px; right: auto; top: 455px;" class="translator-theme-default" id="translator-floating-panel"> <div title="Click to translate" id="translator-floating-panel-button"></div> </div> </body> </html>