Hi, (I realize it's more than a month since my last post to this list,but let me assure you, I'm not dead, just married!)
On Sun, 2007-05-13 at 21:59 +0200, Anders Kvist wrote: > I've just been chatting with Anders Lauritsen (the mysterious guy to the > left in the release planning meeting image - Why doesn't anybody ask if all Danes are named Anders? :) > http://rawstudio.org/news.php), who had helped with the rawstudio > development some time ago. He offered to integrate a script language in > rawstudio for pre- and postprocessing. He was suggesting Python as > scripting language, which seems fine with me. > > Any comments on implementation, language or ? I think it's a nice idea - but as Mr. Egger, I feel we have bigger fish to fry, but if Anders Lauritsen is up to the task, I see no reason to stop him :) Some discussion starters: Should this scripting engine expose Rawstudios internal api to Python? Should there be an inline text-editor for scripting? Do we need to place hooks at appropiate functions? (load/save etc) Does this go hand in hand with a plugin architecture? Would it help to make a librawstudio? Is Python easy to implement? Is this simply a problem of linking to the appropriate python-libs? Will it result in (more) external dependencies? /abrander _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
