Le 14/09/2010 02:13, Reactor a écrit :
> Christian Froeschlin <chr### [at] chrfrde> wrote:
>> Stephen wrote:
>>
>>> Thanks for your reply Le I thought that be the case but I was hoping
>>> that there was some undocumented function that everyone but me knew.
>>
>> I don't think so. What you can do, though, is call POV-Ray from
>> the command line where you can control the file names and even pass
>> them to the scene via generated include file.
>>
>>> It is a slight pain to change the code manualy as I save my files
>>> incrementally, a lot, as I make changes in the scene.
>>
>> Maybe source control should be integrated into the Windows editor ;)
> 
> That actually crossed my mind a while ago - making a full IDE type environment
> for POV-ray.  I like the idea of having a project file that tracks the scene
> files, included files, images, etc.  Even better if it has the ability to jump
> between identifier definitions and their references across files...
> 

Ever heard of povclipse ?

> At one point I was looking into existing IDEs that have the ability to syntax
> highlight or 'compile' for any language that you give it a definition file for.
> The idea is that it has already been done very well, and this would simply be
> the reuse of existing packages.

povclipse ran on eclipse.

-- 
A good Manager will take you
through the forest, no mater what.
A Leader will take time to climb on a
Tree and say 'This is the wrong forest'.

Post a reply to this message