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

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

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

"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

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

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

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

"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

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

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

If you try that it will be best if I would give you starting point. As I merged
may way of a new UI into the master you will have only limited luck on building
something that will fit anyones need ;)

Will give a ping here, for all who think it is worth it.

Dick Balaska <dic### [at] buckosoftcom> wrote:
> 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

I created a branch on my fork named 'original'.
https://github.com/tribad/povmodeler/tree/original
That contains a runnable, at least for me, version of my base. There are some
changes already made to the source. But let us see how it work out.

First thing is the building of the povmodeler. So I changed the CMakeLists.txt

Please check. Ping!

Post a reply to this message

"simbad" <Han### [at] gmxde> wrote:
> I created a branch on my fork named 'original'.
> https://github.com/tribad/povmodeler/tree/original
> That contains a runnable, at least for me, version of my base. There are some
> changes already made to the source. But let us see how it work out.
>
> First thing is the building of the povmodeler. So I changed the CMakeLists.txt
>
> Please check. Ping!

I checked it on a debian-10 VM. Building is no problem if all standard packages
that are needed to build anything are available. But its crashing. Found the
point, but will fix it tomorrow.

Post a reply to this message

On https://github.com/tribad/povmodeler/tree/original I have a version ready
that may do it on a debian installation.

I did checkout this branch on my debian-10 VM did a

make install

and afterwards find a povmodeler desktop icon in the gnome3 activities overview.
A click on the Icon starts the povmodeler.

Please check it.

Post a reply to this message

On 10/29/19 12:52 PM, simbad wrote:
> On https://github.com/tribad/povmodeler/tree/original I have a version ready
> that may do it on a debian installation.

> 
> Please check it.
> 
> 

What are you using for an IDE?

-- 
dik
Rendered 21,270,988,800 of 40,928,716,800 pixels (51%)

Post a reply to this message

Dick Balaska <dic### [at] buckosoftcom> wrote:
> On 10/29/19 12:52 PM, simbad wrote:
> > On https://github.com/tribad/povmodeler/tree/original I have a version ready
> > that may do it on a debian installation.
>
> >
> > Please check it.
> >
> >
>
> What are you using for an IDE?
>
> --
> dik
> Rendered 21,270,988,800 of 40,928,716,800 pixels (51%)

Qtcreator

Post a reply to this message

I did create a debian-10 package.
Could be downloaded here https://simulated-universe.de/povmodeler-0.1-Linux.deb

This is my first try ever to create a debian package. It will evolve over time.

RPM is coming next.

Post a reply to this message

"simbad" <Han### [at] gmxde> wrote:
> I did create a debian-10 package.
> Could be downloaded here https://simulated-universe.de/povmodeler-0.1-Linux.deb
>
> This is my first try ever to create a debian package. It will evolve over time.

I opened it in Mint's Package Installer, and got:
"Error: dependency is not satisfiable: libglx0"

I tried sudo apt-get install libglx0 (and libglx and libgl) but it couldn't find
any such package to install.   So I'm not sure what I need to install or where
to install it from...

then I tried this:

sudo dpkg -i povmodeler-0.1-Linux.deb
[sudo] password for oem:
Selecting previously unselected package povmodeler.
(Reading database ... 288574 files and directories currently installed.)
Preparing to unpack povmodeler-0.1-Linux.deb ...
Unpacking povmodeler (0.1) ...
dpkg: dependency problems prevent configuration of povmodeler:
 povmodeler depends on libglx0; however:
  Package libglx0 is not installed.
 povmodeler depends on libopengl0; however:
  Package libopengl0 is not installed.
 povmodeler depends on libqt5core5a (>= 5.11.0~rc1); however:
  Version of libqt5core5a:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
 povmodeler depends on libqt5gui5 (>= 5.7.0); however:
  Version of libqt5gui5:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
 povmodeler depends on libqt5widgets5 (>= 5.11.0~rc1); however:
  Version of libqt5widgets5:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.

I'll work on it for a little while, but I'm trying this at the end of the day...
:O

Post a reply to this message

On 11/2/19 9:53 PM, Bald Eagle wrote:
> 
> "simbad" <Han### [at] gmxde> wrote:
>> I did create a debian-10 package.
>> Could be downloaded here https://simulated-universe.de/povmodeler-0.1-Linux.deb
>>
>> This is my first try ever to create a debian package. It will evolve over time.
> 
> I opened it in Mint's Package Installer, and got:
> "Error: dependency is not satisfiable: libglx0"
> 
> I tried sudo apt-get install libglx0 (and libglx and libgl) but it couldn't find
> any such package to install.   So I'm not sure what I need to install or where
> to install it from...
> 
> then I tried this:
> 
> sudo dpkg -i povmodeler-0.1-Linux.deb
> [sudo] password for oem:
> Selecting previously unselected package povmodeler.
> (Reading database ... 288574 files and directories currently installed.)
> Preparing to unpack povmodeler-0.1-Linux.deb ...
> Unpacking povmodeler (0.1) ...
> dpkg: dependency problems prevent configuration of povmodeler:
>   povmodeler depends on libglx0; however:
>    Package libglx0 is not installed.
>   povmodeler depends on libopengl0; however:
>    Package libopengl0 is not installed.
>   povmodeler depends on libqt5core5a (>= 5.11.0~rc1); however:
>    Version of libqt5core5a:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
>   povmodeler depends on libqt5gui5 (>= 5.7.0); however:
>    Version of libqt5gui5:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
>   povmodeler depends on libqt5widgets5 (>= 5.11.0~rc1); however:
>    Version of libqt5widgets5:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
> 
> I'll work on it for a little while, but I'm trying this at the end of the day...
> :O
> 
> 

I have libglx0 and libopengl0 [1], but I'm not sure where they came 
from. AFAICT they are in the normal mint/ubuntu repos. The home page 
listed below contains just the source, not a .deb package.  The only 
custom repos in /etc/apt/sources.list.d point to my own stuff (like 
qtpovray).

The Qt >= 5.11 is problematic.  That is way too new to be in any debian 
distros. Baldy is Mint 19.1 with QT 5.5.  I am Mint 19.2 (newest 
version, 2 months old) and that is QT 5.9.

Simbad, my reading of
https://www.debian.org/doc/manuals/debmake-doc/ch08.en.html#cmake-single
says you ran some cmake command which generated the debian folder, then 
you ran something else to build the .deb.  You should edit the 
debian/control file and remove the versions from the dependencies and 
try to let the packager figure it out.
You run the risk of using a qt5 feature newer than 5.5, but it's a low 
risk.  I had a couple of issues solved like this:
https://github.com/dickbalaska/qtpovray/blob/qtpovray/qt/gui/editor/codeeditor.cpp#L114

qtpovray's control looks like this:
https://github.com/dickbalaska/qtpovray/blob/qtpovray/debian/control

I find it mush easier to keep the debian folder around as a native part 
of the source tree rather than continually recreating and editing them.

Another example is, your icons aren't quite right. These need to move:
hi16-app-kpovmodeler.png /usr/share/icons/hicolor/16x16/povmodeler.png
hi22-app-kpovmodeler.png /usr/share/icons/hicolor/22x22/povmodeler.png
hi32-app-kpovmodeler.png /usr/share/icons/hicolor/32x32/povmodeler.png
hi48-app-kpovmodeler.png /usr/share/icons/hicolor/48x48/povmodeler.png

and then in your povmodeler.desktop the icon reference is just 
povmodeler.  You can either hack debian/rules to move and rename them, 
like this:
https://github.com/dickbalaska/slyther-debian/blob/master/rules
or just reorg them in the source tree, and reference them normally.

---

[1] $ apt-cache show libglx0
Package: libglx0
Architecture: amd64
Version: 1.0.0-2ubuntu2.3
Multi-Arch: same
Priority: extra
Section: libs
Source: libglvnd
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubu### [at] listsubuntucom>
Original-Maintainer: Debian X Strike Force <deb### [at] listsdebianorg>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 90
Depends: libc6 (>= 2.14), libglvnd0 (= 1.0.0-2ubuntu2.3), libx11-6 (>= 
2:1.4.99.1), libglx-mesa0
Breaks: libgl1-mesa-glx (<< 18.0.5-0ubuntu0~18.04), libglvnd0 (<< 
0.2.999+git20170201-1)
Replaces: libgl1-mesa-glx (<< 18.0.5-0ubuntu0~18.04), libglvnd0 (<< 
0.2.999+git20170201-1)
Filename: pool/main/libg/libglvnd/libglx0_1.0.0-2ubuntu2.3_amd64.deb
Size: 28088
MD5sum: 312d48ae120aeba38800cf0eba14d139
SHA1: 65dfb7b0292b18c98710105fef352278df87c041
SHA256: 11d56b939271cac02b251dcc53630aec86aa66fc9433f3b63e3c6806580b20e8
Homepage: https://github.com/NVIDIA/libglvnd
Description-en: Vendor neutral GL dispatch library -- GLX support
  This is an implementation of the vendor-neutral dispatch layer for
  arbitrating OpenGL API calls between multiple vendors on a per-screen 
basis.
  .
  This package contains support for GLX.

-- 
dik
Rendered 22,077,619,200 of 40,928,716,800 pixels (53%)

Post a reply to this message

On 11/3/19 1:29 AM, Dick Balaska wrote:

> 
> Another example is, your icons aren't quite right. These need to move:
> hi16-app-kpovmodeler.png /usr/share/icons/hicolor/16x16/povmodeler.png
> hi22-app-kpovmodeler.png /usr/share/icons/hicolor/22x22/povmodeler.png
> hi32-app-kpovmodeler.png /usr/share/icons/hicolor/32x32/povmodeler.png
> hi48-app-kpovmodeler.png /usr/share/icons/hicolor/48x48/povmodeler.png

Sorry, these are wrong.  The correct directories are

/usr/share/icons/hicolor/16x16/apps/povmodeler.png
/usr/share/icons/hicolor/22x22/apps/povmodeler.png

etc.
-- 
dik
Rendered 22,077,619,200 of 40,928,716,800 pixels (53%)

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "simbad" <Han### [at] gmxde> wrote:
> > I did create a debian-10 package.
> > Could be downloaded here https://simulated-universe.de/povmodeler-0.1-Linux.deb
> >
> > This is my first try ever to create a debian package. It will evolve over time.
>
> I opened it in Mint's Package Installer, and got:
> "Error: dependency is not satisfiable: libglx0"
>
> I tried sudo apt-get install libglx0 (and libglx and libgl) but it couldn't find
> any such package to install.   So I'm not sure what I need to install or where
> to install it from...
>
> then I tried this:
>
> sudo dpkg -i povmodeler-0.1-Linux.deb
> [sudo] password for oem:
> Selecting previously unselected package povmodeler.
> (Reading database ... 288574 files and directories currently installed.)
> Preparing to unpack povmodeler-0.1-Linux.deb ...
> Unpacking povmodeler (0.1) ...
> dpkg: dependency problems prevent configuration of povmodeler:
>  povmodeler depends on libglx0; however:
>   Package libglx0 is not installed.
>  povmodeler depends on libopengl0; however:
>   Package libopengl0 is not installed.
>  povmodeler depends on libqt5core5a (>= 5.11.0~rc1); however:
>   Version of libqt5core5a:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
>  povmodeler depends on libqt5gui5 (>= 5.7.0); however:
>   Version of libqt5gui5:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
>  povmodeler depends on libqt5widgets5 (>= 5.11.0~rc1); however:
>   Version of libqt5widgets5:amd64 on system is 5.5.1+dfsg-16ubuntu7.6.
>
> I'll work on it for a little while, but I'm trying this at the end of the day...
> :O

I already setup some more VMs. I create these packages soon for your OS. So
please tell me what OS you use.

Post a reply to this message

Dick Balaska <dic### [at] buckosoftcom> wrote:

> I have libglx0 and libopengl0 [1], but I'm not sure where they came
> from. AFAICT they are in the normal mint/ubuntu repos.

I haven't done a lot with the PPA / repositories  --- I've just sort of cut and
pasted command line stuff from some betty crocker web pages as I've needed them,
so I don't know which ones I'm plugged into and which ones are "the normal
ones".

> The Qt >= 5.11 is problematic.  That is way too new to be in any debian
> distros. Baldy is Mint 19.1 with QT 5.5.  I am Mint 19.2 (newest
> version, 2 months old) and that is QT 5.9.

I'm presuming that I need to do more than just a simple "sudo apt-get upgrade",
since I've done that a few times in recent memory, and it looks like I'm still
lagging behind you, Speedy.

Mint 19.3 is scheduled for December.  Maybe I'll figure out how to install that
and see if it fixes some things...
https://www.omgubuntu.co.uk/2019/10/linux-mint-19-3-tricia-release-features


With regard to QTPOV-Ray:  I find that - too often - I'm doing something that
pastes a bit of copied text into my scene in what looks like random places.
Maybe I'm clicking a mouse button or using a keystroke when I'm actually in the
editor but I think I'm in the browser window or the system's text editor...
But I was wondering if any such thing ever happened to you.
I'm forever scratching my head, wondering "How did THAT get in there...?"
That mouse-click-paste is a dangerously easy thing to inadvertently do.
Can I disable?


> [1] $ apt-cache show libglx0

My terminal typeface has that nice "dotted zero", but my GUI typeface seems to
use one that makes it look too much like O.  :|

Ever since I tried using Redshift to relieve some eye strain and it took me
forever to shut it off (I think I resorted to ps, grep, and "kill -9 [pid]"  :D
) I haven't fiddled with the greebles and frobs much...

Post a reply to this message

hi,

(forgot)

"Bald Eagle" <cre### [at] netscapenet> wrote:
> ...
> Ever since I tried using Redshift to relieve some eye strain and it took me
> forever to shut it off (I think I resorted to ps, grep, and "kill -9 [pid]"  :D
> ) I haven't fiddled with the greebles and frobs much...

there's also 'killall' which has the advantage of taking names, eg killall
redshift.

personally, I prefer the 'kill -s SIG pid' notation.  safer in use, imo.


regards, jr.

Post a reply to this message

On 11/3/19 9:27 AM, Bald Eagle wrote:
> 
> Dick Balaska <dic### [at] buckosoftcom> wrote:
> 
>> I have libglx0 and libopengl0 [1], but I'm not sure where they came
>> from. AFAICT they are in the normal mint/ubuntu repos.
> 
> I haven't done a lot with the PPA / repositories  --- I've just sort of cut and
> pasted command line stuff from some betty crocker web pages as I've needed them,
> so I don't know which ones I'm plugged into and which ones are "the normal
> ones".

/etc/apt/sources.list.d/official-package-repositories.list
contains the normal ones.  Any you add are in their own file, like 
qtpovray-qtpovray-bionic.list

> 
>> The Qt >= 5.11 is problematic.  That is way too new to be in any debian
>> distros. Baldy is Mint 19.1 with QT 5.5.  I am Mint 19.2 (newest
>> version, 2 months old) and that is QT 5.9.
> 
> I'm presuming that I need to do more than just a simple "sudo apt-get upgrade",
> since I've done that a few times in recent memory, and it looks like I'm still
> lagging behind you, Speedy.

*You* shouldn't have to do anything.  It's up to the dev to try to 
broaden his potential user base (which is pretty small to begin with) 
and not use bleeding edge versions.  If he is cutting debian versions, 
he needs to use supported debian versions as much as possible.

(Unless absolutely necessary, which in this case is a port from 2005's 
Qt 3, so I doubt there is anything Qt 5.11 specific)

> 
> With regard to QTPOV-Ray:  I find that - too often - I'm doing something that
> pastes a bit of copied text into my scene in what looks like random places.
> Maybe I'm clicking a mouse button or using a keystroke when I'm actually in the
> editor but I think I'm in the browser window or the system's text editor...
> But I was wondering if any such thing ever happened to you.
> I'm forever scratching my head, wondering "How did THAT get in there...?"
> That mouse-click-paste is a dangerously easy thing to inadvertently do.
> Can I disable?

That middle-mouse-button-paste thing is indeed a pita, and really 
useless.  It is left over from the '80s and I can't believe it's still a 
thing.
I do it rarely, accidentally, of course.  I looked at disabling it, it's 
not easy and doesn't really work for me.  Solution: Don't do that.


-- 
dik
Rendered 22,077,619,200 of 40,928,716,800 pixels (53%)

Post a reply to this message

Dick Balaska <dic### [at] buckosoftcom> wrote:

> *You* shouldn't have to do anything.  It's up to the dev to try to
> broaden his potential user base (which is pretty small to begin with)
> and not use bleeding edge versions.  If he is cutting debian versions,
> he needs to use supported debian versions as much as possible.
>
> (Unless absolutely necessary, which in this case is a port from 2005's
> Qt 3, so I doubt there is anything Qt 5.11 specific)
>

> --
> dik
> Rendered 22,077,619,200 of 40,928,716,800 pixels (53%)

Full ack to this. It is my responsibility to make the packages work. But as its
the first time doing that, I need some more days to upgrade my dev environment.
I think it would be a good idea to have some different systems available to not
only check the installation procedure but the build process as well.

To setup a specific distribution into a VM only takes an hour or so. It is ok to
support my efforts, but I need the VMs anyway. So dont risk your own
installation.

That I used a debian-10 busty as my first debian environment, that has the
qt5.11 libs, was sheer coincidence. But, hey. No problem doing it again with a
mint 19.2 and mint 19.1 next. The VMs already up.

Post a reply to this message

I now have a build environment to produce the various packages.

They get build on the original distros. So it should be match far better than in
the first version


https://www.simulated-universe.de/povmodeler-0.1-debian-10.deb

https://www.simulated-universe.de/povmodeler-0.1-linuxmint-19.1.deb

https://www.simulated-universe.de/povmodeler-0.1-linuxmint-19.2.deb

https://www.simulated-universe.de/povmodeler-0.1-opensuse-leap-15.1.rpm


As I mostly work on weekend on this project its going on slowly.
I did not change anything on the installation places and the like. Maybe doing
this tomorrow.

Post a reply to this message

Did some changes to the installation places and give the packages a better
version info.

https://www.simulated-universe.de/povmodeler-1.1.4-debian-10.deb
https://www.simulated-universe.de/povmodeler-1.1.4-linuxmint-19.1.deb
https://www.simulated-universe.de/povmodeler-1.1.4-linuxmint-19.2.deb
https://www.simulated-universe.de/povmodeler-1.1.4-opensuse-leap-15.1.rpm
https://www.simulated-universe.de/povmodeler-1.1.4-fedora-30.rpm

Check it!

Post a reply to this message

"simbad" <Han### [at] gmxde> wrote:
> Did some changes to the installation places and give the packages a better
> version info.

> Check it!

Nice!   I will.
inxi -Fx gives me Linux Mint 18.3 Sylvia - I'll let you know how the debian
packages work out with these.

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "simbad" <Han### [at] gmxde> wrote:
> > Did some changes to the installation places and give the packages a better
> > version info.
>
> > Check it!
>
> Nice!   I will.
> inxi -Fx gives me Linux Mint 18.3 Sylvia - I'll let you know how the debian
> packages work out with these.

Installed a Linux Mint 18.3 and checked it. I would not expect it to run. I can
not even build it on this distro. Should not be a big problem. But must check
how to not break my build environment.

Post a reply to this message

"simbad" <Han### [at] gmxde> wrote:
> "Bald Eagle" <cre### [at] netscapenet> wrote:
> > "simbad" <Han### [at] gmxde> wrote:
> > > Did some changes to the installation places and give the packages a better
> > > version info.
> >
> > > Check it!
> >
> > Nice!   I will.
> > inxi -Fx gives me Linux Mint 18.3 Sylvia - I'll let you know how the debian
> > packages work out with these.
>
> Installed a Linux Mint 18.3 and checked it. I would not expect it to run. I can
> not even build it on this distro. Should not be a big problem. But must check
> how to not break my build environment.

Completed. Even it feels like a hack. But it produced something. The packages
have been updated and a package for the Mint-18.3 is here

https://www.simulated-universe.de/povmodeler-1.1.4-linuxmint-18.3.deb

But as I checked it only in the debian-10 VM and my own fedora-30 it may fail to
work.

Post a reply to this message

"simbad" <Han### [at] gmxde> wrote:

> > Installed a Linux Mint 18.3 and checked it. I would not expect it to run. I can
> > not even build it on this distro. Should not be a big problem. But must check
> > how to not break my build environment.
>
> Completed. Even it feels like a hack. But it produced something. The packages
> have been updated and a package for the Mint-18.3 is here

Well it works, so your hacks are good   :)

I have to set up the environment variables so that it can find a version of
POV-Ray to use, so a pointer to any documentation this thing used to have would
be sweet!
Also, if there are some .kpm files to use as examples, anyone new to this would
likely find those useful.

Super work!    Glad to finally have a running example of this to play with.
Thanks so much for what must be a LOT of unseen work in the background.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "simbad" <Han### [at] gmxde> wrote:
> > "Bald Eagle" <cre### [at] netscapenet> wrote:
> > > "simbad" <Han### [at] gmxde> wrote:
> > > > Did some changes to the installation places and give the packages a better
> > > > version info.
> > >
> > > > Check it!
> > >
> > > Nice!   I will.
> > > inxi -Fx gives me Linux Mint 18.3 Sylvia - I'll let you know how the debian
> > > packages work out with these.
> >
> > Installed a Linux Mint 18.3 and checked it. I would not expect it to run. I can
> > not even build it on this distro. Should not be a big problem. But must check
> > how to not break my build environment.
>
> Completed. Even it feels like a hack. But it produced something. The packages
> have been updated and a package for the Mint-18.3 is here
>
> https://www.simulated-universe.de/povmodeler-1.1.4-linuxmint-18.3.deb
>
> But as I checked it only in the debian-10 VM and my own fedora-30 it may fail to
> work.

sounds promising.  will you, in due course, release a source tarball?  (the
preferred format for Slackware)


regards, jr.

Post a reply to this message

On 11/17/19 4:34 PM, jr wrote:
> hi,

> 
> sounds promising.  will you, in due course, release a source tarball?  (the
> preferred format for Slackware)
> 

You could clone the source

https://github.com/tribad/povmodeler

-- 
dik
Rendered 24,551,424,000 of 40,928,716,800 pixels (59%)

Post a reply to this message

Dick Balaska <dic### [at] buckosoftcom> wrote:
> On 11/17/19 4:34 PM, jr wrote:
> > hi,
>
> >
> > sounds promising.  will you, in due course, release a source tarball?  (the
> > preferred format for Slackware)
> >
>
> You could clone the source
>
> https://github.com/tribad/povmodeler
>
> --
> dik
> Rendered 24,551,424,000 of 40,928,716,800 pixels (59%)

Yeah....
The packages are produced from the branch named "original".

All other branches are somewhat out of sync. So unusable, already modified a
lot.

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "simbad" <Han### [at] gmxde> wrote:
>
> > > Installed a Linux Mint 18.3 and checked it. I would not expect it to run. I can
> > > not even build it on this distro. Should not be a big problem. But must check
> > > how to not break my build environment.
> >
> > Completed. Even it feels like a hack. But it produced something. The packages
> > have been updated and a package for the Mint-18.3 is here
>
> Well it works, so your hacks are good   :)
>
> I have to set up the environment variables so that it can find a version of
> POV-Ray to use, so a pointer to any documentation this thing used to have would
> be sweet!
> Also, if there are some .kpm files to use as examples, anyone new to this would
> likely find those useful.
>
> Super work!    Glad to finally have a running example of this to play with.
> Thanks so much for what must be a LOT of unseen work in the background.

Examples and such things can be found in /usr/share/povmodeler

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> Dick Balaska <dic### [at] buckosoftcom> wrote:
> > On 11/17/19 4:34 PM, jr wrote:
> > > sounds promising.  will you, in due course, release a source tarball?  (the
> > > preferred format for Slackware)
> >
> > You could clone the source
> >
> > https://github.com/tribad/povmodeler
> >
> > --
> > dik
> > Rendered 24,551,424,000 of 40,928,716,800 pixels (59%)
>
> Yeah....
> The packages are produced from the branch named "original".

thanks, both of you.  it'll have to wait a while though, busy with other stuff.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > Dick Balaska <dic### [at] buckosoftcom> wrote:
> > > On 11/17/19 4:34 PM, jr wrote:
> > > > sounds promising.  will you, in due course, release a source tarball?  (the
> > > > preferred format for Slackware)
> > >
> > > You could clone the source
> > >
> > > https://github.com/tribad/povmodeler
> > >
> > > --
> > > dik
> > > Rendered 24,551,424,000 of 40,928,716,800 pixels (59%)
> >
> > Yeah....
> > The packages are produced from the branch named "original".
>
> thanks, both of you.  it'll have to wait a while though, busy with other stuff.
>
>
> regards, jr.

What slackware is it? 14.x? Think this was the last release. So maybe I give it
a try. Used slackware a long time. But need to check how to create a package
there. Never did before.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "simbad" <Han### [at] gmxde> wrote:
> > > Dick Balaska <dic### [at] buckosoftcom> wrote:
> > > > On 11/17/19 4:34 PM, jr wrote:
> > > > > sounds promising.  will you, in due course, release a source tarball?  (the
> > > > > preferred format for Slackware)
> > > >
> > > > You could clone the source
> > > >
> > > > https://github.com/tribad/povmodeler
> > > >
> > > > --
> > > > dik
> > > > Rendered 24,551,424,000 of 40,928,716,800 pixels (59%)
> > >
> > > Yeah....
> > > The packages are produced from the branch named "original".
> >
> > thanks, both of you.  it'll have to wait a while though, busy with other stuff.
> >
> What slackware is it? 14.x? Think this was the last release. So maybe I give it
> a try. Used slackware a long time. But need to check how to create a package
> there. Never did before.

yes, both 14.1 and 14.2.  for the command see "man 8 makepkg".  no rush.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > "simbad" <Han### [at] gmxde> wrote:

.......

> > > thanks, both of you.  it'll have to wait a while though, busy with other stuff.
> > >
> > What slackware is it? 14.x? Think this was the last release. So maybe I give it
> > a try. Used slackware a long time. But need to check how to create a package
> > there. Never did before.
>
> yes, both 14.1 and 14.2.  for the command see "man 8 makepkg".  no rush.
>
>
> regards, jr.

Do you have an unchanged 14.1 14.2 installation? As this would make things more
and more complicated.

14.2 uses qt-4.8.7
14.1 uses qt-4.8.5 and additional has cmake version 2.8.12

So even I want many systems supported it takes more and more effort to get it
compiled.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "simbad" <Han### [at] gmxde> wrote:
> > > "jr" <cre### [at] gmailcom> wrote:
> > > > "simbad" <Han### [at] gmxde> wrote:
> .......
> Do you have an unchanged 14.1 14.2 installation? As this would make things more
> and more complicated.

:-)

> 14.2 uses qt-4.8.7
> 14.1 uses qt-4.8.5 and additional has cmake version 2.8.12

I have (on the 14.1 box) both qt-4.8.7 and qt5-5.7.1.

> So even I want many systems supported it takes more and more effort to get it
> compiled.


regards, jr.

Post a reply to this message

I worked on the slackware-14.x support and got an executable. But its not good
enough to let it out into the wild.

But it builds with Qt4 and even the OpenGL things seems to work. But docking of
the widgets and some file-loading things are not ready.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> I worked on the slackware-14.x support and got an executable. But its not good
> enough to let it out into the wild.

:-)

> But it builds with Qt4 and even the OpenGL things seems to work. But docking of
> the widgets and some file-loading things are not ready.

thanks.  keep "us" in the loop, please.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > I worked on the slackware-14.x support and got an executable. But its not good
> > enough to let it out into the wild.
>
> :-)
>
> > But it builds with Qt4 and even the OpenGL things seems to work. But docking of
> > the widgets and some file-loading things are not ready.
>
> thanks.  keep "us" in the loop, please.
>
>
> regards, jr.

Ok.
I do have a version that seems to run on slackware 14.1 and 14.2
As I am not very familiar with the functionalities of povmodeler and the qt
library tweaks it may still have bugs.

But it looks promising as it has been build against the distros qt libs
versions. So Qt4.x

Next would be to pack that and make it available. But this comes the next days.
For now I check whether the other packages still build and work.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > thanks.  keep "us" in the loop, please.
>
> Ok.
> I do have a version that seems to run on slackware 14.1 and 14.2
> As I am not very familiar with the functionalities of povmodeler and the qt
> library tweaks it may still have bugs.
>
> But it looks promising as it has been build against the distros qt libs
> versions. So Qt4.x
>
> Next would be to pack that and make it available. But this comes the next days.
> For now I check whether the other packages still build and work.

have a look at: <https://slackbuilds.org/>
that is sort of the standard.

if you want to discuss stuff, feel free to email direct.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > thanks.  keep "us" in the loop, please.
> >
> > Ok.
> > I do have a version that seems to run on slackware 14.1 and 14.2
> > As I am not very familiar with the functionalities of povmodeler and the qt
> > library tweaks it may still have bugs.
> >
> > But it looks promising as it has been build against the distros qt libs
> > versions. So Qt4.x
> >
> > Next would be to pack that and make it available. But this comes the next days.
> > For now I check whether the other packages still build and work.
>
> have a look at: <https://slackbuilds.org/>
> that is sort of the standard.
>
> if you want to discuss stuff, feel free to email direct.
>
>
> regards, jr.
Hi ho,
there are two packages available.

 * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-1hjl.tgz
 * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-2hjl.tgz

for slackware-14.1 and slackware-14.2

I experienced segfaults on first start. I could not find the cause for now.
While it has vanished with the next start it has been hard to identify.

While checking a coredump I found an iterator through the action list failed.
But the debugging on slackware is hard, as the X11 in a vm runs without any
accelleration support. Everything is very slow.

So look out for those crashes. Maybe I got some more ideas about the situation
that will cause this.

I did not created any slackbuild-script but added the slack-desc file to the
repo. As it should be easy to be build on a slackware distro now I think I will
not deliver the slack-build script.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> Hi ho,
> there are two packages available.
>
>  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-1hjl.tgz
>  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-2hjl.tgz
>
> for slackware-14.1 and slackware-14.2
>
> I experienced segfaults on first start. I could not find the cause for now.
> While it has vanished with the next start it has been hard to identify.
>
> While checking a coredump I found an iterator through the action list failed.
> But the debugging on slackware is hard, as the X11 in a vm runs without any
> accelleration support. Everything is very slow.
>
> So look out for those crashes. Maybe I got some more ideas about the situation
> that will cause this.
>
> I did not created any slackbuild-script but added the slack-desc file to the
> repo. As it should be easy to be build on a slackware distro now I think I will
> not deliver the slack-build script.

ah, thanks.  no idea whether it will be "easy to build" since all you provide is
a binary (system) install.  (I was minded to try the software, but would want to
build and install it to "fit in")  cheers, anyway.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > Hi ho,
> > there are two packages available.
> >
> >  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-1hjl.tgz
> >  * https://www.simulated-universe.de/povmodeler-1.1.4-x86_64-2hjl.tgz
> >
> > for slackware-14.1 and slackware-14.2
> >
> > I experienced segfaults on first start. I could not find the cause for now.
> > While it has vanished with the next start it has been hard to identify.
> >
> > While checking a coredump I found an iterator through the action list failed.
> > But the debugging on slackware is hard, as the X11 in a vm runs without any
> > accelleration support. Everything is very slow.
> >
> > So look out for those crashes. Maybe I got some more ideas about the situation
> > that will cause this.
> >
> > I did not created any slackbuild-script but added the slack-desc file to the
> > repo. As it should be easy to be build on a slackware distro now I think I will
> > not deliver the slack-build script.
>
> ah, thanks.  no idea whether it will be "easy to build" since all you provide is
> a binary (system) install.  (I was minded to try the software, but would want to
> build and install it to "fit in")  cheers, anyway.
>
>
> regards, jr.

git clone https://github.com/tribad/povmodeler.git
cd povmodeler
git checkout slackware14.x
cmake .
make
make install

A build script will not do anything different. So if you have anything different
than the standard slackware 14 software installed, even the slack-build may
fail.
So doing it the way I described above should be the way if you want more control
on the build process.

The packages I produced are created on fresh installed vms. So they should work
out if the box.

Accessing the repo has the advantage that you will stay up to date to any
upcoming changes. That would not possible with a source package as it only
contains "released" source code.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "simbad" <Han### [at] gmxde> wrote:
> > > Hi ho,
> > > there are two packages available.
> > > ...
>
> git clone https://github.com/tribad/povmodeler.git
> cd povmodeler
> git checkout slackware14.x
> cmake .
> make
> make install

> ...
> Accessing the repo has the advantage that you will stay up to date to any
> upcoming changes. That would not possible with a source package as it only
> contains "released" source code.

sure.  I simply assumed that "available packages" means released, and are based
on "released" code bases  (must be my age ;-)).  thanks though.


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "simbad" <Han### [at] gmxde> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > "simbad" <Han### [at] gmxde> wrote:
> > > > Hi ho,
> > > > there are two packages available.
> > > > ...
> >
> > git clone https://github.com/tribad/povmodeler.git
> > cd povmodeler
> > git checkout slackware14.x
> > cmake .
> > make
> > make install
>
> > ...
> > Accessing the repo has the advantage that you will stay up to date to any
> > upcoming changes. That would not possible with a source package as it only
> > contains "released" source code.
>
> sure.  I simply assumed that "available packages" means released, and are based
> on "released" code bases  (must be my age ;-)).  thanks though.
>
>
> regards, jr.

I dont think I will really "release" any version with the old code as it is hard
to maintain and is in many ways complicated.
But on the other hand I want to keep on to support the old users as good as
possible. I already started a rewrite of the GUI but this will take some time.
So I split my time between support for the old code and to rewrite the GUI.

But the build environment and packaging will be needed in both development
pathes.

For handling of bugs I think it would be best to use the github issue tracker.
This would help to establish something near to release managment.

Post a reply to this message

hi,

"simbad" <Han### [at] gmxde> wrote:
> > ...
> I dont think I will really "release" any version with the old code as it is hard
> to maintain and is in many ways complicated.
> But on the other hand I want to keep on to support the old users as good as
> possible. I already started a rewrite of the GUI but this will take some time.

something to look forward to.  :-)

> So I split my time between support for the old code and to rewrite the GUI.
>
> But the build environment and packaging will be needed in both development
> pathes.
>
> For handling of bugs I think it would be best to use the github issue tracker.

ok.

> This would help to establish something near to release managment.

yes, be(com)ing the package maintainer/developer for a software with an existing
user base is a pretty big hat to wear, I think.  wishing you good fortune.


regards, jr.

Post a reply to this message