From debjyoti at gmail.com Fri Oct 24 00:44:39 2008 From: debjyoti at gmail.com (Debjyoti Paul) Date: Thu, 23 Oct 2008 15:44:39 -0700 Subject: [uDraw(Graph)-Users] Performance issues and scaling enhancement request Message-ID: <9ed8e5050810231544r53d2e1b7y3cd8787aaac0ec88@mail.gmail.com> Hi I just started using uDraw for graph viewing and find it useful. It has many features which are superior to the tool I was previously using (VCG) like navigation/scaling/views etc. I have 2 issues though 1. Runtime: Loading even small graphs takes 20-30 seconds. This is on a 3.0 Ghz Pentium running Redhat EE4. The CPU is not loaded (as seen using 'top' ). Larger graphs take much longer. Is there a way to speedup up this ? If this is due to optimizing of the layout, can this be switched off ? If this is due to TCL interpretation of the graph file, can this be done in C/C++ for faster runtime and leave the graphics/non-runtime intensive parts to TCL ? 2. The scaling feature is nice expect that the labels and other text are not scaled. It would be very useful if text was visible at different scalings. It is ok if scaling is not continuous from 1-100 and does jumps of 10's. Like 100%/90%/80% etc. Again, these are just 2 issues I have. Otherwise uDraw is quite good and stable. Regards Debjyoti -- Regards Debjyoti -------------- next part -------------- An HTML attachment was scrubbed... URL: From debjyoti at gmail.com Fri Oct 24 00:47:26 2008 From: debjyoti at gmail.com (Debjyoti Paul) Date: Thu, 23 Oct 2008 15:47:26 -0700 Subject: [uDraw(Graph)-Users] Fwd: Performance issues and scaling enhancement request In-Reply-To: <9ed8e5050810231544r53d2e1b7y3cd8787aaac0ec88@mail.gmail.com> References: <9ed8e5050810231544r53d2e1b7y3cd8787aaac0ec88@mail.gmail.com> Message-ID: <9ed8e5050810231547u7fb8aab3y7648fa2510fc590e@mail.gmail.com> Oops, forgot to attach file ! ---------- Forwarded message ---------- From: Debjyoti Paul Date: Thu, Oct 23, 2008 at 3:44 PM Subject: Performance issues and scaling enhancement request To: udrawgraph-users at informatik.uni-bremen.de Hi I just started using uDraw for graph viewing and find it useful. It has many features which are superior to the tool I was previously using (VCG) like navigation/scaling/views etc. I have 2 issues though 1. Runtime: Loading even small graphs takes 20-30 seconds. This is on a 3.0 Ghz Pentium running Redhat EE4. The CPU is not loaded (as seen using 'top' ). Larger graphs take much longer. Is there a way to speedup up this ? If this is due to optimizing of the layout, can this be switched off ? If this is due to TCL interpretation of the graph file, can this be done in C/C++ for faster runtime and leave the graphics/non-runtime intensive parts to TCL ? 2. The scaling feature is nice expect that the labels and other text are not scaled. It would be very useful if text was visible at different scalings. It is ok if scaling is not continuous from 1-100 and does jumps of 10's. Like 100%/90%/80% etc. Again, these are just 2 issues I have. Otherwise uDraw is quite good and stable. Regards Debjyoti -- Regards Debjyoti -- Regards Debjyoti -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: eco_cover_reduced_g.udg Type: application/octet-stream Size: 3933 bytes Desc: not available URL: From mawe at informatik.uni-bremen.de Fri Oct 24 10:41:53 2008 From: mawe at informatik.uni-bremen.de (Mattias Werner) Date: Fri, 24 Oct 2008 10:41:53 +0200 Subject: [uDraw(Graph)-Users] Performance issues and scaling enhancement request In-Reply-To: <9ed8e5050810231544r53d2e1b7y3cd8787aaac0ec88@mail.gmail.com> References: <9ed8e5050810231544r53d2e1b7y3cd8787aaac0ec88@mail.gmail.com> Message-ID: <49018A51.6020102@informatik.uni-bremen.de> Hi, Debjyoti Paul schrieb: > I just started using uDraw for graph viewing and find it useful. It has thank you. > 1. Runtime: Loading even small graphs takes 20-30 seconds. This is on a > 3.0 Ghz Pentium running Redhat EE4. The CPU is not loaded (as seen using > 'top' ). Larger graphs take much longer. Is there a way to speedup up This must be a problem on your machine. On my machine here, which is a Pentium 4 3.0GHz with openSuSE 10.3, your example graph loads immediately from command line and from the API. I've written two API commands in a file to show you: menu(file(open_graph("eco_cover_reduced_g.udg"))) menu(file(quit)) Running this with the time command: -> time uDrawGraph -pipe time uDrawGraph -pipe this ? If this is due to optimizing of the layout, can this be switched > off ? If this is due to TCL interpretation of the graph file, can this > be done in C/C++ for faster runtime and leave the graphics/non-runtime > intensive parts to TCL ? Only the user interface of uDraw(Graph) is written in Tcl, everything else is written in a functional programming language that compiles to C. > 2. The scaling feature is nice expect that the labels and other text are > not scaled. It would be very useful if text was visible at different > scalings. It is ok if scaling is not continuous from 1-100 and does > jumps of 10's. Like 100%/90%/80% etc. This was a design decision several years ago, which can't be changed easily, I am sorry. If you need smaller text, you could use smaller fonts but that is not the same as scaling, I know. Regards, Mattias Werner uDraw(Graph) project -- Dipl. Inform. Mattias Werner Bremen University, FB 3 E-Mail: mawe at informatik.Uni-Bremen.DE WWW: http://www.informatik.uni-bremen.de/~mawe/ From debjyoti at gmail.com Fri Oct 24 20:42:26 2008 From: debjyoti at gmail.com (Debjyoti Paul) Date: Fri, 24 Oct 2008 11:42:26 -0700 Subject: [uDraw(Graph)-Users] API: window(position(int,int)) Message-ID: <9ed8e5050810241142nc1d3ab2u7ba37845c99eef78@mail.gmail.com> Hi Minor issue with Window(position()) api. I always get a 'Tcl/Tk Error: bad geometry specification "40+40" ' when I use this api. Please see attached command file. I tried single quotes/double quotes and '+' sign but couldn't fix it. Can you take a look ? -- Regards Debjyoti -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: x.api Type: application/octet-stream Size: 123 bytes Desc: not available URL: