I think going through so much of the Leo codebase as you have done in
the last couple of weeks you've come up with something of a catalog of
things that might benefit from different approaches, in some cases the
benefit of hindsight, for that matter.
I can't put together a detailed response right
This thread is primarily intended for Leo developers. It might be long and
boring for other readers. So read it at your own risk.
If I had looked more thoroughly in unitTests.leo earlier I would never make
a proposition to incorporate new data model in Leo and make all unit tests
pass. I
>
>
> I'm eager to see the code. Could you publish what you have? I promise not
> to touch it :-)
>
>> There are also new things I have learned about Leo and I wish to discuss
>> them but right now I am a bit exhausted and I have to rest for the next few
>> days.
>>
>
>
I have just pushed
On Sat, Jul 28, 2018 at 2:40 PM, vitalije wrote:
I have incorporated new data model into Leo and all unit tests pass.
>
A few more comments.
Two days ago I had a version which passed all tests for the first time.
> However, there have been serious speed issues. Running all tests with new
>
This *is* exciting. One of my more pressing questions: if a future front
end were written which does not use PyQt/PySide, would it benefit from the
same speedups during drawing?
On Saturday, July 28, 2018 at 3:40:15 PM UTC-4, vitalije wrote:
>
> I have incorporated new data model into Leo and
