Well then post a date for the release of such. Again for the current state
of the app to be at .48.1 and still exhibit poor performance is ludicrous. I
have well over 23 yrs of software development across platforms and industry
as well as managing such projects ad the sr. level. It would be nice to see
this clearly stated in the roadmap and an implementation date for the
"optimized" code.



On Sat, Mar 12, 2011 at 1:53 PM, Alexandre Prokoudine <
<email address hidden>> wrote:

> > At what point do you stop trying to add features and go back and
> address performance?
>
> I think there's a little misconception about present, future and past
> tenses you have there ;)
>
> Performance has already been addressed during GSoC2010 with two
> projects, one of them being port of rendering to Cairo. Have a go at
> http://inkscape.org/archive.php?lang=en&year=2010&month=09, last news
> item, please.
>
> > My recommendation is to get a better handle and control over the
> development effort and split your team
>
> Splitting what's left of the team isn't likely to be a better control
> over development.
>
> > When I launched it for the first time a while back I nearly laughed at
> the performance.
>
> We all need a chuckle sometimes
>
> > Do everyone a favor and place in your roadmap a REAL item to address
> performance and refactoring the code.
>
> 0.49 is already supposed to be refactoring-focused release. The roadmap
> page probably doesn't say that, but it never was a real roadmap anyway.
>
> > As of now I am going to kick off my own branch of this code and move
> it to QT4 for the UI
>
> Well, good luck with silver bullets.
>
> > I would invite you to address performance.
>
> And I invite you to inkscape-devel@ to tell us what exactly you could do
> to improve performance.
>
> P.S. No, Qt4 port won't help.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/733966
>
> Title:
>  Inkscape way to SLOW - Refactor
>
> Status in Inkscape: A Vector Drawing Tool:
>  Opinion
>
> Bug description:
>  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.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/inkscape/+bug/733966/+subscribe
>