Re: [kde-artists] oxygen style and kwin client, svn external

Hugo Pereira Da Costa <[email protected]>
Newsgroups gmane.comp.kde.artists,gmane.comp.kde.devel.kwin
Message-ID <[email protected]>
On 01/04/2010 04:32 PM, Aaron J. Seigo wrote:
> On January 4, 2010, Hugo Pereira Da Costa wrote:
>    
>>> what can happen is that it uses more cpu to achieve an animation since it
>>> may generates more frames than you strictly want (if the animation frame
>>> generation is quick), but the timespan itself should be no different. if
>>> anything, the animation should be smoother but more cpu intensive.
>>>        
>> well, that's the surprising part. It seems (to me) that the "tab"
>> transitions take more time (and is smoother) with QPropertyAnimation
>> than with QTimeLine,
>>      
> i wonder if it isn't just that there are more frames and therefore more visual
> transitions which then make it _feel_ slower (due to more happening visually).
> this could be completely psychological (so much is with animations ;). it may
> be that with QPropertyAnimation it is possible to shorten the duration of the
> animation for the same degree of quality/effect?
>    
could be.
I actually did shorten the time alocated to the tab transition from 250 
to 150msec after the change to kinetic. (great minds blah blah blah).

>    
>>> uses a shared timer. in the case of many animations running
>>> simultaneously, having a shared timer is usually better for
>>> coordination, wakeups, etc.
>>>        
>> True.
>>
>>      
>>>> I'm confident I can commit both before the branching tomorrow (since
>>>> this was the original plan).
>>>>          
>>> great; i've already got the oxygen style done, so i'll commit that then.
>>>        
>> It's all committed already.
>>      
> ah; that was fast. :)
>
> (as an aside: i find it's nice to let people commit their own work. it does a
> number of things: it gives them that "huzzah!" moment when the commit goes in
> as a nice reward, it prevents them ending up with conflicts in their checkout
> when you commit it for them and if there are things that need to be fixed
> first you can communicate it to them and have them fix it before committing.
> this way they learn what you want in your code. it's not a big deal in this
> case, but even if it does mean one has to wait some extra time for the other
> person to commit their patch, it's usually a good idea for community / team
> building. :)
>
> as for the shared library thing, i'm happy to help you with that as soon as
> 4.5 opens up so that we can get rid of the svn extern. i don't even mind doing
> the entire bit of work needed to make it happen. just let me know :)
>
>    
>> Right now I'm trying to address some of the
>> obvious bugs that have been reported.
>> (notably that Qt apps do not used a different text color for disabled
>> widgets, while kde apps do)
>>      
> great :) the oxygen theme set is coming along really nicely!
>
>    

______________________________________________________________________________
[email protected] |  https://mail.kde.org/mailman/listinfo/kde-artists
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.