Claudius,
That zoom and pan code was written for "Le Gru" which is not a "widget", the svg generated from autoCAD was originally over 700K per floor (including toilets, true), that I manually squeezed to 40K. It's got quite a bunch of parcels, as you say, not 5000 though. There's no performance difference with the small parcels I put in the widget. That said, it would be nice of you to show us an example of the comparative code you used for your test. If you solved efficiently the bug you mention we would be glad to benefit. Last, don't forget that many have been benefiting from code graciously shared on this list by most svg "widget" developers. > ... these parameters can affect their event handling > and the visible size of their controls. ??? <G#> --- In [email protected], "cgoroll" <[EMAIL PROTECTED]> wrote: > > Hi Domenico, > > you wrote: > .... > > If we admit both visual experience and what Andr� says then this > > is not true or proven, and your statement can mislead other users, > > taking away from them the opportunity to benefit from the potential > > of the scripts in the library, which were written with the intention > > of providing optimized and easy to implement routines. One capital > > goal was also highest possible execution speed, especially to > > partially palliate display and rendering limitations. I think the > > goal was achieved, as a simple visual test can prove. > .... > > Wrong, the performance goal was not achieved ! > > First of all, try your example "SVG MAP" with more parcels. E.g. 500 > or 5000 and combined with a image. You will notice the perfomance loss > on setting the viewbox to achieve a pan/zoom. > I tried and compared performance by myself. Using currentTranslate and > currentScale is much faster. > And for retrieving/recalculating the coordinates of pointer-events > when currentTranslate or currentScale is set is easy. You just have to > d it. Unfortunately most svg "widget" developers are not aware that > these parameters can affect their event handling and the visible size > of their controls. > > Therefore I must agree to alex: setting viewBox is slower (maybe even > the slowest possible solution) than currentTranslate and currentScale. > > One think mus be said about currentTranslate. in ASV 3 you cannot set > the values to be larger than (+/1)32786. (SVG Spec. says that these > values must be float, Adobe seems to handle that as signed integer :-((). > > So when you encounter the currentTranslate to get bigger than that > value, you have to reset the viewBox to workaround that bug. > > ciao, > > Claudius ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
