[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Bug 76757 : modification of style manager
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2004-07-25 13:54:46
Message-ID: 200407251554.46205.nicolasg () snafu ! de
[Download RAW message or body]

On Sunday 25 July 2004 15:41, p.stirnweiss_koffice@bluewin.ch wrote:
> >-- Message original --
>
> From: Nicolas Goutte <nicolasg@snafu.de>
>
> >To: For developer's discussion about KOffice <koffice-devel@mail.kde.org>
> >Date: Sun, 25 Jul 2004 14:52:42 +0200
> >Subject: Re: Bug 76757 : modification of style manager
> >Reply-To: For developer's discussion about KOffice
> > <koffice-devel@mail.kde.org>
> >
> >On Sunday 25 July 2004 10:50, p.stirnweiss_koffice@bluewin.ch wrote:
> >> >-- Message original --
> >>
> >> From: Nicolas Goutte <nicolasg@snafu.de>
> >>
> >> >To: For developer's discussion about KOffice
> >> > <koffice-devel@mail.kde.org> Date: Sat, 24 Jul 2004 23:36:52 +0200
> >> >Subject: Re: Bug 76757 : modification of style manager
> >> >Reply-To: For developer's discussion about KOffice
> >> > <koffice-devel@mail.kde.org>
> >> >
> >> >On Saturday 24 July 2004 19:07, p.stirnweiss_koffice@bluewin.ch wrote:
> >> >> Hi, I am starting to have a look at this one.
> >> >> I would like to change some stuff in the way the style manager is
> >> >> organised. Let me know your opinions on these ideas (I personaly find
> >>
> >> them
> >>
> >> >> more logical, but it may not look the same to everybody):
> >> >
> >> >The problem of splitting dialogs is that it is only good if it is not
> >
> >done
> >
> >> >only in the stylist but also in each of the individual dialogs.
> >> > (Especially
> >> >
> >> >for the points 2 and 3 below.)
> >
> >I want to add to my comment here, that it is also important, as KWord is
> >
> >supposed to get character styles soon and possibly the stylist dialog
> > should
> >
> >be modified having this idea in mind too.
>
> Wow, this seems to evolve way beyond my current level of understanding. I
> am not sure it is Junior level anymore :).

Well, I had always doubts about marking this bug as Junior Job due to the 
Stylist, but I did anyway. :-)

To be serious again: I do not mean that you need to do it. I just want to tell 
that layout (paragraph formatting) and character formatting have to be kept 
separated due to this. (Image layout dialogs being greyed out for character 
styles.)

> Anyway, I have a patch that only move the Font position to the Font effect
> tab. This solve the Format/Font dialog in 800x600 all together. And make
> the Style manager just a bit to big (height wise) but the buttons
> (OK,Cancel...) are now reachable. I do not know if this patch is
> interesting if the whole thing is going to have a face lift anyway.

Fix the bug first. (As we have not too much developers, it always possible 
that the changes would be for after KOffice 1.4.)

>
(...)
> >> >> 2. Create a "Paragraph flow" tab (better name welcome) that would
> >> >> group
> >> >>
> >> >> General/Next style (perhaps renamed to Style of next paragraph),
> >> >> Font/Font Effect/Language and Hyphenation.
> >> >
> >> >No!
> >> >
> >> >General/Next style is at layout level (layout == paragraph formating)
> >> >
> >> >But font effect, language and hypenation are charcter properties.
> >>
> >> I did not want to move font effect, just the langage and hyphenation (I
> >> was indicating the path, but I see now that it was not very clear) and
> >
> >the
> >
> >> next style.
> >>
> >>
> >> I agree that langages are not always used at the whole paragraph and can
> >> be used at a word level. However, I don't agree it is a character
> >> property. The minimum item you will give a langage property is a word
> >> and most of the time it is set for paragraphs. In order to set it for an
> >> individual word we might need to add a langage sub-menu in the format
> >> menu. I would definitly not expect to find the langage setting in Fonts.
> >
> >But it is a character property. If you want it word-wise you cannot have
> >it
> >paragraph-wise. A property can be at paragraph level or at character
> > level.
> >
> >That is all. (That perhaps "font" is a bad title is perhaps another
> > problem.)
>
> OK. I understand the problem now. (Sorry to be a bit slow but I just
> started to have a look at Koffice and programming in general). I will give
> a thorough thinking (yes, with the proper fuel, I can do this :) ). I still
> think that there is a way to accomodate the programming constraints and
> still have something logical on the user perspective.

Yes, of course, I suppose that the user interface could be improved. I just 
wanted to tell that we have constraints so that we cannot mix the properties 
freely (because otherwise users would not understand anymore what is only
paragraph-level only and what can be done at character-level too.)

>
(...)
> >
> >> >> Pierre
> >
> >Have a nice day!
(...)

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]