paolini (Maurizio Paolini)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Wednesday

  • Clear sailing ahead.

User Details

User Since
Dec 1 2017, 9:54 AM (89 w, 2 d)
Availability
Available

Recent Activity

Jun 1 2018

paolini closed D13139: Kig bug 394676.

pushed patch to master

Jun 1 2018, 3:39 PM · KDE Edu
paolini committed R331:f324508e822d: Fix bug 394676 (authored by paolini).
Fix bug 394676
Jun 1 2018, 3:37 PM
paolini accepted D13139: Kig bug 394676.

Now that the goldenpoint got merged in master, we should also push this bug patch (in master). I can take care of that.
perhaps a bug should also be merged into other branches of kig?

Jun 1 2018, 3:31 PM · KDE Edu

May 30 2018

paolini added a comment to D13139: Kig bug 394676.

I think we should wait for David Narvaez to decide what to do

May 30 2018, 5:03 PM · KDE Edu

May 26 2018

paolini added a comment to D13139: Kig bug 394676.

This patch is on top of the golden ratio point patch.

May 26 2018, 11:26 PM · KDE Edu
paolini added a comment to D12913: Golden ratio point.

As I said, this is not a probem specific of the Golden Ratio. You should have a look at the bug report https://bugs.kde.org/show_bug.cgi?id=394676
This is a consequence of a somewhat obscure information that can (should) be associated to a construction.
I know this very well since I am responsible for it.

May 26 2018, 10:42 PM · KDE Edu

May 25 2018

paolini added a comment to D12913: Golden ratio point.

I just filed a bug report for the problem mentioned above: https://bugs.kde.org/show_bug.cgi?id=394676
in that report there is no mention of the new GoldenRatio property; it would raise the number of properties
of a segment from 5 to 6, the method mentioned in the bug report should return "true" for the GoldenRatio
property, since the constructed point is contained in the segment.

May 25 2018, 4:42 PM · KDE Edu
paolini added a comment to D12913: Golden ratio point.

About the crash above: the problem resides in AbstractLineImp::isPropertyDefinedOnOrThroughThisImp...
However it involves more than the new Golden Point. Perhaps the right action should be to file a bug
report.
It seems that the implementation of this property is wrong with respect to the hierarchy of objects

May 25 2018, 2:36 PM · KDE Edu
paolini added a comment to D12913: Golden ratio point.

I get a crash with a construction involving the new 'golden ratio' point:

  1. construct a segment s = AB
  2. construct the golden point G from the segment
  3. circle of center C (somewhere) through G
  4. position C such that the circle has two distinct intersections with the segment, one is G
  5. contruct the intersections between the segment and the circle
May 25 2018, 1:52 PM · KDE Edu

May 16 2018

paolini accepted D12913: Golden ratio point.

I would not object in accepting this revision

May 16 2018, 3:24 PM · KDE Edu
paolini added a comment to D12913: Golden ratio point.

Concerning the external point... I would *not* add a construction for it... I am afraid that such construction would be somewhat confusing.

May 16 2018, 3:03 PM · KDE Edu
paolini added a comment to D12913: Golden ratio point.

As you see... most (if not all) of the figures representing the golden section show the larger segment on the left. And when you say
"short to long equals long to whole", this is simply the result of a phrase where the subject is actually the "long", something like
"the long is 'in between' the whole and the rest".
Moreover you could as well say
"whole to long equals long to short" (and I would prefer this latter phrasing as more corresponding to the definition:

May 16 2018, 2:44 PM · KDE Edu
paolini added a comment to D12913: Golden ratio point.

I have one remark. Since the result is different depending on how we orient the segment (say) AB we have to decide if the construction
gives the point on the segment nearest to A or the one nearest to B. The proposed solution:

May 16 2018, 1:04 PM · KDE Edu