Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Paul McIntosh]

thanks for the reply - I will give it a go with the geenral list and use osgQT 
in the subject line to make it easy to see.

Cheers,
Paul

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=69409#69409





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[michael kapelko]

I would say it's good to have OSG related info in one place.

2016-11-15 19:25 GMT+07:00 Robert Osfield :

> On 15 November 2016 at 10:37, Paul McIntosh
>  wrote:
> > Should osgQT have it's own section in the forums?
>
> This is a decision for the community/forum moderators.
>
> I am not a forum user or moderator so don't have any direct input or
> exposure to how it is used.  I can see value in have a osgQt section
> on the forum, but really can't say/do much beyond this.
>
> Robert.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

On 15 November 2016 at 10:37, Paul McIntosh
 wrote:
> Should osgQT have it's own section in the forums?

This is a decision for the community/forum moderators.

I am not a forum user or moderator so don't have any direct input or
exposure to how it is used.  I can see value in have a osgQt section
on the forum, but really can't say/do much beyond this.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Paul McIntosh]

Hi Robert,

Should osgQT have it's own section in the forums?

I keep coming back to this thread for updates while I am trying to get it to 
work myself on Windows 10. I am eager to contribute but it is bit hard not 
having an area to post and answer osgQT related issues.

Cheers,
Paul

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=69367#69367





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Stev Kookmal]

Hi Mathieu, 

Here is a summary of what I did to get it to compile in MSVC 2015. 

at line 130 where is says 
SET(OPENSCENEGRAPH_SOVERSION 145)

add the following lines that set the version numbers
SET(OPENSCENEGRAPH_MAJOR_VERSION 3)
SET(OPENSCENEGRAPH_MINOR_VERSION 5)
SET(OPENSCENEGRAPH_PATCH_VERSION 6)

Otherwise MSVC will throw an error: RC2127 version WORDs separated by commas 
expected   

delete the following lines as they are not needed
# 3rd Party Dependency Stuff
IF(WIN32)
INCLUDE(Find3rdPartyDependencies)
ENDIF()

At this point MSVC threw an error that it could not find a baseclass for 
fstream is OSGDB, the problem is that fstream is also an include in OSGDB 
include folder... in essence it was not "finding" the std:: include files in 
the MSVC directory.  I am not sure why, something to look into.  I just 
manually copied the absolute directory path to point the compiler to the exact 
file in my MSVC include folder.

IE #include 

It did this a few more times where there were std:: functions. I just added the 
path by hand to the header and it finally compiled.  It was interesting since I 
do see the path for the MSVC includes sitting there in the build system paths.  
Not sure why the compiler is not finding them.

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=69047#69047





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

I'll look into that thanks for the update
Le lun. 17 oct. 2016 à 13:04, Stev Kookmal  a écrit :

> Hey all,
>
> When building with MSVC2015 and WIN32.  CMAKE throws am error at this line
>
> INCLUDE(Find3rdPartyDependencies)
>
> This probably shouldnt be there anymore and is artifact from the original
> OSG .cmake.  Deleting it makes things run fine again and CMAKE configures
> and generates without an error.
>
> But, when I try to build my solution in MSVC, it will not find my
> headers... gives me the 'cannot open include files error'.
>
> Does anyone have a fix for this?
>
> Cheers,
> Bora
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=69031#69031
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Stev Kookmal]

Hey all,

When building with MSVC2015 and WIN32.  CMAKE throws am error at this line

INCLUDE(Find3rdPartyDependencies)

This probably shouldnt be there anymore and is artifact from the original OSG 
.cmake.  Deleting it makes things run fine again and CMAKE configures and 
generates without an error. 

But, when I try to build my solution in MSVC, it will not find my headers... 
gives me the 'cannot open include files error'. 

Does anyone have a fix for this?  

Cheers,
Bora

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=69031#69031





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Curtis Rubel]

Hi Mathieu,

One other thing that is also not any sort of priority or
any sort of bug report for you to concern yourself with, but
maybe you know something about it with your work on this
project.

The attached PIC to this reply is what I get when starting
the osgviewerQt example.  You will notice the left larger  window
only contains one model instead of the 4 models that it should
have.  Just was running the example after building it and
it reminded me of seeing this again.

The 4 models show up properly as soon as I touch the window
and resize it.  Minimizing it or covering it up and then uncovering
does not fix it, it needs a resize event to finally show the correct
output, doesn't matter if its sized larger or smaller.

This linux system has QT 5.4.2 installed on it right  now, I want to
say this behavior started with the first version of Qt5 we started
to use after our linux distro finally updated from 4.8.x.

Anyhow, just curious if you have seen this at all with your Qt work
and if this is actually a Qt bug that we have to live with until they fix 
it or its something in the osgQt implementation.

We get the same as I recall when we run this on our development
Mac as well, not sure about windows we don't have the examples built
on that platform right now for me to test it at the moment.

... 

Thank you!

Cheers,
Curtis

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68985#68985



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Curtis Rubel]

Hi Mathieu,

  I did a pull on osg and osgQt just to make sure I had the
latest of both.

  cmake on osgQt completed without error now with both
the default settings and with the examples selected to build.

Just an FYI, when I selected the documentation build in the
cmake-gui...  I got a cmake error...anyhow that is just
so you know about it, its not anything that we need, just
figured I would pass it along to you for your TODO list...

CMake Error: File 
/usr/local/3rdparty/osgQt-git/doc/Doxyfiles/openthreads.doxyfile.cmake does not 
exist.
CMake Error at CMakeLists.txt:888 (CONFIGURE_FILE):
  configure_file Problem configuring file

... 

Thank you for the quick fix(s)...

Cheers,
Curtis

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68984#68984





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Curtis,

I'll have to try and reproduce on a Linux box on my side. But could you try
to pull current master and check if you can get further ?

--
nǝıɥʇɐƜ

On 12 October 2016 at 17:57, Curtis Rubel  wrote:

> Hi Mathieu,
>
>
> Basically that is exactly what I did and am getting an error.
>
> CMake Error: File /usr/local/3rdparty/osgQt-git/packaging/ld.so.conf.d/
> openscenegraph.conf.in does not exist.
> CMake Error at CMakeLists.txt:971 (CONFIGURE_FILE):
>   configure_file Problem configuring file
>
> The ld.so.conf.d directory does not exist within the packaging
> directory on my system, its actually at: /etc/ld.so.conf.d
>
> Currently ONLY the master branch 3.5.6 of osg is installed
> on my system in its default location of /usr/local/lib64.
>
> Here is my output of the entire process:
>
> amx@ios:/usr/local/3rdparty> cd osgQt-git/
> amx@ios:/usr/local/3rdparty/osgQt-git> mkdir BUILD
> amx@ios:/usr/local/3rdparty/osgQt-git> cd BUILD/
> amx@ios:/usr/local/3rdparty/osgQt-git/BUILD> cmake ..
> -- The C compiler identification is GNU 4.8.3
> -- The CXX compiler identification is GNU 4.8.3
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Found osgDB: /usr/local/lib64/libosgDB.so
> -- Found osgGA: /usr/local/lib64/libosgGA.so
> -- Found osgUtil: /usr/local/lib64/libosgUtil.so
> -- Found osgText: /usr/local/lib64/libosgText.so
> -- Found osgViewer: /usr/local/lib64/libosgViewer.so
> -- Found osgWidget: /usr/local/lib64/libosgWidget.so
> -- Found osg: /usr/local/lib64/libosg.so
> -- Found OpenThreads: /usr/local/lib64/libOpenThreads.so
> -- Found OpenSceneGraph: /usr/local/lib64/libosgDB.so;/
> usr/local/lib64/libosgGA.so;/usr/local/lib64/libosgUtil.so;
> /usr/local/lib64/libosgText.so;/usr/local/lib64/
> libosgViewer.so;/usr/local/lib64/libosgWidget.so;/usr/
> local/lib64/libosg.so;/usr/local/lib64/libOpenThreads.so (found suitable
> version "3.5.6", minimum required is "3.5.5")
> -- Looking for include file pthread.h
> -- Looking for include file pthread.h - found
> -- Looking for pthread_create
> -- Looking for pthread_create - not found
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE
> -- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so
> -- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so
> - found
> -- Looking for gethostbyname
> -- Looking for gethostbyname - found
> -- Looking for connect
> -- Looking for connect - found
> -- Looking for remove
> -- Looking for remove - found
> -- Looking for shmat
> -- Looking for shmat - found
> -- Looking for IceConnectionNumber in ICE
> -- Looking for IceConnectionNumber in ICE - found
> -- Found X11: /usr/lib64/libX11.so
> -- Found OpenGL: /usr/lib64/libGL.so
>
> The build system is configured to install libraries to /usr/local/lib64
> Your applications may not be able to find your installed libraries unless
> you:
> set your LD_LIBRARY_PATH (user specific) or
> update your ld.so configuration (system wide)
> You have an ld.so.conf.d directory on your system, so if you wish to
> ensure that
> applications find the installed osg libraries, system wide, you could
> install an
> OpenSceneGraph specific ld.so configuration with:
> sudo make install_ld_conf
>
> CMake Error: File /usr/local/3rdparty/osgQt-git/packaging/ld.so.conf.d/
> openscenegraph.conf.in does not exist.
> CMake Error at CMakeLists.txt:971 (CONFIGURE_FILE):
>   configure_file Problem configuring file
>
>
> -- Configuring incomplete, errors occurred!
> See also "/usr/local/3rdparty/osgQt-git/BUILD/CMakeFiles/CMakeOutput.log".
> See also "/usr/local/3rdparty/osgQt-git/BUILD/CMakeFiles/CMakeError.log".
>
>
> I was able to get past this error by running cmake-gui and
> manually setting the build path, then clicked configure again
> and then finally was able to generate the makefile.  After that
> the osgQt project  built and installed ok on my system.
>
> I currently have cmake 3.0.2 installed on my 64bit OpenSuSE
> 13.2 Linux system that I am using  for this initial test in case
> that affects any of this.
>
> Thank you for your quick response..
>
> Cheers,
> Curtis
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=68981#68981
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing 

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Curtis Rubel]

Hi Mathieu,


Basically that is exactly what I did and am getting an error.

CMake Error: File 
/usr/local/3rdparty/osgQt-git/packaging/ld.so.conf.d/openscenegraph.conf.in 
does not exist.
CMake Error at CMakeLists.txt:971 (CONFIGURE_FILE):
  configure_file Problem configuring file

The ld.so.conf.d directory does not exist within the packaging
directory on my system, its actually at: /etc/ld.so.conf.d

Currently ONLY the master branch 3.5.6 of osg is installed
on my system in its default location of /usr/local/lib64.

Here is my output of the entire process:

amx@ios:/usr/local/3rdparty> cd osgQt-git/
amx@ios:/usr/local/3rdparty/osgQt-git> mkdir BUILD
amx@ios:/usr/local/3rdparty/osgQt-git> cd BUILD/
amx@ios:/usr/local/3rdparty/osgQt-git/BUILD> cmake ..
-- The C compiler identification is GNU 4.8.3
-- The CXX compiler identification is GNU 4.8.3
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found osgDB: /usr/local/lib64/libosgDB.so  
-- Found osgGA: /usr/local/lib64/libosgGA.so  
-- Found osgUtil: /usr/local/lib64/libosgUtil.so  
-- Found osgText: /usr/local/lib64/libosgText.so  
-- Found osgViewer: /usr/local/lib64/libosgViewer.so  
-- Found osgWidget: /usr/local/lib64/libosgWidget.so  
-- Found osg: /usr/local/lib64/libosg.so  
-- Found OpenThreads: /usr/local/lib64/libOpenThreads.so  
-- Found OpenSceneGraph: 
/usr/local/lib64/libosgDB.so;/usr/local/lib64/libosgGA.so;/usr/local/lib64/libosgUtil.so;/usr/local/lib64/libosgText.so;/usr/local/lib64/libosgViewer.so;/usr/local/lib64/libosgWidget.so;/usr/local/lib64/libosg.so;/usr/local/lib64/libOpenThreads.so
 (found suitable version "3.5.6", minimum required is "3.5.5") 
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so
-- Looking for XOpenDisplay in /usr/lib64/libX11.so;/usr/lib64/libXext.so - 
found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib64/libX11.so
-- Found OpenGL: /usr/lib64/libGL.so  

The build system is configured to install libraries to /usr/local/lib64
Your applications may not be able to find your installed libraries unless you:
set your LD_LIBRARY_PATH (user specific) or
update your ld.so configuration (system wide)
You have an ld.so.conf.d directory on your system, so if you wish to ensure that
applications find the installed osg libraries, system wide, you could install an
OpenSceneGraph specific ld.so configuration with:
sudo make install_ld_conf

CMake Error: File 
/usr/local/3rdparty/osgQt-git/packaging/ld.so.conf.d/openscenegraph.conf.in 
does not exist.
CMake Error at CMakeLists.txt:971 (CONFIGURE_FILE):
  configure_file Problem configuring file


-- Configuring incomplete, errors occurred!
See also "/usr/local/3rdparty/osgQt-git/BUILD/CMakeFiles/CMakeOutput.log".
See also "/usr/local/3rdparty/osgQt-git/BUILD/CMakeFiles/CMakeError.log".


I was able to get past this error by running cmake-gui and
manually setting the build path, then clicked configure again 
and then finally was able to generate the makefile.  After that 
the osgQt project  built and installed ok on my system.
   
I currently have cmake 3.0.2 installed on my 64bit OpenSuSE 
13.2 Linux system that I am using  for this initial test in case
that affects any of this.

Thank you for your quick response..

Cheers,
Curtis

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68981#68981





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Curtis,

The repository now lies next to osg's :
https://github.com/openscenegraph/osgQt
To be able to compile osgQt you need to have an existing osg installation
beforehand.
I'll try to make change the Readme to explain in better detail.
What I did (macOS with Qt5) :
git clone ...
cd osgQt
mkdir build
cd build
cmake ..
make
:-)


--
nǝıɥʇɐƜ

On 12 October 2016 at 16:25, Curtis Rubel  wrote:

> Hi,
>
>   Just curious how things are proceeding with this process.
>
> I saw Roberts request to test the latest 3.5.6 Master branch with the
> new vertex buffer changes  and would like to try and do that
> but our entire baseline relies heavily on osgQt being present
> to build against.
>
> We are mainly a Linux house, but also have some Windows
> and MacOSX requirements from time to time.
>
> My first attempt to clone out the latest osgQt kit from GitHub
> does not allow me to run cmake on it successfully as
> a standalone project/directory on my system.   I looked around
> a bit and I do not see how to actually get cmake to properly
> setup the project to build with OSG now that its been
> separated.
>
> Can someone point me in the direction to find a set of
> instructions to follow or possibly give me some hints on
> how to get osgQt built against the current 3.5.6 master branch
> of OSG.  I have a little bit of time right now so, any info would
> be greatly appreciated so that we can start to provide back some feedback
> on the latest master branch of OSG as well as this
> new osgQt project.
>
> ...
>
> Thank you!
>
> Cheers,
> Curtis
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=68976#68976
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Curtis Rubel]

Hi,

  Just curious how things are proceeding with this process.

I saw Roberts request to test the latest 3.5.6 Master branch with the
new vertex buffer changes  and would like to try and do that
but our entire baseline relies heavily on osgQt being present
to build against.

We are mainly a Linux house, but also have some Windows
and MacOSX requirements from time to time.

My first attempt to clone out the latest osgQt kit from GitHub
does not allow me to run cmake on it successfully as
a standalone project/directory on my system.   I looked around
a bit and I do not see how to actually get cmake to properly
setup the project to build with OSG now that its been
separated.

Can someone point me in the direction to find a set of
instructions to follow or possibly give me some hints on
how to get osgQt built against the current 3.5.6 master branch
of OSG.  I have a little bit of time right now so, any info would 
be greatly appreciated so that we can start to provide back some feedback on 
the latest master branch of OSG as well as this 
new osgQt project.

... 

Thank you!

Cheers,
Curtis

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68976#68976





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Robert,

I received and confirmed your invitation on the OpenSceneGraph osgQt repo.
Thanks !
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi Mathieu,

On 11 October 2016 at 15:56, Mathieu MARACHE  wrote:
> Hi Robert the project is ready since it is only a extraction of osgQt in
> terms of functionality. I've merged into master and tagged as 3.5.5

I have now forked your osgQt on openscenegraph:

https://github.com/openscenegraph/osgQt

I have also added you as a collaborator, you'll need to accept this, I
presume you'll get an email with an accept link.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Robert the project is ready since it is only a extraction of osgQt in
terms of functionality. I've merged into master and tagged as 3.5.5
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi Mathieu,

How are things progressing on the osgQt front?  Is the project ready
to be moved to an openscenegraph/osgQt github repo?

Let me know when you are ready and I can fork your repo as
openscenegraph/osgQt and generate the appropriate write access for
you.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

It is a sensible but not very flexible way to answer the issue imho. I
could propose the "conan" way like we do internally (upload versioned
binary packages to a public repo). But I will make a proposal first.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Jordi Torres]

Hi Mathieu,


> If I want to compile osgQt using travisCI or appveyor I need to pull also
> osg's code to compile it ?
>

Maybe we could upload the OSG succesful builds in travis CI to docker. And
then pull it from osgQt build. I will need to figure out how to do this but
it cuold be an option.

Cheers.




>
>
>>
>> Robert.
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>


-- 
Jordi Torres
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Gianni Ambrosio]

Hi Mathieu,

Mathieu wrote:
> Qt4 is now on extended support (commercial) since december 2015. Which means 
> that any project seriously using Qt should have migrated long ago (wink to my 
> colleagues) !
> 

I would not say "long ago" in general. We moved recently to Qt5. There are 
several aspects to take in account: win10 support (from qt5.5 on if I remember 
correctly), supported compilers, ... and so on. Moreover there is also an LGPL 
license.
I would suggest to support Qt5 from a certain OSG version, but create a branch 
of the latest osgQt that supports Qt4.

Regards,
Gianni

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68668#68668





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Robert,

On Mon, Sep 19, 2016 at 9:46 AM Robert Osfield 
wrote:

> Hi Mathieu,
>
> One of the items that could complicate things is the qfont plugin as this
> would normally be placed in the lib/osgPlugins-version directory.  This
> coupling to a specific OSG version is not helpful for the osgQt build or
> maintainers.
>
> I think the solution is to simply place the
> src/osgPlugins/qfont/ReaderQFont.cpp file directly into the osgQt directory
> and remove the separate plugin completely.  One wouldn't use the qfont
> ReaderWriter without using qt/osgQt so there is nothing to loose from
> making this change, what you gain is simplicity and flexibility.
>

I'm OK with that.


> > One issue will be trigger CI builds without recompiling osg.
>
> Could you explain what specifically is the problem?
>

If I want to compile osgQt using travisCI or appveyor I need to pull also
osg's code to compile it ?


>
> Robert.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi Mathieu,

One of the items that could complicate things is the qfont plugin as this
would normally be placed in the lib/osgPlugins-version directory.  This
coupling to a specific OSG version is not helpful for the osgQt build or
maintainers.

I think the solution is to simply place the
src/osgPlugins/qfont/ReaderQFont.cpp file directly into the osgQt directory
and remove the separate plugin completely.  One wouldn't use the qfont
ReaderWriter without using qt/osgQt so there is nothing to loose from
making this change, what you gain is simplicity and flexibility.

> One issue will be trigger CI builds without recompiling osg.

Could you explain what specifically is the problem?

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

HI Mathieu,

On 18 September 2016 at 01:49, Mathieu MARACHE
 wrote:
> I cloned tom's attempt to reduce history :
> https://github.com/blobfish/osgQtCleaned01
>
> I'm now in the process of simplifying a bit some things, finding OT, OSG,
> etc.

I've just had a quick look at your osgQt repository, it still has lots
of commits.  I didn't see a separate repository cloned from Tom's.
Are there changes you haven't checked in?


> Something is still bothering me as OpenSceneGraph is not the only piece of
> software osgQt depends on, but also OpenThreads... And the needed
> OpenThreads is the one built on Qt's QThreads...
>
> OpenSceneGraph itself is agnostic of the threading library OT is built on.
> And it should, however OT is very aware :-)
>
> The only way I see removing Qt altogether from the OpenSceneGraph equation
> is to separate OpenThreads also, just like osgQt...

Part of the motivation of moving osgQt out of the core OSG was meant
to simplify things within the OSG, moving OpenThreads out is
technically possible by would add an external dependency to the OSG
that it hasn't had for a long time.

Personally I think we should avoid OpenThreads having any dependency
on Qt.  OpenThreads is a lightweight wrapper of native threading
libraries, it's not ever meant to be to be a wrapper of a large 3rd
party library that wraps the native libraries.

A solution where osgQt works correctly without requiring a Qt version
of OpenThreads would be the most sound technical solution.

One of the previous contributors to an OSG/Qt5 thread said he had
threading working robustly without the need for build OpenThreads
against Qt.  It would be worth chasing this up, I'm afraid I don't
recall the persons name though.  It think it was in a thread in the
past 6 months.

> I'm not sure how this would simplify linux distro package creators.

It would complicate linux distro's as they'd need to make a decision
about which OpenThreads to install - the one that wraps the native
threading library in a lightweight way or one that wraps Qt threading
that wraps native threading.  Adding a Qt dependency to an otherwise
small little library really isn't something you'd want to roll out to
all OpenSceneGraph applications that you might install want to have
part of a linux distribution.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi again,

I've moved forward and compiled and executed osgQt on Qt5 on macOS.
The modifications are made on my repo (forked from Tom's) in a branch :

https://github.com/mathieu/osgQt/tree/findingOSG

There are still some bits like soversion that are hardcoded (the stock
FindOpenSceneGraph.cmake doesn't provide it).



--
nǝıɥʇɐƜ

On 18 September 2016 at 02:49, Mathieu MARACHE 
wrote:

> Hi Robert,
>
> I cloned tom's attempt to reduce history : https://github.com/blobfish/os
> gQtCleaned01
>
> I'm now in the process of simplifying a bit some things, finding OT, OSG,
> etc.
>
> Something is still bothering me as OpenSceneGraph is not the only piece of
> software osgQt depends on, but also OpenThreads... And the needed
> OpenThreads is the one built on Qt's QThreads...
>
> OpenSceneGraph itself is agnostic of the threading library OT is built on.
> And it should, however OT is very aware :-)
>
> The only way I see removing Qt altogether from the OpenSceneGraph equation
> is to separate OpenThreads also, just like osgQt...
>
> I'm not sure how this would simplify linux distro package creators.
>
> Thoughts ?
>
> Le ven. 16 sept. 2016 à 18:02, Robert Osfield 
> a écrit :
>
>> On 16 September 2016 at 16:17, Mathieu MARACHE
>>  wrote:
>> > Better approach ! Looks like we have a winner :-)
>>
>> Do you want me to apply the script to my osgQt, or do you want to
>> apply them to your own.
>>
>> Once we feel that osgQt is ready to be used standalone I'd suggest
>> forking which ever of our osgQt repo's is most appropriate so that we
>> then have a osgQt on the openscenegraph git hub account, I then can
>> grant you and who else you want write permission on the project.
>>
>> Just let me know how you'd want thing to progress.
>>
>> One thing I was planning to do with my osgQt repo was simplifying the
>> CMakeLists.txt files to remove all the complex stuff that exists due
>> to complexity/history of the OSG project.  I have written a few
>> NodeKit;s over the years with simplified CMake files which I can use
>> as inspiration.  Unfortunately these aren't public projects so I can't
>> just point you at them as an example.
>>
>> Robert.
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Robert,

I cloned tom's attempt to reduce history : https://github.com/blobfish/
osgQtCleaned01

I'm now in the process of simplifying a bit some things, finding OT, OSG,
etc.

Something is still bothering me as OpenSceneGraph is not the only piece of
software osgQt depends on, but also OpenThreads... And the needed
OpenThreads is the one built on Qt's QThreads...

OpenSceneGraph itself is agnostic of the threading library OT is built on.
And it should, however OT is very aware :-)

The only way I see removing Qt altogether from the OpenSceneGraph equation
is to separate OpenThreads also, just like osgQt...

I'm not sure how this would simplify linux distro package creators.

Thoughts ?

Le ven. 16 sept. 2016 à 18:02, Robert Osfield  a
écrit :

> On 16 September 2016 at 16:17, Mathieu MARACHE
>  wrote:
> > Better approach ! Looks like we have a winner :-)
>
> Do you want me to apply the script to my osgQt, or do you want to
> apply them to your own.
>
> Once we feel that osgQt is ready to be used standalone I'd suggest
> forking which ever of our osgQt repo's is most appropriate so that we
> then have a osgQt on the openscenegraph git hub account, I then can
> grant you and who else you want write permission on the project.
>
> Just let me know how you'd want thing to progress.
>
> One thing I was planning to do with my osgQt repo was simplifying the
> CMakeLists.txt files to remove all the complex stuff that exists due
> to complexity/history of the OSG project.  I have written a few
> NodeKit;s over the years with simplified CMake files which I can use
> as inspiration.  Unfortunately these aren't public projects so I can't
> just point you at them as an example.
>
> Robert.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Better approach ! Looks like we have a winner :-)
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[tom spencer]

Hi,

Here is my attempt to help. Here is a command that I have put together that 
seems to be accomplishing the task. from 14240 commits to 1204.


Code:
git filter-branch \
--prune-empty \
--index-filter '
git ls-tree -z -r --name-only --full-tree $GIT_COMMIT \
| grep -z -v "^AUTHORS.txt" \
| grep -z -v "^ChangeLog" \
| grep -z -v "^CMakeLists.txt" \
| grep -z -v "^CTestConfig.cmake" \
| grep -z -v "^LICENSE.txt" \
| grep -z -v "^NEWS.txt" \
| grep -z -v "^README.md" \
| grep -z -v "^CMakeModules/cmake_uninstall.cmake.in" \
| grep -z -v "^CMakeModules/ListHandle.cmake" \
| grep -z -v "^CMakeModules/ModuleInstall.cmake" \
| grep -z -v "^CMakeModules/OsgCPack.cmake" \
| grep -z -v "^CMakeModules/OsgCPackConfig.cmake.in" \
| grep -z -v "^CMakeModules/OsgDetermineCompiler.cmake" \
| grep -z -v "^CMakeModules/OsgMacroUtils.cmake" \
| grep -z -v "^CMakeModules/UtilityMacros.cmake" \
| grep -z -v "^doc/Doxyfiles/all_Doxyfile" \
| grep -z -v "^doc/Doxyfiles/auto_Doxyfile" \
| grep -z -v "^doc/Doxyfiles/auto_Mainpage" \
| grep -z -v "^doc/Doxyfiles/core_Doxyfile" \
| grep -z -v "^doc/Doxyfiles/custom_Footer.html" \
| grep -z -v "^doc/Doxyfiles/doxyfile.cmake" \
| grep -z -v "^examples/CMakeLists.txt" \
| grep -z -v "^examples/osgqfont" \
| grep -z -v "^examples/osgQtBrowser" \
| grep -z -v "^examples/osgQtWidgets" \
| grep -z -v "^examples/osgviewerQt" \
| grep -z -v "^include/osgQt" \
| grep -z -v "^packaging/pkgconfig/openscenegraph-osgQt.pc.in" \
| grep -z -v "^PlatformSpecifics" \
| grep -z -v "^src/CMakeLists.txt" \
| grep -z -v "^src/osgQt" \
| grep -z -v "^src/osgPlugins/CMakeLists.txt" \
| grep -z -v "^src/osgPlugins/qfont" \
| xargs -0 -r git rm --cached -r
' \
-- \
--all



I ran this with the HEAD reset back to '489860f Updated version number to 
3.5.5' and used Roberts cleanup commit as a reference. I pushed the results to 
'github blobfish osgQtCleaned01'. If you want to try this command, note that it 
works on all branches in the repo. You might want to clone a copy of your repo 
to experiment with. Keeping only relevant history on individual files (like 
CMakeLists.txt) will be more problematic.


Thank you!

Cheers,
tom[/code]

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68610#68610





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi Mathieu,

Thanks for taking this further.  I wonder if there is some easy way of
pruning down the repository as it seems crazy to be carrying the lots
of baggage around for what should be a small little project and
repository.

I guess the crude way would be to just copy the files across to a new
repository and start from scratch with a new history for the osgQt
files. We'll always have the osgQt in the OSG history which won't be
pruned so perhaps this would be sufficient.

Robert.

On 14 September 2016 at 15:48, Mathieu MARACHE
 wrote:
> Hi All,
>
> I've gone through the process of striping the osgQt repository from osg only
> related files in it's history. This means rewriting commits and removing
> unnecessary files from each commit. This is a long process.
>
> I've added a commit removing non osgQt related examples.
> I then listed all the files present in the repository giving me listing A.
> I did a listing B of all files before Robert's removal of osg only files.
> I kept only the files given by B - A in listing C.
>
> I then issued a git command :
> git filter-branch --index-filter 'git rm --cached --ignore-unmatch [files in
> C]' HEAD
>
> It was a long process : 3615 seconds (an hour) and even thought it seems
> that the size of the repository hasn't gained any weight, there is no signs
> of those listing C files.
>
> The result is there
> https://github.com/marache/osgQt
>
> The main issue is that we now have 14240 different commits than the 14240
> commit of osg. So there is no easy turning back into osg.
> The size of a newly clone repository isn't smaller than Robert's original
> one.
>
> We could remove history altogether and use git replace to start history
> sooner than Dan's original commit
>
> Any thoughts ?
> --
> nǝıɥʇɐƜ
>
> On 14 September 2016 at 07:34, Paul McIntosh
>  wrote:
>>
>>
>> Mathieu wrote:
>> >
>> > Anyone out there wanting to chip in ?
>> >
>>
>>
>> I can help - my time is very limited though. At the very least I can
>> feedback on the documentation, setup and use.
>>
>> I have past experience with Qt/OSG/Delta3D and am currently reviving all
>> that knowledge on a personal project which combines Qt5/OSG.
>>
>> Cheers,
>>
>> Paul
>>
>> --
>> Read this topic online here:
>> http://forum.openscenegraph.org/viewtopic.php?p=68597#68597
>>
>>
>>
>>
>>
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi All,

I've gone through the process of striping the osgQt repository from osg
only related files in it's history. This means rewriting commits and
removing unnecessary files from each commit. This is a long process.

I've added a commit removing non osgQt related examples.
I then listed all the files present in the repository giving me listing A.
I did a listing B of all files before Robert's removal of osg only files.
I kept only the files given by B - A in listing C.

I then issued a git command :
git filter-branch --index-filter 'git rm --cached --ignore-unmatch [files
in C]' HEAD

It was a long process : 3615 seconds (an hour) and even thought it seems
that the size of the repository hasn't gained any weight, there is no signs
of those listing C files.

The result is there
https://github.com/marache/osgQt

The main issue is that we now have 14240 different commits than the 14240
commit of osg. So there is no easy turning back into osg.
The size of a newly clone repository isn't smaller than Robert's original
one.

We could remove history altogether and use git replace to start history
sooner than Dan's original commit

Any thoughts ?
--
nǝıɥʇɐƜ

On 14 September 2016 at 07:34, Paul McIntosh  wrote:

>
> Mathieu wrote:
> >
> > Anyone out there wanting to chip in ?
> >
>
>
> I can help - my time is very limited though. At the very least I can
> feedback on the documentation, setup and use.
>
> I have past experience with Qt/OSG/Delta3D and am currently reviving all
> that knowledge on a personal project which combines Qt5/OSG.
>
> Cheers,
>
> Paul
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=68597#68597
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Paul McIntosh]

Mathieu wrote:
> 
> Anyone out there wanting to chip in ?
> 


I can help - my time is very limited though. At the very least I can feedback 
on the documentation, setup and use.

I have past experience with Qt/OSG/Delta3D and am currently reviving all that 
knowledge on a personal project which combines Qt5/OSG.

Cheers,

Paul

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68597#68597





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi All,

I have done an initial experiment with cloning the OpenSceneGraph
repository and cutting it down to contain just the osgQt, qfont plugin
and the Qt related examples.  I haven't got it compiling yet.  I
posted it on my personal github account:

https://github.com/robertosfield/osgQt

It's a first step.  One thing we'd probably want to do is cut down the
repository itself so it doesn't contain all the history of the rest of
the OSG as the OSG repository is pretty big, osgQt should be tiny in
comparison, but as of right my osgQt has all the history of the OSG
behind it.  I'm no git master so would need to look how to cut out the
various components that we won't need the history for.  Suggestions
welcome.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi,
Regarding the hosting, within the openscenegraph account would be the best
I recon. Both for visibility and ease to find.
Concerning rights, you can setup "Collaborators" that will have push access
to the repository in the repository settings. You could then mandate a
maintainer the right to push to a osgQt repository owned by the
 openscenegraph user

Regards,
Mathieu

On Wed, Sep 7, 2016 at 9:39 PM Robert Osfield 
wrote:

>
> Another area for discussion would be where to host the main version of
> the new osgQt, we could have in the openscenegraph account alongside
> the OSG, or have it live entirely separately.  I am not clear on how
> fine grained we can make the permissions on projects within the
> openscenegraph account so an entirely separate repository might be
> best w.r.t permissions.
>
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

HI Mathieu,

Thanks for offering to help out.

I agree the easiest way to create an osgQt project would be to clone
the whole OSG then cut down and then replace the CMake build to be a
bit more streamlined.  I have written other NodeKits that have have
relatively straight forward CMake build.

I could tackle this and then let others clone my cut down version, or
others could just directly do there own clone and cutdown.

Another area for discussion would be where to host the main version of
the new osgQt, we could have in the openscenegraph account alongside
the OSG, or have it live entirely separately.  I am not clear on how
fine grained we can make the permissions on projects within the
openscenegraph account so an entirely separate repository might be
best w.r.t permissions.

Robert.


On 6 September 2016 at 19:50, Mathieu MARACHE  wrote:
> Hi Robert,
>
> We are users of the osgQt library, we are in the process of migrating from
> Qt4 to Qt5. I can propose to be the maintainer of the osgQt Nodekit...
>
> I would propose, in order to keep the history, to fork the current osg repo
> and cut out everything else to create an osg Nodekit library.
>
> Anyone out there wanting to chip in ?
>
> Le mar. 6 sept. 2016 à 15:10, Robert Osfield  a
> écrit :
>>
>> Do we not have any Qt users anymore? No one care enough to chip in?
>>
>> I'm not going to wait around forever before making decisions.  I need
>> to get on with moving the OSG towards OSG-3.6.
>>
>> The OSG/Qt users need to decide how they want to progress from here
>> once osgQt has been move out from the core OSG.  If you don't step up
>> then osgQt will likely languish unloved and unsupported. I don't have
>> the Qt expertise to do the support, you guys need to step up.
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

HI Sebastian,

To be clear, it's not a case of a democratic vote of whether osgQt
remains part of the core or not.  I've discussed the mater at length
previously, it became clear that the current status quo isn't viable,
osgQt really should never have been merged in the first place, Qt is
such a huge external dependency makes osgQt completely at odds with
the rest of the core OSG which has OpenGL/C++ at the core.

For OSG-3.6 will not be part of the core.  As the maintainer of the
OSG I'm not prepared to keep maintaining something I have no expertise
over.

The decision now is how the community want to progress with osgQt once
it's out of the core.  I can help Sheppard the move out of the core,
but once it's out it bar far best maintained by those who know Qt and
have a need for osgQt.

Robert.

On 6 September 2016 at 21:13, Sebastian Messerschmidt
 wrote:
> Hi,
>
> I'd vote for keeping osgQT in the core, with maintenance for  the current Qt
> version only.
> Basically that would mean to keep the legacy qt things out of the core, thus
> reducing maintenance efforts but keeping compatibility for the current
> versions.
> Right now the Qt+OSG combination is frustrating enough and pushing it out of
> the core won't improve the situation. Yet a lot of people use this
> combination (osgEarth I think is using it definitively), so totally
> separating it might decrease acceptance.
> So basically having the Qt5 version supported by the current OSG version
> would be beneficial for the "stock" user, maintaining a separate
> Qt[insertOldVersionHere] repository would satisfy the needs of the "I'm
> stuck to  insertOldVersionHere - x" people.
>
> I'm not a fan of removign osgQt altogether.
>
> Cheers
> Sebastian
>
>> Hi Werner,
>>
>> The key problem we have is that the osgQt can't support both Qt4 and
>> Qt5 without rebuilding osgQt.  This is fine if you build the OSG
>> yourself, but for distributions that include OSG binaries have to
>> choose between OSG with Qt4 or Qt5.  This just doesn't work for all
>> end users, it's broken and can't be fixed while Qt is directly
>> integrated into the OSG.
>>
>> Once osgQt is out of the core OSG there will be the potential for
>> supporting both Qt4 and Qt5.  How best to manage this needs to be
>> something that the OSG Qt community decide to manage.
>>
>> Robert.
>>
>>
>>
>> On 6 September 2016 at 14:49, Werner Modenbach
>>  wrote:
>>>
>>> Hi Robert,
>>>
>>> if I recognized well, there are still frequent questions on the list
>>> about
>>> Qt-interface in OSG.
>>> At least we are using it very intensely. There was not much move in the
>>> interface since long and so
>>> we just take it as it was and as it works so far.
>>> The threading problem is a bit unsatisfactory but we learned to live with
>>> it.
>>>
>>> For us it would be a big problem if further compatibility between OSG and
>>> Qt
>>> would break.
>>> I fully understand that you like to focus on the real OSG related tasks.
>>> I have no idea what the best way would be for the future.
>>> Unfortunately I also have not enough expertise to support Qt interface.
>>>
>>> But I instantly hope there will be a good solution.
>>>
>>> - Werner -
>>>
>>>
>>> Am 06.09.2016 um 15:09 schrieb Robert Osfield:
>>>
>>> Do we not have any Qt users anymore? No one care enough to chip in?
>>>
>>> I'm not going to wait around forever before making decisions.  I need
>>> to get on with moving the OSG towards OSG-3.6.
>>>
>>> The OSG/Qt users need to decide how they want to progress from here
>>> once osgQt has been move out from the core OSG.  If you don't step up
>>> then osgQt will likely languish unloved and unsupported. I don't have
>>> the Qt expertise to do the support, you guys need to step up.
>>> ___
>>> osg-users mailing list
>>> osg-users@lists.openscenegraph.org
>>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>>
>>>
>>> --
>>> TEXION Software Solutions, Rotter Bruch 26a, D-52068 Aachen
>>> Phone: +49 241 475757-0
>>> Fax: +49 241 475757-29
>>> Web: http://texion.eu
>>> eMail: i...@texion.eu
>>>
>>> ___
>>> osg-users mailing list
>>> osg-users@lists.openscenegraph.org
>>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>>
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Sebastian Messerschmidt]

Hi,

I'd vote for keeping osgQT in the core, with maintenance for  the 
current Qt version only.
Basically that would mean to keep the legacy qt things out of the core, 
thus reducing maintenance efforts but keeping compatibility for the 
current versions.
Right now the Qt+OSG combination is frustrating enough and pushing it 
out of the core won't improve the situation. Yet a lot of people use 
this combination (osgEarth I think is using it definitively), so totally 
separating it might decrease acceptance.
So basically having the Qt5 version supported by the current OSG version 
would be beneficial for the "stock" user, maintaining a separate 
Qt[insertOldVersionHere] repository would satisfy the needs of the "I'm 
stuck to  insertOldVersionHere - x" people.


I'm not a fan of removign osgQt altogether.

Cheers
Sebastian

Hi Werner,

The key problem we have is that the osgQt can't support both Qt4 and
Qt5 without rebuilding osgQt.  This is fine if you build the OSG
yourself, but for distributions that include OSG binaries have to
choose between OSG with Qt4 or Qt5.  This just doesn't work for all
end users, it's broken and can't be fixed while Qt is directly
integrated into the OSG.

Once osgQt is out of the core OSG there will be the potential for
supporting both Qt4 and Qt5.  How best to manage this needs to be
something that the OSG Qt community decide to manage.

Robert.



On 6 September 2016 at 14:49, Werner Modenbach
 wrote:

Hi Robert,

if I recognized well, there are still frequent questions on the list about
Qt-interface in OSG.
At least we are using it very intensely. There was not much move in the
interface since long and so
we just take it as it was and as it works so far.
The threading problem is a bit unsatisfactory but we learned to live with
it.

For us it would be a big problem if further compatibility between OSG and Qt
would break.
I fully understand that you like to focus on the real OSG related tasks.
I have no idea what the best way would be for the future.
Unfortunately I also have not enough expertise to support Qt interface.

But I instantly hope there will be a good solution.

- Werner -


Am 06.09.2016 um 15:09 schrieb Robert Osfield:

Do we not have any Qt users anymore? No one care enough to chip in?

I'm not going to wait around forever before making decisions.  I need
to get on with moving the OSG towards OSG-3.6.

The OSG/Qt users need to decide how they want to progress from here
once osgQt has been move out from the core OSG.  If you don't step up
then osgQt will likely languish unloved and unsupported. I don't have
the Qt expertise to do the support, you guys need to step up.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


--
TEXION Software Solutions, Rotter Bruch 26a, D-52068 Aachen
Phone: +49 241 475757-0
Fax: +49 241 475757-29
Web: http://texion.eu
eMail: i...@texion.eu

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi Werner,

The key problem we have is that the osgQt can't support both Qt4 and
Qt5 without rebuilding osgQt.  This is fine if you build the OSG
yourself, but for distributions that include OSG binaries have to
choose between OSG with Qt4 or Qt5.  This just doesn't work for all
end users, it's broken and can't be fixed while Qt is directly
integrated into the OSG.

Once osgQt is out of the core OSG there will be the potential for
supporting both Qt4 and Qt5.  How best to manage this needs to be
something that the OSG Qt community decide to manage.

Robert.



On 6 September 2016 at 14:49, Werner Modenbach
 wrote:
> Hi Robert,
>
> if I recognized well, there are still frequent questions on the list about
> Qt-interface in OSG.
> At least we are using it very intensely. There was not much move in the
> interface since long and so
> we just take it as it was and as it works so far.
> The threading problem is a bit unsatisfactory but we learned to live with
> it.
>
> For us it would be a big problem if further compatibility between OSG and Qt
> would break.
> I fully understand that you like to focus on the real OSG related tasks.
> I have no idea what the best way would be for the future.
> Unfortunately I also have not enough expertise to support Qt interface.
>
> But I instantly hope there will be a good solution.
>
> - Werner -
>
>
> Am 06.09.2016 um 15:09 schrieb Robert Osfield:
>
> Do we not have any Qt users anymore? No one care enough to chip in?
>
> I'm not going to wait around forever before making decisions.  I need
> to get on with moving the OSG towards OSG-3.6.
>
> The OSG/Qt users need to decide how they want to progress from here
> once osgQt has been move out from the core OSG.  If you don't step up
> then osgQt will likely languish unloved and unsupported. I don't have
> the Qt expertise to do the support, you guys need to step up.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
> --
> TEXION Software Solutions, Rotter Bruch 26a, D-52068 Aachen
> Phone: +49 241 475757-0
> Fax: +49 241 475757-29
> Web: http://texion.eu
> eMail: i...@texion.eu
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Gianni Ambrosio]

Hi All,
I use osgQt. Currently I'm on Qt 5.5 with OSG 3.4 but if I remember correctly 
older OSG versions are not compatible with Qt5 and vice versa. So probably 
there should be two different forks: osgQt4 from the OSG version compatible 
with Qt4, and osgQt5 from an OSG version compatible with Qt5. From which 
version make a fork for osgQt5 depends on the modifications on osgQt of the 
latest OSG stable version wrt trunk code.

Regards,
Gianni

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=68538#68538





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Mathieu MARACHE]

Hi Robert,

We are users of the osgQt library, we are in the process of migrating from
Qt4 to Qt5. I can propose to be the maintainer of the osgQt Nodekit...

I would propose, in order to keep the history, to fork the current osg repo
and cut out everything else to create an osg Nodekit library.

Anyone out there wanting to chip in ?

Le mar. 6 sept. 2016 à 15:10, Robert Osfield  a
écrit :

> Do we not have any Qt users anymore? No one care enough to chip in?
>
> I'm not going to wait around forever before making decisions.  I need
> to get on with moving the OSG towards OSG-3.6.
>
> The OSG/Qt users need to decide how they want to progress from here
> once osgQt has been move out from the core OSG.  If you don't step up
> then osgQt will likely languish unloved and unsupported. I don't have
> the Qt expertise to do the support, you guys need to step up.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Werner Modenbach]

Hi Robert,

if I recognized well, there are still frequent questions on the list
about Qt-interface in OSG.
At least we are using it very intensely. There was not much move in the
interface since long and so
we just take it as it was and as it works so far.
The threading problem is a bit unsatisfactory but we learned to live
with it.

For us it would be a big problem if further compatibility between OSG
and Qt would break.
I fully understand that you like to focus on the real OSG related tasks.
I have no idea what the best way would be for the future.
Unfortunately I also have not enough expertise to support Qt interface.

But I instantly hope there will be a good solution.

- Werner -

Am 06.09.2016 um 15:09 schrieb Robert Osfield:
> Do we not have any Qt users anymore? No one care enough to chip in?
>
> I'm not going to wait around forever before making decisions.  I need
> to get on with moving the OSG towards OSG-3.6.
>
> The OSG/Qt users need to decide how they want to progress from here
> once osgQt has been move out from the core OSG.  If you don't step up
> then osgQt will likely languish unloved and unsupported. I don't have
> the Qt expertise to do the support, you guys need to step up.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

-- 
*TEXION Software Solutions*, Rotter Bruch 26a, D-52068 Aachen
Phone: +49 241 475757-0
Fax: +49 241 475757-29
Web: http://texion.eu
eMail: i...@texion.eu
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Do we not have any Qt users anymore? No one care enough to chip in?

I'm not going to wait around forever before making decisions.  I need
to get on with moving the OSG towards OSG-3.6.

The OSG/Qt users need to decide how they want to progress from here
once osgQt has been move out from the core OSG.  If you don't step up
then osgQt will likely languish unloved and unsupported. I don't have
the Qt expertise to do the support, you guys need to step up.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Feedback/guidance sought on move of osgQt out into it's own project/repository

[Robert Osfield]

Hi All,

The issue of supporting Qt4 and Qt5 isn't something we can do
concurrently with the current version of the OSG's osgQt library - the
compiler or the binaries distributor has to make a compile time
decision between Qt4 or Qt5.

We've discussed this topic before back then I resolved to remove osgQt
from the core OSG and move it out into it's own separate project where
it can be evolved further as required by the community and led by
members of the community that have Qt expertise that I don't possess.

I want to make this change before OSG-3.6, otherwise this issue will
still be a sticky issue for another couple of years with no resolution
as we wait for yet another stable release cycle.

I've now got far enough with my other my work in prep for OSG-3.6 that
it's time for me tackle moving osgQt out into it's own project.
Initially I can take on the work on just moving osgQt itself out and
getting to a place where it builds and runs independently from the
OSG, compiling against the upcoming OSG-3.6 and potentially OSG-3.2
and 3.4 if we change the library name.

I'd like to retain history from the present osgQt in the separated out
project, which is where I'd like feedback from the community on how
best to go about this.  Need git/github experts for this.

Another open question is where the osgQt itself would be hosted, and
perhaps whether it should become separate osgQt4 and osgQt5 projects
right from the start.

One possibility in the layout strucure might be to have something like:

  osgQt

  include/osgQt
  include/osgQt4
  include/osgQt5
  src/osgQt
  src/osgQt4
  src/osgQt5

With osgQt deferring to osgQt4 or osgQt5 in some manner to keep
backwards compatibility.  Not sure how much this is worth the effort
though.

This is something for Qt/OSG users to chime in on.  My priority is
OSG/OpenGL rather than Qt, so won't feel the same pain if things
aren't done right while users with actual skin in the game i.e.
applications that use Qt will know what works and what doesn't far
more keenly.



--

So feedback on the practicalities of cloning what we need from the OSG
git/github to build a new base for osgQt.  And feedback on how you'd
like it to evolve in the future.  Also if we have  volunteers to take
the reign's and guide the project would be very welcome too.

Cheers,
Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org