Le 17-10-20 à 15:12, Bald Eagle a écrit :
> Is there a way to be able to use only the parser (and the editor)?
> 
> Just thinking it might be handy to have a stripped-down portable SDL language
> environment that doesn't require a registry-based installation.
> Something that could be run off a USB stick...
> 
> Is that possible - and 'straightforward'?
> 
> 

As for the editor, any text editor that save as simple ASCII will do.

As for the parser, it would need to save the parsed scene to be of any 
use. Then, you'd need to pass that to the renderer part.

As for running from an USB stick, you can always use the Linux, command 
line version. Useable under Windows by enabling the Unix environment 
available from Windows 7 onward.

Post a reply to this message

Am 21.10.2017 um 18:09 schrieb Alain:

> As for running from an USB stick, you can always use the Linux, command
> line version. Useable under Windows by enabling the Unix environment
> available from Windows 7 onward.

The "Windows Subsystem for UNIX-based applications" (SUA) has actually
been available from Windows Vista onward, and a predecessor, "Windows
Services for UNIX" (SFU), has been available from XP onward.

Both require a Server, Enterprise or Ultimate edition of Windows though.

The successor, "Windows Subsystem for Linux" (WSL), on the other hand,
is only available for Windows 10, but appears to be available on all
(64-bit) editions.

Post a reply to this message

hi,

re standalone editor

I like Vim (http://www.vim.org/).  it has syntax highlighting for the
SDL (and many other languages), and is cross-platform.

while no help with the parser, Vim's "make" command can be set to call
povray and render the scene file in the current buffer.

regards, jr.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:

> Do you want the Windows GUI and parser without the render engine? What
> good would that be?

I'd be able to write SDL on any computer I was sitting at, and check for proper
syntax and other errors without having to install POV-Ray on every box I used.

Color coded contextual highlighting is nice (I will check out VIM), but the
parser is really the thing that tells me if something's going to even GET TO the
render phase without choking on a missing include file, a missing ) or }, an
undeclared variable, etc.

It was just an idea for something useful, if it was simple enough to do.

A dream in a longer, narrower pipe would be to have an online editor / parser
that could be used in a browser...

Post a reply to this message

Le 17-10-23 à 13:03, Bald Eagle a écrit :
> clipka <ano### [at] anonymousorg> wrote:
> 
>> Do you want the Windows GUI and parser without the render engine? What
>> good would that be?
> 
> I'd be able to write SDL on any computer I was sitting at, and check for proper
> syntax and other errors without having to install POV-Ray on every box I used.
> 
> Color coded contextual highlighting is nice (I will check out VIM), but the
> parser is really the thing that tells me if something's going to even GET TO the
> render phase without choking on a missing include file, a missing ) or }, an
> undeclared variable, etc.
> 
> It was just an idea for something useful, if it was simple enough to do.
> 
> A dream in a longer, narrower pipe would be to have an online editor / parser
> that could be used in a browser...
> 
> 

You may want to take the Unix/Linux source files, remove/comment out the 
renderer part and compile.

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> clipka <ano### [at] anonymousorg> wrote:
>
> > Do you want the Windows GUI and parser without the render engine? What
> > good would that be?
>
> I'd be able to write SDL on any computer I was sitting at, and check for proper
> syntax and other errors without having to install POV-Ray on every box I used.
>
> Color coded contextual highlighting is nice (I will check out VIM), but the
> parser is really the thing that tells me if something's going to even GET TO the
> render phase without choking on a missing include file, a missing ) or }, an
> undeclared variable, etc.
>
> It was just an idea for something useful, if it was simple enough to do.
>
> A dream in a longer, narrower pipe would be to have an online editor / parser
> that could be used in a browser...

You can already run the Windows Povray version off a USB stick.

Post a reply to this message

"jhu" <nomail@nomail> wrote:

> You can already run the Windows Povray version off a USB stick.

Is there a special way I have to "install" it on the USB?
I tried to copy the bin directory onto a USB and run the executable, and got:




ERROR: Cannot find Home entry in registry (and cannot infer it).

This entry should have been set by the installation program.

POV-Ray can usually infer the installation path but that requires a standard
layout of directories, which also seems to be absent.

...... etc.

Post a reply to this message

Am 27.10.2017 um 13:53 schrieb Bald Eagle:
> "jhu" <nomail@nomail> wrote:
> 
>> You can already run the Windows Povray version off a USB stick.
> 
> Is there a special way I have to "install" it on the USB?
> I tried to copy the bin directory onto a USB and run the executable, and got:

> ERROR: Cannot find Home entry in registry (and cannot infer it).

You'd have to copy the whole POV-Ray install directory (e.g. `C:\Program
Files\POV-Ray\v3.7\`) to the USB stick (e.g. `E:\POV-Ray\v3.7\`).

In addition, you'd have to copy POV-Ray's directory of user-editable
files (sample scenes, include files etc., e.g.
`C:\Users\JohnDoe\Documents\POV-Ray\v3.7`) to the USB stick (e.g.
`E:\User\POV-Ray\v3.7\

On the system you want to work on, you'd then have to invoke the
following command once:

    pvengine.exe /INSTALL "E:\POV-Ray\v3.7\" "E:\User\POV-Ray\v3.7\"

(It should also be possible to throw both directories together on the
USB stick.)


However, this does not really qualify as a so-called "portable
installation", which is what most people expect when they talk about
"running program XY off a USB stick", as the above command does actually
modify the computer's registry. This means that it won't work on a
computer where you don't have the necessary administrative privileges.

Also, if you later work with POV-Ray on the same computer again, and
another USB stick happens to be plugged in, so that the USB stick's
drive letter changes (e.g. "F:" instead of "E:"), you have to invoke the
above command /again/ (with according changes).

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:

> You'd have to copy the whole POV-Ray install directory (e.g. `C:\Program
> Files\POV-Ray\v3.7\`) to the USB stick (e.g. `E:\POV-Ray\v3.7\`).
>
> In addition, you'd have to copy POV-Ray's directory of user-editable
> files (sample scenes, include files etc., e.g.
> `C:\Users\JohnDoe\Documents\POV-Ray\v3.7`) to the USB stick (e.g.
> `E:\User\POV-Ray\v3.7\

Did that, 'cause I figured I'd need those  ;)

> On the system you want to work on, you'd then have to invoke the
> following command once:
>
>     pvengine.exe /INSTALL "E:\POV-Ray\v3.7\" "E:\User\POV-Ray\v3.7\"
>
> (It should also be possible to throw both directories together on the
> USB stick.)
>
> However, this does not really qualify as a so-called "portable
> installation", which is what most people expect when they talk about
> "running program XY off a USB stick", as the above command does actually
> modify the computer's registry. This means that it won't work on a
> computer where you don't have the necessary administrative privileges.

.....

Exactly.
I was curious, as it would be something useful _for me_.

I'm assuming the same situation applies if I'm running it off of a network
drive.

Post a reply to this message

Am 27.10.2017 um 16:01 schrieb Bald Eagle:

>> However, this does not really qualify as a so-called "portable
>> installation", which is what most people expect when they talk about
>> "running program XY off a USB stick", as the above command does actually
>> modify the computer's registry. This means that it won't work on a
>> computer where you don't have the necessary administrative privileges.
> 
> ......
> 
> Exactly.
> I was curious, as it would be something useful _for me_.
> 
> I'm assuming the same situation applies if I'm running it off of a network
> drive.

Hm... I must correct my above statement: Admin privileges should /not/
be needed, as the registry keys are stored in HKCU (the current user's
registry stuff).

However, I've never tried this, so I can't vouch for it.

Post a reply to this message