Hello Simon,
Thanks for fast reply.
I finally decide to draw connections with jsplumb in pagination
format, 50 connection in every page. If the dependent records are
more, then the user can go next and previous to get the results.
I think, jsplumb is slow not because it has any problems, but it is
the browser which cannot handle lots of graphic rendering operations.
For now, i think this is a better way to go on. I hope, you are also
agree with me.
Thanks
On Jun 3, 3:00 am, Simon Porritt <
simon.porr...@gmail.com> wrote:
> I just saw your tweet. Got any timing figures? I'm always interested in
> ways of making it faster.
>
> On Sat, Jun 2, 2012 at 3:39 PM, Simon Porritt <
simon.porr...@gmail.com>wrote:
>
>
>
>
>
>
>
> > You can try making this call before you start creating connections:
>
> > jsPlumb.setSuspendDrawing(true);
>
> > and then when you want it to draw again:
>
> > jsPlumb.setSuspendDrawing(false, true);
>
> > the second argument is optional and tells jsPlumb to do a full repaint
> > immediately after that call (otherwise you can call
> > jsPlumb.repeaintEverything() manually).
>
> > This will most likely help. But be aware that browsers do just get slow
> > when you have hundreds of connections and nodes, particularly IE of course.
>
> > On Sat, Jun 2, 2012 at 3:32 PM, Jamshid HASHIMI <
jamshidhash...@gmail.com>wrote:
>
> >> Hello,
>
> >> I am working over a huge database, where we want to visualize the
> >> dependency of searched keyword to overall records (if they have
> >> dependency) via jsplumb.
>
> >> When trying to work like here:
>
> >>
http://olegpuzanov.com/2010/06/08/visualise-your-twitter-friends-with...