-------- Original-Nachricht -------- > Datum: Wed, 12 Jan 2011 15:45:57 +0300 > Von: "Dmitriy Osminskiy" <i...@realsoft3d.ru> > An: mengil...@gmx.net > CC: begg...@telia.com, user-list@light.realsoft3d.com > Betreff: Re: particle
> In other words, the user appears in a situation when the > package has all necessary possibilities but the user does not know as >them > to apply in working process. Exactly. Especially this JavaScript thing was something that irritated me in the way you wrote here. Especially when talking about shaders/materials, it´s hard for me to see what effects I can achieve with JavaScript, or what effects I possibly can ONLY achieve with javascript. But assuming that you can achieve some effects with JavaScript that you can´t achieve with VSL, then this is pretty awkward - already given a multitude of ways to handle materials, JavaScript just doesn´t fit in very well. If we then take into account the additional possibility of programming shaders (or whatever) directly in C/C++ via the SDK, we get a mashup of half a dozen ways to define material properties, each giving an individual range of possibilities that are hard to comprehend. Maybe the perfect solution for a given problem is amongst these, but chances are you won´t even know if that is the case or not. Greetz Martin -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
