>>>>> "Anders" == Anders Brander <[email protected]> writes: Anders> If you're manipulating XML, then you could add your images to Anders> ~/.rawstudio/batch-queue.xml - then you would only have to press Anders> start after starting Rawstudio. It's not CLI, but I think it's Anders> the best we can do.
We're talking about thousands of runs. Monkey at keyboard is not an acceptable solution. Do I really understand you correctly? Are you telling me that making Rawstudio respond to command line arguments is horribly difficult, and likewise that making it not show a window while batch processing would require a lot of work? If so, I would wager that the code would not be any worse off for a refactoring... :-) MVC and all that. >> Throw in the ability to batch process an entire folder, and >> preferably only the files of a given priority in that folder, now >> that you're at it; I sorely miss that sometimes. I'd like the ability >> to put a remote machine to work without being bound by a low >> bandwidth or low latency network connection. Anders> I'm sorry, but I don't think you'll be able to do that in the Anders> near future. Rawstudio really needs an X server. Why is it necessarily so dependent on one for batch processing. Mind you, I'm only talking about batch processing, nothing else. Anders> Current development tree is "very" multithreaded. Both Anders> interactive, background tasks and batch processing. Expect Anders> version 2.0 to take advantage of multiple cores/cpu's. Nifty! I'll try playing around with it. How difficult was it to go from single-threaded to multi-threaded code? In my experience, if you want to do properly synchronous code, it's almost a requirement that you consider it in your design from the very beginning. Martin _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
