The problem with long running computations in a single threaded UI is that
they may cause the UI to block and become unresponsive for a period.
Definitely not an acceptable user experience.
I have created a library for helping with AI-type searches. This provides a
'next' function that steps
I've spent some time working on a QuadTree based approach, but haven't had
the time to benchmark it properly yet. I don't see why it would be
significantly slower than D3, as the algorithm underpinning it would be the
same.
Sent from my iPhone
On 5 June 2017 at 22:49, Erkal Selman
Coupling view and style is not the problem, it's the *goal*.
Right now, you can't declare CSS in the place where you use it: you need to
create a separate stylesheet with references, use those references in your
view and then put the stylesheet somewhere.
This is not how we write all the rest
It seams that you have driven yourself into a corner because of a series of
choices that you made with your code architecture.
The best way forward is to refactor you code so that you decouple the style
from the view.
You should be able to get both of them from the model independently.
Once
