Here's my "outsider's" (non-developer's) opinion: While I tend to agree, I think it's a pretty broad sweeping criticism, without many specific suggestions. However, good to see Gary's taking the bull by the horns and attempting to do something about it :-)
Gary, I'd highly recommend not switching to QT4 at the same time as trying to improve performance, even if QT is your favorite toolkit. AFAIU, Inkscape is pretty well invested in GTK, and trying to switch toolkits is such a huge job that it would completely eclipse any efforts to improve performance.
I know for a fact that GTK apps can be fast. I doubt if GTK is a factor in Inkscape's sluggish performance, per se.
Refactoring is a great idea, and using some profiling tools is another great idea. But don't forget that premature optimization is the root of all evil -- don't over-optimise, keep a keen eye for clean code over and above highly optimized code, and only optimize what actually needs it.
http://c2.com/cgi/wiki?PrematureOptimization
I would LOVE to see Inkscape's performance addressed.
- Bryan
On Sun, Mar 13, 2011 at 08:31, ~suv
<suv-sf@...58...> wrote:
Could some of the devs help with bug triage and comment on this recent
report?
~suv
-------- Original Message --------
Subject: [Bug 733966] [NEW] Inkscape way to SLOW - Refactor
Date: Sat, 12 Mar 2011 18:49:58 -0000
From: Gary <733966@...1882...>
Reply-To: Bug 733966 <733966@...2582...2...>
Public bug reported:
Guys truly it is time to stop adding features to Inkscape and go back
and refactor the code to fix bus and the terrible performance issues.
There is little excuse for it to be at ver .48 and performance to be
slow sluggish. Even the about box repaints the logo/image very slowly.
That alone would have told me I have performance issues. At what point
do you stop trying to add features and go back and address performance?
My recommendation is to get a better handle and control over the
development effort and split your team and branch to allow some to work
on new features and others the refactoring of the code and eventual
merge. When I launched it for the first time a while back I nearly
laughed at the performance. Then expecting someone to address it in .48
would have been an expectation.
Do everyone a favor and place in your roadmap a REAL item to address
performance and refactoring the code. This sluggish performance is
across ALL platforms. For any developer on the team to be tolerant of
such or even think of asking what hardware is foolish. Any junior level
developer can easily determine the performance issues are within the
code.
As of now I am going to kick off my own branch of this code and move it
to QT4 for the UI and begin refactoring for performance. I will make
that split in the branch available for those who want a highly
performance version of InkScape.
I would invite you to address performance.
** Affects: inkscape
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Inkscape
Bug Team, which is subscribed to Inkscape.
https://bugs.launchpad.net/bugs/733966
Title:
Inkscape way to SLOW - Refactor
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
--
PS. Check out the Brush newsletter: Subscribe or read our previous newsletters
Bryan Hoyt, Web Development Manager -- Brush Technology
Ph: +64 3 741 1204 Mobile: +64 21 238 7955
Web: brush.co.nz