Summary of bugs

Readers,

A useful summary of bugs in LO:
https://bugs.freedesktop.org/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=LibreOffice&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_status=NEEDINFO&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=.

Thought it would be useful to share.

Would you mind to hit "Enter" between whiles?
:slight_smile:

Dne 19.10.2011 11:15, e-letter napsal(a):

Hi :slight_smile:
Adding an enter would mess up the very long link. It is very long but is also very interesting and answers a few questions i have had about LO.
Regards from
Tom :slight_smile:

Hi

  Thank you I think it is a good and necesary job.

Regards,

Jorge Rodríguez

e-letter wrote (19-10-11 11:15)

Thought it would be useful to share.

Indeed. Thanks.
Doing some QA work now and then (when other responsibilities permit) I find that for functions that I know, be cause I use them, it is relatively easy to help a bit. By clarifying bugs, sometimes pointing reporters to a direct solution and such.
I have the idea that - with some little guidance - more users would be able to do such simple tasks now and then.
It is very useful - talking recently with devs, made clear to me (once again) that when they work on fixing bugs, more time then necessarily is spent in finding the right information, bugs etc.
Some some great change for each concerned with the quality of LibreOffice to work on.

Hmm... I mentioned ' some little guidance ' in the paragraphs above.
So I will ask some other people with experience in QA about setting this up.
Therefore you may see this mail now, just as a heads up about what will come later :wink:

Cheers,

Hello!
  Is it possible to see not only the total numbers of bugs on
categories, but also the "progress" in time? It is also interesting to
see the number of fixed (and not fixed) bugs on each new LO version.
Can I find such information?

  Thanks.
    Vladimir

"Progress" to what? Resolution of the error? This would be represented
by the ratio of fixed to unresolved bugs.

In terms of each LO version, have been thinking about a periodic
retrieval of the csv data for this summary table and then plotting the
results. If this was repeated on a monthly basis, you would see how
bugs resolution occurred during time, which would be interesting.

It is interesting to review this data. Since the first issue, the
total number of bugs has increased. There does not seem to be a method
of obtaining historic data which is a disappointment. The ratio of
bugs assignment to new bugs is less than 10 %; is this to be expected?

The big problem I see with tracking reported bugs is that some are not bugs per se and some of the bugs are not explicitly killed when a new version is produced. For example conversion of MSOx files were dodgey with 3.3.0 and 3.3.1 but were much improved with 3.4.0 and later releases in the 3.3.X family. Obviously there was a bug that was fixed with the later versions but was this reported fixed because it was reported against an earlier version - I do not know.

The code cleanup efforts by the devs has killed many bugs in the later releases but are they reported as fixed against the earlier releases.

The statistics may be interesting but I suspect they could be very misleading because of different definitions used to determine what exactly is a bug and what constitutes a fix.

In concept the idea is straightforward but it is probably more difficult to pin down. Also, bugs should be weighted; bugs do not have the same overall severity.

The other issue is trying to compare the number of bugs in LO against MSO - you do not have any MSO data that I know about.

Hello!

> Hello!
> Is it possible to see not only the total numbers of bugs on
> categories, but also the "progress" in time? It is also interesting
> to see the number of fixed (and not fixed) bugs on each new LO
> version. Can I find such information?
>

"Progress" to what? Resolution of the error? This would be represented
by the ratio of fixed to unresolved bugs.

In terms of each LO version, have been thinking about a periodic
retrieval of the csv data for this summary table and then plotting the
results. If this was repeated on a monthly basis, you would see how
bugs resolution occurred during time, which would be interesting.

  Yes, this is what I was talking about. I'd like just to see how many
bugs had been fixed by developers before each version of LO release. Is
is possible at the moment?
  The idea is to see whether the number of fixed bugs for each version
increases ore decreases with time.

  Regards,
    Vladimir

This question has two parts: simple and more complex:

simple: I wish to read the value of the currently selected cell (in Calc, of course) into a variable in the macro language (Libre Basic). Script example please. and thank you!

more complex: AFAIK the LibreHelp does not document the stuff like:

dispatcher.executeDispatch(document, ".uno:GoToCell", "", 0, args2())

I used to be pretty skilled at recording macros and then modifying them. Where do I go to find things related to "uno:GoToCell"? Universal Network Objects? Can't find the "starting point".

Thank you for an orientation,

Hi David,

This question has two parts: simple and more complex:

simple: I wish to read the value of the currently selected cell (in
Calc, of course) into a variable in the macro language (Libre Basic).
Script example please. and thank you!

I can't answer your question, but if you come from the world of VBA, this document might be of use :

http://documentation.openoffice.org/HOW_TO/various_topics/VbaStarBasicXref.pdf

more complex: AFAIK the LibreHelp does not document the stuff like:

dispatcher.executeDispatch(document, ".uno:GoToCell", "", 0, args2())

I used to be pretty skilled at recording macros and then modifying them.
Where do I go to find things related to "uno:GoToCell"? Universal
Network Objects? Can't find the "starting point".

Your best bet would probably be to read the API documentation :

http://api.libreoffice.org/

or alternatively the Sun OOo Basic Programming Guide :

http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide

or buy one of the books on Macro programming :
- OpenOffice.org Macros Explained by Andrew Pitonyak
- Learn Openoffice.Org Spreadsheet Macro Programming by Mark Bain

Alex

Hi :slight_smile:
There are various books and guides about Macros. I've been told by various people that Andrew Pitonyak's is excellent. Hopefully the link is on this page
http://wiki.documentfoundation.org/Documentation/Publications

I'm not sure if that will help with the specific problem as we might need to collect links to more external resources onto that page.
Regards from
Tom :slight_smile:

Spotty access to email and short on time....

The included help does not include API level documentation since most
people have no need for it.

Sadly, I have no ability at the moment to generate an example, but, you
can find numerous examples in AndrewMacro.odt for this. I believe that
there will be a better explanation in OOME as available on my web site. If
you download that and it does not yet contain Calc examples, shoot me a
private email and I will push a copy that (although incomplete) will
contain an example of how this is done.

In brief, the idea is that you:

1. Obtain a reference to the document. If it is the current document, then
you can use the variable "ThisComponent".

2. Get a reference to the sheet containing the cell. In most cases, you
can do something like the following:

ThisComponent.sheets.getByIndex(0) ' Get the first sheet
ThisComponent.sheets.getByName("Investments") ' Get a sheet by name

Sometimes you simply want to get the currently active sheet, which is a
bit more difficult. It probably looks something like the follow (from
memory so I am probably wrong).

ThisComponent.CurrentController.ActiveSheet

After you have the sheet, then you can get the cell. Again, this is all
from memory, so I am likely totally wrong, but it probably looks something
like:

oSheet.getCellByPosition(1,2) 'Cell B3
oSheet.getCellRangeByName("B3")

A cell range with a single cell returns that cell I believe.

Next, you must decide how to get the contents of the cell. Do you want the
contained formula, a numeric value, or a string representation?

Oh, and David, I copied you with a BCC because I do not know if my post to
the list will go through based on the credentials used to send this email.

Andrew Pitonyak

Hi :slight_smile:
There are various books and guides about Macros. I've been told by
various people that Andrew Pitonyak's is excellent. Hopefully the link

is

on this page
http://wiki.documentfoundation.org/Documentation/Publications

I'm not sure if that will help with the specific problem as we might

need

to collect links to more external resources onto that page.
Regards from
Tom :slight_smile:

From: David S. Crampton <david_crampton@ie2b.com>
Subject: [libreoffice-users] How may I read the value of a cell into a
macro variable?
To: users@global.libreoffice.org
Date: Saturday, 29 October, 2011, 0:44
This question has two parts: simple
and more complex:

simple: I wish to read the value of the currently selected
cell (in Calc, of course) into a variable in the macro
language (Libre Basic).  Script example please. and
thank you!

more complex: AFAIK the LibreHelp does not document the
stuff like:

dispatcher.executeDispatch(document, ".uno:GoToCell", "",
0, args2())

I used to be pretty skilled at recording macros and then
modifying them. Where do I go to find things related to
"uno:GoToCell"?  Universal Network Objects?  Can't
find the "starting point".

Thank you for an orientation,
--David S. Crampton

--For unsubscribe instructions e-mail to:
users+help@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:

http://wiki.documentfoundation.org/Netiquette

Sub Main
  Dim x As Double
  x=ThisComponent.getCurrentSelection().getValue()

  Dim y As String
  y=ThisComponent.getCurrentSelection().getFormula()

  Dim z As String
  z=ThisComponent.getCurrentSelection().getString()

  Print x, y, z
End Sub

Kind regards

Johnny Rosenberg
ジョニー・ローゼンバーグ