 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
As an aside, Bishop 3D announced in September that they are going to
release their next version as open source software.
Perhaps, instead of worrying about long dead kpovmodeler, it might be
wiser if the community rallied around updating Bishop 3D.
Just my 2 cents,
Todd
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/21/2015 3:37 PM, Todd Carnes wrote:
> On 2015-11-21 06:14, LanuHum wrote:
>> You want to have the adequate editor for Povray?
>> My experience shows that you aren't interested in it!
>
> Bishop 3D & Wings 3D both export to POV-Ray.
>
Bishop 3D could also import a subset of Povray code. Which is very handy.
>
> Todd
>
> As an aside, Bishop 3D announced in September that they are going to release their
next version as open source software.
>
It was September last year that Hugo posted that announcement. Not heard
anything since. :-(
> Perhaps, instead of worrying about long dead kpovmodeler, it might be wiser if the
community rallied around updating Bishop 3D.
>
I think that LanuHum was just using kpovmodeler as an example.
If you remember in Pov-Ray's heydays there was a distinct lack of
interest in modellers. Many a Flame-war was started decrying them.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2015-11-21 09:10, Stephen wrote:
>
>>
>> Todd
>>
>> As an aside, Bishop 3D announced in September that they are going to
>> release their next version as open source software.
>>
>
> It was September last year that Hugo posted that announcement. Not heard
> anything since. :-(
Sorry, my mistake. I misread the date.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2015-11-21 09:10, Stephen wrote:
> I think that LanuHum was just using kpovmodeler as an example.
> If you remember in Pov-Ray's heydays there was a distinct lack of
> interest in modellers. Many a Flame-war was started decrying them.
Perhaps, that's why we STILL haven't seen anything come of Moray?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/21/2015 5:33 PM, Todd Carnes wrote:
> On 2015-11-21 09:10, Stephen wrote:
>> I think that LanuHum was just using kpovmodeler as an example.
>> If you remember in Pov-Ray's heydays there was a distinct lack of
>> interest in modellers. Many a Flame-war was started decrying them.
>
> Perhaps, that's why we STILL haven't seen anything come of Moray?
It could be. Then there is also the cost (in man hours) of converting
propriety software to open source. That is why I am pleased that MR and
LanuHum are creating exporters for Blender. Then we can have an
integrated Mesh Editor for PovRay. :-)
> Sorry, my mistake. I misread the date.
Wishful thinking, I expect. :-)
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen <mca### [at] aol com> wrote:
>
> I think that LanuHum was just using kpovmodeler as an example.
> If you remember in Pov-Ray's heydays there was a distinct lack of
> interest in modellers. Many a Flame-war was started decrying them.
>
>
>
> --
>
> Regards
> Stephen
Yes. This is example
My dear developers joke...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen <mca### [at] aolcom> wrote:
> On 11/21/2015 3:37 PM, Todd Carnes wrote:
> > On 2015-11-21 06:14, LanuHum wrote:
> >> You want to have the adequate editor for Povray?
> >> My experience shows that you aren't interested in it!
> >
> > Bishop 3D & Wings 3D both export to POV-Ray.
> >
>
> Bishop 3D could also import a subset of Povray code. Which is very handy.
>
>
>
> >
> > Todd
> >
> > As an aside, Bishop 3D announced in September that they are going to release their
next version as open source soft
ware.
> >
>
> It was September last year that Hugo posted that announcement. Not heard
> anything since. :-(
>
> > Perhaps, instead of worrying about long dead kpovmodeler, it might be wiser if the
community rallied around updatin
g Bishop 3D.
> >
>
> I think that LanuHum was just using kpovmodeler as an example.
> If you remember in Pov-Ray's heydays there was a distinct lack of
> interest in modellers. Many a Flame-war was started decrying them.
>
>
>
> --
>
> Regards
> Stephen
There is no problem in Qt5
Qt4 will be supported very long
But it doesn't influence a situation
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Todd Carnes <tod### [at] gmailcom> wrote:
> On 2015-11-21 06:14, LanuHum wrote:
> > You want to have the adequate editor for Povray?
> > My experience shows that you aren't interested in it!
>
> Bishop 3D & Wings 3D both export to POV-Ray.
>
> As for your comments regarding kpovmodeler, the thread that is
> referenced in that bug report is misleading at best.
>
> For instance, it claims that the source has been updated to Qt5. That is
> not true. In fact, the source is set up to compile for KDE 3 and Qt 4.
>
> I have recently (yesterday) downloaded the so-called kpovmodeler-Qt5
> source in hopes of reviving it, but it looks like it will NOT be an easy
> task.
>
> My hope is to get rid of all the KDE crap and make it a pure Qt 5 app,
> but that's not something that will happen any time soon.
>
> Todd
wings3d - only mesh
blender - all shapes. The desire and support is necessary
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 21.11.2015 um 15:14 schrieb LanuHum:
> You want to have the adequate editor for Povray?
> My experience shows that you aren't interested in it!
> Blender? Yes, has problems, but Povray has no that it would be impossible to
> present lists.
> My notes allow to connect any material created by you, but to you isn't present
> to this interest. What do you want? Blender can be built as the Python module.
> Having desire it is possible to write own graphical representation, using import
> bpy(import blender)
You're doing a good job trying to bridge the gap between Blender and
POV-Ray, but there's one thing you can't accomplish, which Anthony
expressed discontent about:
Blender can't import POV-Ray geometry.
As a matter of fact, in a strict sense, Blender can't /import/ anything
from POV-Ray at all. It is possible to paste POV-Ray code snippets into
Blender scenes, but they remain POV-Ray code snippets; Blender has no
idea what they mean, and can't do anything with them except feed them
back to POV-Ray.
Because Blender can't import POV-Ray geometry, its cloth simulation
can't be used for existing POV-Ray scenes.
It is not your fault that this is still impossible; as a matter of fact,
it is fundamentally impossible (well, actually just highly infeasible)
to solve this issue at the Blender side.
What is really needed is an effort from the POV-Ray team to either (a)
add export functionality to POV-Ray, so that scenes can be exported in
popular geometry formats that can then be imported into Blender, or (b)
decouple POV-Ray's parser code from the main program, making it a
library that can be used in other projects, like a Blender import module.
Some people have also tried solution (c), which is programming a parser
for POV-Ray files from scratch, but with so many quirks in POV-Ray's
language it is virtually unavoidable that it behaves differently from
the original, so I think that's not a viable approach in the long run.
The POV-Ray team does have (b) comparatively high on the agenda, but
we're not there yet, and in contrast to your work there is nothing fancy
we can show right now, as it is all about modifying the underlying
architecture.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/21/2015 2:14 PM, LanuHum wrote:
> You want to have the adequate editor for Povray?
> My experience shows that you aren't interested in it!
Some history:
For a lot of people, PovRay was a "scripting" program and using a GUI
was a cheat.
Note. I am not saying that Clipka thinks that. But it is how PovRay grew up.
> Blender? Yes, has problems, but Povray has no that it would be impossible to
> present lists.
If I understand you. That is good.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
