 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I like Hugo Asm am by no means a C or C++ programmer. I can however write
programs in other languages. I came here to the programming forum to
second Hugo's request for some extensions to the #read directive in SDL.
Namely I was going to request the addition of some of the standerd file
reading functions:
get current byte position in an open file
set current byte position in an open file
return a string containing all data until the next newline charicture (get
line)
But while reading the replies to the post made by Hugo it occured to me that
no matter how many new directives are added to sdl it will never satisfy
everyone's needs. What Povray needs is a plug-ins API...
Amazing work has been done in the form of patchs like MegaPov, MLPov,
SlimePov etc. And in the case of MegaPov many patches have been brought
together to form the most advanced Pov pre 3.5. Each of these is seperate
though, they do not work together, and a scene writen for one will not
neccisarily work with another. Would it not make more sense to have a
standard method for writing plug-ins to extend Povrays capabilities? So
that the user would be able to chose which patches or features he or she
needs at any one time, and so that the user could use different patches
together in the same scene without needing to create a custom compile
themselves?
It would be difficult... In fact I don't think any one person could write a
standardized API to the Povray render engine. It would take a team of
programmers working together. But having a direct interface would allow
other programers to write useful utilities, extensions, objects and more
without spending months or years studying the Povray modules and how they
work together.
I cannot say how this could or should be done, I am just an artist. I can
program enough to make little utilities and tools for the work I do. I
have seen the source for Povray, and I cannot believe anyone can create
such a huge and amazing program. What I do know is that the current patch
system is limiting the number of people who can contribute to Povrays
abilities, and that a scriptable or programable interface could allow
greater versitility to this alread powerful tool.
Perhapse though this should be a feature for the next version of Povray, let
everyone start with an official unpatched version and build from there.
Wish I could help more on the implimentation of this, I really think it
would be a useful addition...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 11 May 2003 22:52:44 EDT, "Kitsune_e" <kit### [at] hotmail com> wrote:
> What Povray needs is a plug-ins API...
They are called "patches" here. And the initial API is at
http://megapov.inetart.net/manual/internals.html :-)
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.3ebf0c7ca214be38a7ab6a390@news.povray.org> , "Kitsune_e"
<kit### [at] hotmailcom> wrote:
> I like Hugo Asm am by no means a C or C++ programmer. I can however write
> programs in other languages. I came here to the programming forum to
> second Hugo's request for some extensions to the #read directive in SDL.
> Namely I was going to request the addition of some of the standerd file
> reading functions:
Before I respond to your "idea", I would like to make clear for everyone:
This group is not meant for *any* kind of feature requests by *users*. It
is for, and only for "Programming related discussion (i.e. source code
etc.)" of POV-Ray by *programmers* knowing or having (specific) questions
about the POV-Ray source code. So, please do not clutter this group with
unrelated discussion. The extreme noise level in this group by people who
got lost (due to the many groups) has always been a big problem in this
group, but *please* lets not make it worse!
> But while reading the replies to the post made by Hugo it occured to me that
> no matter how many new directives are added to sdl it will never satisfy
> everyone's needs. What Povray needs is a plug-ins API...
No, it does not and will not get such *nonsense* for good reasons that
should be really obvious to a programmer. If not, just look back at the
previous replies to this "plugin idea", usually coming up about once a
year...
Thorsten
(Note: While an official POV-Team response would find nicer words, the point
would remain the same.)
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Lets go to the advanced-users group and continue the talk.
I just posted there, still on the thread: Extending the #read directive
http://news.povray.org/3ebf5a59$1@news.povray.org
Thank you.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Kitsune_e <kit### [at] hotmailcom> wrote:
> What Povray needs is a plug-ins API...
You are free to suggest a way of implementing this so that it will work
in all systems POV-Ray is used (which includes, among others, Windows, MacOS,
Linux, Solaris, RiscOS, etc).
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
From: Nicolas Calimet
Subject: Re: Extending #read, another option...
Date: 12 May 2003 13:17:17
Message: <3EBFD71D.5010001@free.fr>
|
|
|
| |
| |
|
|
> It
> is for, and only for "Programming related discussion (i.e. source code
> etc.)" of POV-Ray by *programmers* knowing or having (specific) questions
> about the POV-Ray source code.
Is this too late to change "programming" to something else ? Maybe
"p.source-code" or "p.engine-internals" or much better ? With "programming"
those who think ("using the SDL" == "programming POV") end up in here...
Post a reply to this message
|
|
| |
| |
|
|
From: Christoph Hormann
Subject: Re: Extending #read, another option...
Date: 12 May 2003 13:31:23
Message: <3EBFDA6B.FA204A36@gmx.de>
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>
> > It
> > is for, and only for "Programming related discussion (i.e. source code
> > etc.)" of POV-Ray by *programmers* knowing or having (specific) questions
> > about the POV-Ray source code.
>
> Is this too late to change "programming" to something else ? Maybe
> "p.source-code" or "p.engine-internals" or much better ? With "programming"
> those who think ("using the SDL" == "programming POV") end up in here...
You will probably have noticed that from the last 6 threads in this group
there was none 'off-topic because only SDL-related'. Still 4 should
better have been started in a different group.
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 28 Feb. 2003 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
>On Sun, 11 May 2003 22:52:44 EDT, "Kitsune_e" <kit### [at] hotmailcom> wrote:
>> What Povray needs is a plug-ins API...
>
>They are called "patches" here. And the initial API is at
>http://megapov.inetart.net/manual/internals.html :-)
>
>ABX
>
I obviously know about patches since I mention several in my post, and I
already knew that there was a programers referance in the Megapov docs.
This is not what I am discussing.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Before I respond to your "idea", I would like to make clear for everyone:
>This group is not meant for *any* kind of feature requests by *users*. It
>is for, and only for "Programming related discussion (i.e. source code
>etc.)" of POV-Ray by *programmers* knowing or having (specific) questions
>about the POV-Ray source code. So, please do not clutter this group with
>unrelated discussion. The extreme noise level in this group by people who
>got lost (due to the many groups) has always been a big problem in this
>group, but *please* lets not make it worse!
>
>> But while reading the replies to the post made by Hugo it occured to me that
>> no matter how many new directives are added to sdl it will never satisfy
>> everyone's needs. What Povray needs is a plug-ins API...
>
>No, it does not and will not get such *nonsense* for good reasons that
>should be really obvious to a programmer. If not, just look back at the
>previous replies to this "plugin idea", usually coming up about once a
>year...
>
I would not have posted here except that it was requested that I post here
by Hugo. Also I attempted to shift the discusion into a more programming
oriented direction.
As for non-sense I do not understand why how giving other programs access to
Povray's internal data is non-sense, or why it cannot be made portable
among machines with similar architecture?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>Kitsune_e <kit### [at] hotmailcom> wrote:
>> What Povray needs is a plug-ins API...
>
> You are free to suggest a way of implementing this so that it will work
>in all systems POV-Ray is used (which includes, among others, Windows, MacOS,
>Linux, Solaris, RiscOS, etc).
>
>#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
>N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
>N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
>
I have read no articles on building plug-ins, I do not know specific
methods. It occures to me that C has generaly the same data structures
accrossed multiple platforms (string int double etc). C is ment to be
portable, the compiler should handle any non-system specific code on any
system. I do not know if that is the case in practice though.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
