Re: [Synfig-devl] dev priority perk claim
Hi! Realistically, to properly choose a development priority it's need to balance between need and effort. As I've mentioned several times, current bones implementation is not the really good implementation. As Konstantin sated at the LGM development priorities meeting, a bone feature has to be implemented via layer, that is, context based. Current bone code is valuenode based so it has to be rewritten completed to turn it into a context based. Maths are there in the current code, so the big deal is not the maths but the integration with the render system. On the other hand, sound layer implemented via no jack mode is not realistic until the on canvas playing with live feedback is a reality. Since some wanted features are dependent on others, I think that those others must be implemented 2013/10/26 Yu Chen jco...@gmail.com: Hi Konstantin and Carlos, I'm going to claim 300$ for the campaign of next month, and personally, I prefer one of two: sound layer and bone layer. But since you would better knowing which one is more reality in one month of development, could you please comment here? Or you have other options instead of the above. My attending of this campaign is not because I need those two features for my life or job, the only reasons are I am enjoying my stay here with you and the other people from community, and hope to help Synfig development as much as I can. Enjoy synfiging ^_^ Hi, Yu! This is a great news for us! Thank you! About the priorities. I think the bones priority is more real sound layer. From one hand, the bones feature is already have some code. From the other hand, the sound problem is related to solving real-time visualization problem, which is hard to estimate. (BTW, Carlos recently made some really neat implementation of new rendering type trying to achieve the real-time feedback. But shame on me, I haven't managed to test it yet!) Also, the sound problem can be partially resolved by the implementing JACK integration, which (I believe) can be done in much cheaper than $300. ^__^ Finally, about other options. From my point of view, the frame-by-frame animation support would be a total favorite for many animators. Best, K. -- http://morevnaproject.org/ -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] dev priority perk claim
Understand it, so I choose bone layer implementation for next month, and as you may know, I finished my $300 donation already. Thanks and regards. Yu Sent from Windows Phone -- 发件人: Carlos López González genet...@gmail.com 发送时间: 2013/10/27 0:58 收件人: Konstantin Dmitriev ksee.zelga...@gmail.com; Yu Chenjco...@gmail.com; synfig-devl@lists.sourceforge.net 主题: Re: dev priority perk claim Hi! Realistically, to properly choose a development priority it's need to balance between need and effort. As I've mentioned several times, current bones implementation is not the really good implementation. As Konstantin sated at the LGM development priorities meeting, a bone feature has to be implemented via layer, that is, context based. Current bone code is valuenode based so it has to be rewritten completed to turn it into a context based. Maths are there in the current code, so the big deal is not the maths but the integration with the render system. On the other hand, sound layer implemented via no jack mode is not realistic until the on canvas playing with live feedback is a reality. Since some wanted features are dependent on others, I think that those others must be implemented 2013/10/26 Yu Chen jco...@gmail.com: Hi Konstantin and Carlos, I'm going to claim 300$ for the campaign of next month, and personally, I prefer one of two: sound layer and bone layer. But since you would better knowing which one is more reality in one month of development, could you please comment here? Or you have other options instead of the above. My attending of this campaign is not because I need those two features for my life or job, the only reasons are I am enjoying my stay here with you and the other people from community, and hope to help Synfig development as much as I can. Enjoy synfiging ^_^ Hi, Yu! This is a great news for us! Thank you! About the priorities. I think the bones priority is more real sound layer. From one hand, the bones feature is already have some code. From the other hand, the sound problem is related to solving real-time visualization problem, which is hard to estimate. (BTW, Carlos recently made some really neat implementation of new rendering type trying to achieve the real-time feedback. But shame on me, I haven't managed to test it yet!) Also, the sound problem can be partially resolved by the implementing JACK integration, which (I believe) can be done in much cheaper than $300. ^__^ Finally, about other options. From my point of view, the frame-by-frame animation support would be a total favorite for many animators. Best, K. -- http://morevnaproject.org/ -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] dev priority perk claim
Oh dear, my latest email was truncated and the last part wasn't delivered! Damn mobile! Anyway, congratulations for the chosen perk! El 27/10/2013 06:02, Yu Chen jco...@gmail.com escribió: Understand it, so I choose bone layer implementation for next month, and as you may know, I finished my $300 donation already. Thanks and regards. Yu Sent from Windows Phone -- 发件人: Carlos López González genet...@gmail.com 发送时间: 2013/10/27 0:58 收件人: Konstantin Dmitriev ksee.zelga...@gmail.com; Yu Chenjco...@gmail.com; synfig-devl@lists.sourceforge.net 主题: Re: dev priority perk claim Hi! Realistically, to properly choose a development priority it's need to balance between need and effort. As I've mentioned several times, current bones implementation is not the really good implementation. As Konstantin sated at the LGM development priorities meeting, a bone feature has to be implemented via layer, that is, context based. Current bone code is valuenode based so it has to be rewritten completed to turn it into a context based. Maths are there in the current code, so the big deal is not the maths but the integration with the render system. On the other hand, sound layer implemented via no jack mode is not realistic until the on canvas playing with live feedback is a reality. Since some wanted features are dependent on others, I think that those others must be implemented 2013/10/26 Yu Chen jco...@gmail.com: Hi Konstantin and Carlos, I'm going to claim 300$ for the campaign of next month, and personally, I prefer one of two: sound layer and bone layer. But since you would better knowing which one is more reality in one month of development, could you please comment here? Or you have other options instead of the above. My attending of this campaign is not because I need those two features for my life or job, the only reasons are I am enjoying my stay here with you and the other people from community, and hope to help Synfig development as much as I can. Enjoy synfiging ^_^ Hi, Yu! This is a great news for us! Thank you! About the priorities. I think the bones priority is more real sound layer. From one hand, the bones feature is already have some code. From the other hand, the sound problem is related to solving real-time visualization problem, which is hard to estimate. (BTW, Carlos recently made some really neat implementation of new rendering type trying to achieve the real-time feedback. But shame on me, I haven't managed to test it yet!) Also, the sound problem can be partially resolved by the implementing JACK integration, which (I believe) can be done in much cheaper than $300. ^__^ Finally, about other options. From my point of view, the frame-by-frame animation support would be a total favorite for many animators. Best, K. -- http://morevnaproject.org/ -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
