[Libreoffice-qa] Bugzilla Report Submission Assistant

Loic Dachary loic at dachary.org
Tue Aug 30 12:08:30 PDT 2011

On 08/30/2011 08:00 PM, Rainer Bielefeld wrote:
> Loic Dachary schrieb:
>> I hacked two scripts
> Hi,
> cool!
> For me your code in linked in the mail is not useful, I can't read/understand it.
Let's forget about it for now then. They extract whatever is needed from the two relevant pages.
>> 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.
> That's the thing we need.
>> 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 ?
> I am thinking about a short Wikipage containing something like tat 2 lines. The Wiki-URL might be
> <http://wiki.documentfoundation.org/Template:FdoCompChart>
> 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 <http://wiki.documentfoundation.org/index.php?title=BugReport_Details> or wherever needed, for you only the template page is interesting. We can protect such relevant so that only Wiki admins can modify them.
> Additionally there might be a reason to have some more elaborated explication. That would have URL
> <http://wiki.documentfoundation.org/FdoCompChart_long>
> 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: <http://wiki.documentfoundation.org/FdoCompChart_long>).
That makes sense.
> I believe such a pattern also could work for other Help texts, for example Subcomponents.
> 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.
Let me know when this page is ready and I'll use its content instead of digging in bugzilla for the comment.
> That can we do based on a test you do with my Chart text example.
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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libreoffice-qa/attachments/20110830/44f6a314/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: loic.vcf
Type: text/x-vcard
Size: 327 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/libreoffice-qa/attachments/20110830/44f6a314/attachment.vcf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/libreoffice-qa/attachments/20110830/44f6a314/attachment.pgp>

More information about the Libreoffice-qa mailing list