POV-Ray : Newsgroups : povray.programming : povmodeler Server Time: 22 Nov 2019 05:50:00 GMT
  povmodeler (Message 1 to 10 of 38)  
Goto Latest 10 Messages Next 10 Messages >>>
From: simbad
Subject: povmodeler
Date: 27 Oct 2019 13:20:01
Message: <web.5db5988d68e3c02c9cfad62f0@news.povray.org>
Hello all,

I did a fork of eticres excelent work, https://github.com/eticre/povmodeler, on
removing the KDE stuff from the original source and moving the qt code to some
modern version.

As I fixed an exception on closing the library browser I do not only tried to
prevent the situation but to understand how this could happen.
I found that the particular object involved gets deleted while executing its own
destructor. I then tried to find the cause for this behaviour and
failed on understanding the code and what parts are done where.

After some code exploration tours, and some mild changes, I thought the best
would be to re-new the UI.
The original code is nearly 20 years old and realy needs an upgrade. So I went
on with the fork. First thing was to isolate the model store from the UI. This
is already done and loading some examples works.

But after a week of good progress I am afraid that I started a work nobody will
ever use. So it would be interesting to know if anyone is using the original and
would be interested in some new UI that should lead to new features.

So please give me some hint.


Post a reply to this message

From: Dick Balaska
Subject: Re: povmodeler
Date: 27 Oct 2019 15:13:29
Message: <5db5b419$1@news.povray.org>
On 10/27/19 9:17 AM, simbad wrote:

> 
> So please give me some hint.

I saw a comment/request for someone to turn this into a debian package, 
so I started to do that.  The first thing I did though was to rearrange 
the single directory of foo into a Qt layout.  i.e. ./source 
./resources and now I'm adding a qmake povmodeler.pro file.

Then I got a little depressed because that dead-ends my fork from yours 
and eticres'.  But I will finish the debian package because I actually 
have a couple of use cases for povmodeler coming up in my movie.


-- 
dik
Rendered 18,243,532,800 of 40,928,716,800 pixels (40%)


Post a reply to this message

From: jr
Subject: Re: povmodeler
Date: 27 Oct 2019 15:15:01
Message: <web.5db5b36af7e9e652feeb22ff0@news.povray.org>
hi,

"simbad" <Han### [at] gmxde> wrote:
> ...
> But after a week of good progress I am afraid that I started a work nobody will
> ever use. So it would be interesting to know if anyone is using the original and
> would be interested in some new UI that should lead to new features.
>
> So please give me some hint.

I removed the old version, which _claimed_ to be KDE-free, only a few weeks ago.
 nevertheless, it would be good, perhaps, if you could write about your progress
in the newsgroups, I'm sure there'll be some interest.


regards, jr.


Post a reply to this message

From: Bald Eagle
Subject: Re: povmodeler
Date: 27 Oct 2019 16:20:01
Message: <web.5db5c312f7e9e6524eec112d0@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:

> > would be interested in some new UI that should lead to new features.
> >
> > So please give me some hint.

Yes.   I recently tried to install povmodeler, with no success.
It would be great if I had even a basic version that was easy to install on
linux Mint.  I tried to install kde - but that went nowhere fast.

> I removed the old version, which _claimed_ to be KDE-free, only a few weeks ago.
>  nevertheless, it would be good, perhaps, if you could write about your progress
> in the newsgroups, I'm sure there'll be some interest.

There are a lot of projects that make sporadic progress - either to address some
sort of "I wish I had a modeler to do this" issue, or to try to implement a
simple modeler for a handful of objects.
I'm halfway through the circle/tangent thing for prisms myself, and that may
still take some time before It's ready for use/abuse testing.

Please, by all means, get something installable and useable out to the community
- I get the feeling that there are a lot of people who lurk or use POV-Ray but
are not active participants in the forum.


Post a reply to this message

From: simbad
Subject: Re: povmodeler
Date: 27 Oct 2019 17:30:01
Message: <web.5db5d23bf7e9e6529cfad62f0@news.povray.org>
Ok,

to all here posting in this quiet few hours.

As far as I see, there are two different problems here. One is, that the
original source cannot be installed build without problems and run, as expected.

As far as I have seen from the source code of my starting point there is no KDE
dependency in the source anymore. So I would think its in the cmake. I did
changed it for my own work in complete, but ignored the installation thing, as I
am far away from working for my fork.

With my new ui already merged into the master I could only create a branch that
will produce my old starting point, that would be mostly the eticre repo.

And then we need to sort out together what kind of problems exist on building
this on different environments. I have no problems to install some different VMs
for checking it out.
An openSUSE VM already exists, but did not use it for installation tests. But
will do that next.

Second problem is about implementation of new features into the old code. This
is somehow hard, because its a monolithic block of code, where lots of files
must be changed for only adding a single POVray object.

Most of it is very early C++ code with near to no use of STL-Containers and
modern C++ capabilities. I do not blame anyone for this, as I know from my own
experience how less stable C++ has been around 2004, and earlier, when it comes
to portability.

But these times are gone now and I think its time to move on with the code.


Post a reply to this message

From: Dick Balaska
Subject: Re: povmodeler
Date: 27 Oct 2019 19:22:53
Message: <5db5ee8d$1@news.povray.org>
On 10/27/19 1:26 PM, simbad wrote:

> 
> And then we need to sort out together what kind of problems exist on building
> this on different environments. I have no problems to install some different VMs
> for checking it out.
> An openSUSE VM already exists, but did not use it for installation tests. But
> will do that next.

povmodeler is just Qt.  Trolltech has worked out all of the building in 
different environments.

qtpovray is a qmake based program.  The same source set builds and runs 
on Linux, Windows and whatever jr is running.

I'll finish my povmodeler->qmake exercise and see if you want to move on 
with that.


-- 
dik
Rendered 18,243,532,800 of 40,928,716,800 pixels (40%)


Post a reply to this message

From: Dick Balaska
Subject: Re: povmodeler
Date: 27 Oct 2019 19:25:12
Message: <5db5ef18$1@news.povray.org>
On 10/27/19 1:26 PM, simbad wrote:

> Most of it is very early C++ code with near to no use of STL-Containers and
> modern C++ capabilities.
Don't use STL-Containers, use the Qt containers.  So much easier, and 
you don't need the nuclear launch codes just to iterate a list.

-- 
dik
Rendered 18,243,532,800 of 40,928,716,800 pixels (40%)


Post a reply to this message

From: Bald Eagle
Subject: Re: povmodeler
Date: 27 Oct 2019 19:50:05
Message: <web.5db5f4c4f7e9e6524eec112d0@news.povray.org>
"simbad" <Han### [at] gmxde> wrote:

> As far as I have seen from the source code of my starting point there is no KDE
> dependency in the source anymore. So I would think its in the cmake. I did
> changed it for my own work in complete, but ignored the installation thing, as I
> am far away from working for my fork.

Hans-Juergen,

Thanks very much.   I just ran cmake ../ again and got the following output, if
this helps at all:

CMake Warning at CMakeLists.txt:26 (find_package):
  Could not find a package configuration file provided by "KF5Parts" with any
  of the following names:

    KF5PartsConfig.cmake
    kf5parts-config.cmake

  Add the installation prefix of "KF5Parts" to CMAKE_PREFIX_PATH or set
  "KF5Parts_DIR" to a directory containing one of the above files.  If
  "KF5Parts" provides a separate development package or SDK, be sure it has
  been installed.


CMake Error at CMakeLists.txt:27 (find_package):
  By not providing "FindKF5KIO.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "KF5KIO", but
  CMake did not find one.

  Could not find a package configuration file provided by "KF5KIO" with any
  of the following names:

    KF5KIOConfig.cmake
    kf5kio-config.cmake

  Add the installation prefix of "KF5KIO" to CMAKE_PREFIX_PATH or set
  "KF5KIO_DIR" to a directory containing one of the above files.  If "KF5KIO"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!
See also
"/home/oem/Downloads/kpovmodeler-master/build/CMakeFiles/CMakeOutput.log".

(I'm still comparatively new to linux, and all that goes along with it.   But on
the plus side, I've been pretty much M$-free for months now. )

> And then we need to sort out together what kind of problems exist on building
> this on different environments.

Probably a good idea - it would be a very nice thing indeed if we could get a
poll of users and their current OS and POV-Ray versions.

> Second problem is about implementation of new features into the old code. This
> is somehow hard, because its a monolithic block of code, where lots of files
> must be changed for only adding a single POVray object.

Yes, I got the impression that even with POV-Ray itself, that sort of thing is
true.

Very old article:

https://www.researchgate.net/publication/234831963_Scientific_visualizations_with_POV-Ray

(See Table 1, page 6)

> Most of it is very early C++ code with near to no use of STL-Containers and
> modern C++ capabilities. I do not blame anyone for this, as I know from my own
> experience how less stable C++ has been around 2004, and earlier, when it comes
> to portability.
>
> But these times are gone now and I think its time to move on with the code.

Yes.

Of course, at this juncture, I would probably have a meeting of the minds with
the people trying to resurrect Moray, and see what can be shared and made
easier.

I'd also maybe take a look at EPSpline, and definitely Microsoft VISIO - which
is what I wish more people would use as inspiration and guidance.

I wish I had maintained my computer literacy and programming skills, but twists
of fate and graduate school in Chemistry didn't leave a lot of time for that
:(

Thanks for looking into this and trying to get it to work!   :)

Bill


Post a reply to this message

From: jr
Subject: Re: povmodeler
Date: 27 Oct 2019 19:55:05
Message: <web.5db5f5b1f7e9e652feeb22ff0@news.povray.org>
hi,

Dick Balaska <dic### [at] buckosoftcom> wrote:
> On 10/27/19 1:26 PM, simbad wrote:
> > And then we need to sort out together what kind of problems exist on building
> > this on different environments. I have no problems to install some different VMs
> > for checking it out.
> > An openSUSE VM already exists, but did not use it for installation tests. But
> > will do that next.
>
> povmodeler is just Qt.  Trolltech has worked out all of the building in
> different environments.
>
> qtpovray is a qmake based program.  The same source set builds and runs
> on Linux, Windows and whatever jr is running.

I think that if it builds/installs cleanly on Debian + BSD, it'll build and
install on pretty much any Linux.

(there's even a Linux VM on Chromebooks.  ;-))

> ...


regards, jr.


Post a reply to this message

From: Dick Balaska
Subject: Re: povmodeler
Date: 27 Oct 2019 20:53:00
Message: <5db603ac$1@news.povray.org>
On 10/27/19 11:13 AM, Dick Balaska wrote:

> 
> Then I got a little depressed because that dead-ends my fork from yours 
> and eticres'.  But I will finish the debian package because I actually 
> have a couple of use cases for povmodeler coming up in my movie.
> 
> 

Bleh, apparently I was working from the original eticre version.
It still has a several KDEisms in it.
I found yours at https://github.com/tribad/povmodeler
and I'm going to punt my copy and start over from yours.


-- 
dik
Rendered 18,496,512,000 of 40,928,716,800 pixels (45%)


Post a reply to this message

Goto Latest 10 Messages Next 10 Messages >>>

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