Thanks Ichiro for sharing your insights. They greatly help to bring the work needed for a real production into perspective. For all who wonder what it actually can take, a rough estimate of "work hours" needed based on what you said and assuming the standard 8 hour day (rarely happens), I figure about 1000-2000 hours of hands-on time. And that assumes one knows the software being used pretty well.

Interesting also about your way of taking a break at times from the project. It makes a great deal of sense, not only to avoid "burn-out", but also to allow the ideas used in the project to be processed by the brain and to mature into what one can call well-rounded solutions. That probably makes the final end result so much better.

Interesting ...

cheers,
tindust