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

List:       kde-devel
Subject:    Re: Advice on Qt User interface
From:       Hugo Pereira Da Costa <hugo.pereira () free ! fr>
Date:       2009-10-27 22:32:46
Message-ID: 4AE7750E.3080902 () free ! fr
[Download RAW message or body]

On 10/27/2009 03:53 PM, Wagner Sales wrote:
> Hi Hugo,
>
> This advice are based on my own experience, since this, don't take an
> "official" advice.
> If you have GUI that's changes a lot dynamically at run time, may be
> will be better not use Designer. If not, Designer ( yes, I know you
> hate :) ) will be a good friend.
> The current Designer's approach are very better than the old Qt 3
> Designer's approach. Try to do a little experience with Qt Creator and
> Designer to see how the things are done.
> I think after some time you'll be very surprised and a lot of time can
> be saved. I think more easy to do and and maintain complex but static
> GUI by using Designer.
>    
ok. You got me on the use case. I'm talking on a "configuration" UI 
(namely oxygen style)
Pretty static. I guess I'll give another shot to designer :)
> Regards,
>
> Wagner
>
> 2009/10/27 Hugo Pereira Da Costa<hugo.pereira@free.fr>:
>    
>> Hi,
>>
>> Newbie question. What's the policy on designing user interfaces (Qt based)
>> in KDE:
>> use UI files rather than brute force c++, or indiferent ?
>> I personally hate Qt designer (for my own reasons) and have been used to
>> design my UI in brute force c++.
>> Are there some known disadvantages with this approach ? Or historical
>> reasons against it ?
>>
>> Thanks in advance,
>>
>> Hugo
>>
>>      
>
>    
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe<<
>>>        
>
>    

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]