*
* *
*
scene.org
Log in:
login for 1 year
No account? register here

Scene.org is hosted and supported by:
Scene.org is sponsored by:
* forum - #coders

*
Topic:  better way to speed up development..
* Posted by jippie Thursday 30 March 2006 - 11:01 
I have been thinking of way to speed up my development. So I thought I ask here.

What I see is that I add a lot of little effects and fine tune them until I get the look I want.
But this is all a change value here and a compile.
Real waste of time, what I was think was adding LUA so I then just need to load the script and try again.

So how do others solve this, it a script best way for this?

regards,

jippie

* Posted by _-_-__ Thursday 30 March 2006 - 11:35 
I wrote a few words about .. productivity .. inside the pdf report you can find at http://knos.free.fr/20060219/

To which I will add that I don't believe in scripting environments. The test/compile/feedback loop should be short, but having a full fledged scripting language impairs change of the core base. It's a pain to make sure the bindings are in sync with the underlying native code, I find.

What ultimately I would like but haven't yet developed is a simple plugin-like infrastructure. You'd have a main binary running constantly. You'd have your favorite c/c++ ide. Once a file is modified, a dll would be compiled. The main binary would pick up that the dll changed since its last load, and would reload that new version inplace and present it to you.

[Post edited by _-_-__ on Thursday 30 March 2006 - 11:38]

* Posted by smash Friday 31 March 2006 - 12:30 
the right environment for tweaking of parameters is a tool. =) create your effects, expose useful parameters and edit the values in the editor.
fx in a separate plugin dll is another good idea.

(both of these things we do in our demotool, and it's a very nice environment to work in.)

* Posted by _-_-__ Friday 31 March 2006 - 13:30 
Then again, I find tools are costly to make, and once they are made, they appear to sediment your possibilities at the bottom of your imagination ;)

Okay I just said that because it sounded good to me.

Let's say I treat the compiler + editor as a tool also, and I have a fetish against external resources. Although there is something I find interesting is to merge the tool and the demo.

Make the tool good enough aesthetically to serve as a demo, in a way.

[Post edited by _-_-__ on Friday 31 March 2006 - 13:38]

* Posted by kusma Tuesday 4 April 2006 - 1:36 
don't be a demo fool, make demo tool with demo tool tool.

* Posted by jippie Monday 10 April 2006 - 22:08 
Can I see yur "demotool" in action?
It would give me some ideas how and what I need to do!!

jippie

*