[scribus-dev] Please review / merge this patch

[Craig Bradney]

> 
> What I hear JL asking here is reasonable to debate. From a dev point of view, I imagine there is an
> esthetic problem of introducing a 'broken' or not fully bulletproof revision in to the master. Why
> would any dev want to sign off on such a thing? My 2 cents FWIW is that if in the meantime it
> increases usability...why not add it and mention it as a 'Known Issue' that is being improved
> on..just like everything else that is being worked on..?

For those like JLuc who build Scribus from source, there's no reason why they cannot apply this to
their own tree. For us, we have decided that we don't want to implement it the way it has been. Jean
has posted a newer patch to the tracker. I've also committed some changes related to how we would
like it to be implemented. Sometimes when an idea comes about we need to fix other things to make it
work right. This one has highlighted items we need to fix. Applying patches that are not
"unwindable" later just makes life harder.

> Ultimately anyone here that is involved by watching Mantis, MLs, etc...offering feedback...has a
> want to see Scribus progress. We want to use it and enjoy it (and we do..and we could enjoy it more)
> It's hard to not be a dev and want the pace to be faster. If there was a way that we could invest
> time in helping the community move initiatives through (and I know it's been done and people have
> walked away from tasks). We could start slowly and elementary... and build from there. It's an
> idea...and separate from the issue above. Just planting some seeds. 

There's many a patch thats been committed directly. I committed 1 the night before last from Pygmee.
I also wrote a function requested by Pygmee, and then added another feature requested by JLuc last
night.

We thank you for your support too.

Craig