POV-Ray : Newsgroups : povray.general : Visual Studio Code as a Cross-Platform POV-Ray Editor with Integrated Rende= Server Time
31 Oct 2024 19:39:29 EDT (-0400)
  Visual Studio Code as a Cross-Platform POV-Ray Editor with Integrated Rende= (Message 11 to 12 of 12)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: J  Max Wilson
Subject: Re: Visual Studio Code as a Cross-Platform POV-Ray Editor with Integrated R=
Date: 1 Jul 2019 15:40:00
Message: <web.5d1a608efb642dd8cad34d700@news.povray.org>
Just a quick update on the POV-Ray extensions for Visual Studio Code:

We're now up to over 200 installs of the extension!

https://marketplace.visualstudio.com/items?itemName=jmaxwilson.vscode-povray

I'm neck deep in a work project, but there will be additional enhancements and
features.

J. Max


Post a reply to this message

From: Mr
Subject: Re: Visual Studio Code as a Cross-Platform POV-Ray Editor with Integrated R=
Date: 28 Feb 2022 18:15:00
Message: <web.621d572dfb642dd834c7846e6830a892@news.povray.org>
"J. Max Wilson" <nomail@nomail> wrote:
> Just a quick update on the POV-Ray extensions for Visual Studio Code:
>
> We're now up to over 200 installs of the extension!
>
> https://marketplace.visualstudio.com/items?itemName=jmaxwilson.vscode-povray
>
> I'm neck deep in a work project, but there will be additional enhancements and
> features.
>
> J. Max

Hello,
I've been using your extension progressively because I tend to switch platforms
and editors a lot. The syntax highlighting of pov files in the same app that
could also highlight the python files of the Blender to povray addon was
attractive, as in: debug the python by looking at their output pov files and the
terminal render log... All seamlessly! Even though I love some killer features
and UX of PyCharm, Vim ubiquity, OS lightness of QTpov, feature wealth of
POVWin, the cross platform + cross languages + killer extensions of VScod(ium)
could make yours another absolute must have, aside from any heart felt
preference.

Now, I do this on a mac and there, the build task is not setup out of the box
and when I manage to set it up, I keep having to redo it manually depending on
the folders I'm in. Isn't there a way to make this be setup automagically more
globally even when no folder is open or stay valid when we move at of some
project's scope ? I also have a bad untrusted workspace default for pov which
isn't the case with other formats I open.

To update the syntax, maybe what we did for the Blender text editor can help you
get partway there?
(https://fossies.org/linux/blender/source/blender/editors/space_text/text_format_pov.c
and
https://fossies.org/linux/blender/source/blender/editors/space_text/text_format_pov_ini.c)


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.