Closed GoogleCodeExporter closed 9 years ago
This makes some sense (although automatic size recomputation should be imho
done only
after automatic alignment and in no other situations).
Prior to implementation, it might be wise to check what sizes of SVG "canvas"
are
reasonable within a browser, with respect to performance.
Original comment by ondrej.zara
on 19 Mar 2010 at 6:56
Maybe a minimal size (2000x2000) should be kept, and enlarged only when a table
(x,y)
is moved farther (x+w>2000 || y+h>2000) ?
This way the actual behavior is kept in most case, and when the model is too
large
relations are still drawn. It so request more performance only when needed.
Original comment by geompse@gmail.com
on 19 Mar 2010 at 10:47
Yes, I imagine this behavior. The question is whether larger SVG elements are
feasible / performant enough.
Original comment by ondrej.zara
on 19 Mar 2010 at 11:11
Tested by setting Area (so SVG) to 500 000 x 500 000
> SQL.Designer.tables[0].moveTo(499500,499500)
Moving the table, there is no performance issue with Chromium.
In fact that's not the size of the canvas, that's the number of objects and
relations
that matters. This is not related to the SVG size.
Test case : build an XML that contains 10 000 tables and load it
=> Might take some seconds to load :)
Original comment by geompse@gmail.com
on 19 Mar 2010 at 11:49
Nice :)
Original comment by ondrej.zara
on 19 Mar 2010 at 12:00
Implemented in r95.
Original comment by ondrej.zara
on 22 Mar 2010 at 1:48
Original issue reported on code.google.com by
geompse@gmail.com
on 18 Mar 2010 at 4:32