[scribus] degenerate objects
louis.desjardins at gmail.com
Tue Feb 9 19:45:29 CET 2010
2010/2/9 Gregory Pittman <gregp_ky at yahoo.com>
> On 02/09/2010 11:42 AM, Louis Desjardins wrote:
>> Reality checks are always good ! :)
>> The user would have the option to turn on or off the import-check. Or, in
>> this particular case — which might happen quite often — I would suggest
>> the warning only appears once the user leaves the edit mode for that
>> Actually, this could be the behaviour of that warning, not at import but
>> once the image is set to its desired size. The warning could appear or
>> disappear while scaling the image. Only then we can really tell whether
>> image has enough resolution.
>> Plus, the warning would be soft. No need to answer [cancel] or [ok] etc.
>> would simply appear into the image in a manner that could even be
>> How’s that ?
> I think if we consider the point-of-view this sub-thread was coming from,
> you are talking about creating a lot more complexity and warnings where less
> complexity and warnings were desired.
That warning should not a pop-up in my view or a dialog or anything as
disturbing or invading. It would be a dynamic warning that would let know
the user that an image has not the sufficient resolution for print according
to the settings he had put there.
There are tons of knowledgeable users who have to deal everyday with
poor-quality images. It’s very easy to lose track of the images that are
tagged as “potential issues“ when you’re dealing with a large document that
includes lots of pictures. So, people forget. And this is a reminder that’s
only there to help get those time-consuming issues out of the way before we
get to the end of the production when there is no time left to address those
issues and yet we have to address them.
In my view, this doesn’t add complexity (at least for the user). It’s a
warning that sits there. Not more disturbing (but not less) than the little
red square in the right down corner of text frames when there is too much
text. And in fact it could be just that, or a bit more obvious — we can
In short: add a little red square on the right down corner of image frames
when the image doesn’t meet the desired output resolution.
To tweak this I would make that square printable or not in the user prefs.
So whoever proofs that job at whatever stage could see that there is
something wrong with this image and either fix it or change it.
> Certainly, if someone wants to fork Scribus into a Scribus-For-Dummies
> version, I say, go for it! Otherwise I think we want to promote
> professionalism and knowing your content and paying attention to the array
> of information that Scribus has at your disposal.
I don’t think this feature would be a Scribus-For-Dummies feature! In fact,
the more I think of it and the more I think it would be a real cool
addition. One other question that we need to answer is at what programming
Does anyone else has a view on that?
> scribus mailing list
> scribus at lists.scribus.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the scribus