<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 10/30/10 8:08 PM, Louis Desjardins wrote:
<blockquote
cite="mid:AANLkTikA6aznhrWAj32iHK9WvSRUU84tEm9fhkDWTrPK@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">2010/10/30 Jean Ghali <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:jghali@libertysurf.fr">jghali@libertysurf.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Louis Desjardins a écrit :<br>
<div>
<div class="h5">> Hi guys,<br>
><br>
> Currently trying to get something out of 1.3.8 on a
Mac.<br>
><br>
> Are we really going to get out of the mud of this
text engine ? out of<br>
> the mud of this style dialog ?<br>
><br>
> Hey ?!?!<br>
><br>
> Set type.<br>
><br>
> Three basic settings...<br>
><br>
> 1. Type.<br>
><br>
> 2. Typsesize.<br>
><br>
> 3. Leading.<br>
><br>
> Now, where are they ?<br>
><br>
> Type and typesize on the next tab...<br>
><br>
> Leading on the first tab...<br>
><br>
> No compliments. It does not work. It does not make
any sense.<br>
><br>
> Yes, I know. I should know how to code.<br>
><br>
> Louis, get out of your comfort zone and start coding.<br>
><br>
> Can we simply get rid of this dialog and have the
style created at right<br>
> hand click ? Bug 300 or so by Lyam, back in 2004 or
something.<br>
><br>
> Please do us a favor and kill this dialog.<br>
><br>
<br>
</div>
</div>
I think everyone agrees there is much to say about current
style dialog. Unfortunately the<br>
complaint cited here shows a lack of functionnality analysis.
Why leading is a character<br>
property in Indesign/QuarkXPress? Because they have the
capability to control that setting<br>
at line level. Scribus has currently no such capability.
Consequently placing leading<br>
control in character style dialog would misrepresent Scribus
functionnalities and makes<br>
currently no sense.<br>
</blockquote>
<div><br>
Does that explain why there is currently a tab split in the
paragraph style to put in different tabs the typesize and the
linespacing? I don’t think that they should be splitted,
first. There are characters attributes to a paragraph style.
But maybe this is not how it’s programmed. But from the user’s
perspective, there is a need not to have to run in circles
into a dialog to set something, look elsewhere, try to find
settings that work together and that are related. It makes no
real sense to set type and typesize without a linespacing
value. So why put those on separate tabs?<br>
</div>
</div>
</blockquote>
<br>
Louis, that interface has been like that for a few years now.<br>
<br>
Given those that can probably change this are working on the OIF
project, I don't understand why you are complaining about this now.<br>
<br>
Still, I 100% agree with Jean.. functionality and usability analysis
needs doing properly before we will change anything.<br>
<br>
Craig<br>
</body>
</html>