Nice, I did something similar with an animation of a rotating
factor structure. What are represented in the x,y,z ?

Harold

"Gilles Tran" <git### [at] wanadoofr> wrote in message
news:3e41a8e7@news.povray.org...

> 3e419903@news.povray.org...
> > Gilles,
> > We are probably doing similar things. No doubt your
> > programing is much better and produces more sophisticated
> > graphs. I'll post a simple example in p.b.i., I'd be interested in
> > seeing what you are doing.
>
> It's probably the other way round, mine just takes a bunch of x,y points
and
> draws a scatter plot plus a regression line. These are really crummy
> graphics (16 colors, 200x200, blue on white) but they're small, there's a
> lot of them and people love them. There's an animated one here
> http://www.inapg.inra.fr/dsa/afz/tables_documents.htm (the AVI file called

> only appreciated by those who know what it's all about!
> Creating the script was a piece of cake. Creating the vb script that
> calculates the regression statistics, on the other hand... I spent a week
on
> it and needed help from the maths/stats department here.
>
> G.
>
>
> --
> **********************
> http://www.oyonale.com
> **********************
> - Graphic experiments
> - POV-Ray and Poser computer images
> - Posters
>
>
>
>

Post a reply to this message

3e41aa0b$1@news.povray.org...
>
> Nice, I did something similar with an animation of a rotating
> factor structure. What are represented in the x,y,z ?

The protein, fibre and starch content of rice bran samples. The plane is the
regression plane Starch = a + b * Protein + c * Fibre. It also shows the
main rice bran types (the macro detect the codes used to identify the
populations and give them different colors).

G.

--

**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message

>>could anyone explain to me how I can run povray from an external program so
>>that povray will "silently" render the picture to a specified folder, but
>>have it so that the main povray interface does not become visible.
> 
> 
> No.  Read the license.  That isn't allowed.

1. It IS possible with the Unix version.
2. Povray would be rather useless (to me anyway)
    if it were not.
3. I just read the license and could not find
    what you meant.
    It should be in USAGE PROVISIONS, right?

So far I mostly used povray by call from other
programs. I made those programs (not including
povray) available to others. Was that wrong?
If so, I will have to look for another raytracer.

   Mark

Post a reply to this message

"Mark Weyer" <wey### [at] informatikuni-freiburgde> wrote in message
news:3E4### [at] informatikuni-freiburgde...
>
> 1. It IS possible with the Unix version.
> 2. Povray would be rather useless (to me anyway)
>     if it were not.
> 3. I just read the license and could not find
>     what you meant.
>     It should be in USAGE PROVISIONS, right?
>
> So far I mostly used povray by call from other
> programs. I made those programs (not including
> povray) available to others. Was that wrong?
> If so, I will have to look for another raytracer.
>

I assume that this is the relevant part of the licence (in the "permitted
modifications" section):

<start>

All executables, documentation, modified files and descriptions of the same must
clearly identify themselves as a modified and unofficial version of POV-RayT.
Any attempt to obscure the fact that the user is running POV-RayT or to obscure
that it is an unofficial version is expressly prohibited.
POV-RayT may not be linked into other software either at compile-time using an
object code linker nor at run-time as a DLL, ActiveX, or other system. Such
linkage can tend to blur the end- user's perception of which program provides
which functions and thus qualifies as an attempt to obscure what is running.

To allow POV-RayT to communicate with outside programs, the official versions of
POV-RayT may include internal communication "hooks" for it to call other tasks,
often called an Application Programming Interface, or API. For example: the
generic part of POV-RayT provides operating system shell-out API commands. The
Windows version has a GUI-extension API and the ability to replace the text
editor. Modification to these APIs or other officially supported communication
mechanisms to increase functionality beyond that of the official version, or to
avoid the intent of this license, is EXPRESSLY PROHIBITED.

<end>

As far as I understand, if you haven't modified POV, and you aren't attempting
to obscure POV's role in what you are doing, then you are okay.

Of course, "obscure", is a slightly ambigous term - I would take it to mean (in
your case) that the use of POV should feature prominently in the documentation
of your apps., butwhaddaiknow?

Post a reply to this message

> As far as I understand, if you haven't modified POV, and you aren't attempting
> to obscure POV's role in what you are doing, then you are okay.
> 
> Of course, "obscure", is a slightly ambigous term - I would take it to mean (in
> your case) that the use of POV should feature prominently in the documentation
> of your apps., butwhaddaiknow?

Thank you. I never gave my modifications of povray to
anyone. There is no documentation to speak of but all
recipients know the role of povray in the application.
Until anybody tells me wrong I will assume that what I
do is OK.

However this discussion has had the effect of a
   decrease_key (find a replacement for povray or write one)
on my projects priority queue.

   Mark

Post a reply to this message

"Mark Weyer" <wey### [at] informatikuni-freiburgde> wrote in message
news:3E4### [at] informatikuni-freiburgde...
>
> Thank you. I never gave my modifications of povray to
> anyone. There is no documentation to speak of but all
> recipients know the role of povray in the application.
> Until anybody tells me wrong I will assume that what I
> do is OK.
>
> However this discussion has had the effect of a
>    decrease_key (find a replacement for povray or write one)
> on my projects priority queue.
>

The bottom line (afaik) is that this part of the licence is to prevent
unscrupulous sellers getting people to pay for a free program. If you ain't
doing that, I can't see what the problem would be. Also, as well as the fact
that you aren't modifying pov, it sounds as though you aren't really
distributing your progs either - in the sense that they are only available to a
clique rather than the general public.

A comment from someone who actually knows what they are talking about would be
useful about now....

Post a reply to this message

> A comment from someone who actually knows what they are talking about would be
> useful about now....

Agreed (no offence intended)

Post a reply to this message

"Harold" <bai### [at] 3dculturecom> wrote in message
news:3e416b79$1@news.povray.org...

> POV script files and shell out to POV-Ray, but I've never
> seen any reason to hide the interface. I do think it is possible
> using the command line options, but why bother?

the thought did occur - hey, Gilles, Mark, why do you need to hide it? What
happens if you don't?

Post a reply to this message

In article <3e416dc4@news.povray.org>, git### [at] wanadoofr says...

> 3e4164ea@news.povray.org...
> > No.  Read the license.  That isn't allowed.
> 
> Before jumping to conclusions about potential wrongdoings and license
> violations, he may have legitimate reasons to do so.
> I'm launching POV-Ray from Access to create graphics for the database I'm
> running at work. I'm using the DOS version of POV-Ray 3.1 to avoid having
> the splash screen pop up every time I create a graphic (I've done 3000 of
> them so far). I'm the sole user, so I definitely don't hide to myself the
> fact that I'm using POV-Ray ;-)
> 
> G.
> 
> 
> --
> **********************
> http://www.oyonale.com
> **********************
> - Graphic experiments
> - POV-Ray and Poser computer images
> - Posters
> 
This brings up an issue of something I was considering. The idea is in 
essence this:

Make a pge that also provides:
  A) Built in display window.
  B) Some basic controls like stop and pause/resume.
  C) Settings for image directory to use and location of the .pov file.
  D) Implements a COM interface, making it an insertable control in other 
programs, with the following calls:
    1. FTP file and render.
    2. UUDecode stream to file and render.
    3. Stop.
    4. Pause/resume.
    5. Set option.

The idea being to provide the control for free, but since the interface 
is implemented by the control itself, it can display the normal text 
streams in the display window, then switches to a graphic one when 
rendering starts (probably in a tab strip design). Thus it will always 
show the same info about POVRay version, etc as you would see in the 
main editor. Since the control is free, it could be included as a 
supported control with a program, but not as part of the program itself.

I think this would theoretically resolve the issues in the license as it 
stands, but I really don't understand how the bloody GUIExt interface 
works and if those streams even available to the extension (something 
that would tend to blow a hole in my idea). I don't really want to spend 
a lot of time trying to figure the interface out if I can't feed those 
streams through it or this idea has some unintentional defect with regard 
to the licensing...

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message

3e42bc46@news.povray.org...
> "Harold" <bai### [at] 3dculturecom> wrote in message
> news:3e416b79$1@news.povray.org...
>
> > POV script files and shell out to POV-Ray, but I've never
> > seen any reason to hide the interface. I do think it is possible
> > using the command line options, but why bother?
>
> the thought did occur - hey, Gilles, Mark, why do you need to hide it?
What
> happens if you don't?

The splash screen was a nuisance as it hid the main Access window, but the
main issue was Povray not exiting at the end. When launching a batch of
renders through VB this really caused problems. These could be solved,
perhaps, but using the old console version was just easier.

G.


--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message