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

List:       koffice-devel
Subject:    Re: Dialogs throughout KOffice
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2004-08-21 18:39:31
Message-ID: 200408212039.32784.nicolasg () snafu ! de
[Download RAW message or body]

Normally .ui dialogs for KOffice are based on QWidget and then integrated in 
code to KDialogBase (see for example koffice/filter/kword/html/export

Creating directly a QDialog with Qt Designer seems to create problems and so 
is seldom used in KDE.

The only little trick with a QWidget-based .ui file is how to place a layout. 
It must be on the top most object (the QWidget) and not as child. The problem 
is that if a translation (for example German) needs larger dialogs than in 
American English.

Have a nice day!

On Saturday 21 August 2004 13:47, p.stirnweiss_koffice@bluewin.ch wrote:
> >-- Message original --
> >Date: Fri, 20 Aug 2004 14:40:04 +0200
>
> From: Tomas Mecir <mecirt@gmail.com>
>
> >To: For developer's discussion about KOffice <koffice-devel@mail.kde.org>
> >Subject: Re: KSpread tasks
> >Reply-To: Tomas Mecir <mecirt@gmail.com>,
> >  For developer's discussion about KOffice <koffice-devel@mail.kde.org>
> >
> >> - Convert dialogs into UI (Qt Designer). Those dialogs are now in
> >> koffice/kspread/dialogs.
> >
> >Is this really needed? Personally, I find it more convenient to write
> >dialogs by hand. But then, others' opinion may vary ;)
> >
> >Personally, I'll currently focus on making KSpreadCell as light-weight
> >as possible, that should help a lot, then I'll see ... :)
>
> I am currently doing the tutorial on Qt Designer. It seems a very good way
> to implement the ui stuff. But then, I am reading Trolltech's material so
> of course the strong points are emphasised. Can somebody explain me the
> drawbacks of this?
> In addition, Thomas said he knows how to do the ui stuff but not implement
> the extension class. My question is: is it necessary in a project like
> KOffice to subclass the forms? Isn't Qt's form.ui.h technique usable
> (overhead...)? And what about the dynamic dialogs (I have not yet started
> this part of the tutorial, but the idea seems really seducing)?
>
> Is there a plan to implement all dialogs to this? I think it probably would
> be better to have all or none (for consistency and maintainability).
>
> This is definitelly something I am interested in doing, and is probably not
> too complicated to do (I hope).
>
>
> Pierre
>
> >/ Tomas
> >_______________________________________________
> >koffice-devel mailing list
> >koffice-devel@mail.kde.org
> >https://mail.kde.org/mailman/listinfo/koffice-devel
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
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]