i made a step back, and fixed the previous implementation of push-pop, and now it seems it works: multiple nested push-pop loops are rendered correctly as in nodebox, and it's a lot faster now, not as fast as nodebox, but we're approaching it! feels much better :-) f.
Il giorno sab, 22/11/2008 alle 11.27 +0100, francesco fantoni ha scritto: > ok, now i know where the bottleneck is: in my totally idiot > implementation of the push-pop thing. > > I think it makes sense to have push-pop logic in Transform class, and as > i designed now it apparently renders correctly even under complex nested > configurations of push-pop couples, the big problem is that in my > present implementation, when there are lot of push-pop, the path's > transform stack grows exponentially, slowing things down. It's quite > clear when you have a push-pop couple into a "for i in range()" loop > for example (as in the example > examples/nodebox/color_shader_example_2.bot). i think push and pop > "engine" should stay in transform class, but i'm afraid my code must be > completely re-thought, because as i've done it now it's pure crap! > sorry, f. _______________________________________________ Shoebot-devel mailing list [email protected] http://lists.tinkerhouse.net/listinfo.cgi/shoebot-devel-tinkerhouse.net
