Can I ask what's happening with Celestia development?
Do the project/participants need crowdfunding?
Do the original programmers help the work?
Can we get a regular update?
Celestia development: what's happening?
- Alexell
- Site Admin
- Posts: 303
- Joined: 07.10.2010
- Age: 30
- With us: 14 years 1 month
- Location: Moscow, Russia
- Contact:
Celestia 1.7.0 Development started in the new repository approved by Chris Laurel.john71 wrote:Can I ask what's happening with Celestia development?
In my opinion crowdfunding may be necessary if we are to attract the experienced freelancers who does not work for nothing. This is the case when the original programmers are not to return to the project.john71 wrote:Do the project/participants need crowdfunding?
I really hope that someone from the original programmers will return to the project.john71 wrote:Do the original programmers help the work?
I do not know. There are some ideas that I am trying to implement and have a couple of people who are ready to help. How quickly will advance the development of, I do not know. Help original programmers have significantly accelerated the process.john71 wrote:Can we get a regular update?
Admin of celestia.space
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
- Alexell
- Site Admin
- Posts: 303
- Joined: 07.10.2010
- Age: 30
- With us: 14 years 1 month
- Location: Moscow, Russia
- Contact:
Mira, Hi. Celestia using OpenGL. There are three graphical front-ends available: GTK or Qt.
Added after 2 minutes 23 seconds:
I do not quite understand what you mean by this question?Mira wrote:What is your program to get celestia out of obsolescence?
Added after 2 minutes 23 seconds:
Periodically we will publish interim compiled version spesial for forum members.john71 wrote:I think some of us can help with testing the new software versions...looking for bugs maybe...
Admin of celestia.space
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
Hi All,
Don't know if this has already been posted but building Celestia 1.6.1 on Ubuntu 16.04 x64 works fine
using the source from http://packages.ubuntu.com/source/trusty/celestia
Process was:
1. Install build tools
sudo apt install build-essential fakeroot devscripts
2. Install dependencies (gtk build, qt untested so far)
sudo apt install libgnomeui-dev libgtkglext1-dev libtheora-dev chrpath autotools-dev libjpeg-dev libpng-dev dpkg-dev
3. Download the files from above site
celestia_1.6.1+dfsg-3.dsc
celestia_1.6.1+dfsg.orig.tar.gz
celestia_1.6.1+dfsg-3.debian.tar.gz
4. Unpack source
tar -zxvf celestia_1.6.1+dfsg.orig.tar.gz
cd celestia-1.6.1+dfsg/
tar -zxvf ../celestia_1.6.1+dfsg-3.debian.tar.gz
5. build unsigned binary
debuild -b -uc -us
The build process ran for about 5 minutes and produced many warning messages (201 of them) about redefining INT64_MAX, e.g.
Other non INT64_MAX warnings pasted here: http://pastebin.com/8jReYAp2
But at the end the build created the following debian/ubuntu binary installer files:
celestia_1.6.1+dfsg-3_all.deb celestia-glut_1.6.1+dfsg-3_amd64.deb
celestia-common_1.6.1+dfsg-3_all.deb celestia-gnome_1.6.1+dfsg-3_amd64.deb
6. Installed Celestia with:
sudo dpkg -i *.deb
7. Then ran the program with a simple:
celestia
Spun Earth a few times then took the tour to Jupiter. Looks ok.
Are there particular tests likely to crash a dodgy build?
Will try to build from latest github repo tomorrow.
Don't know if this has already been posted but building Celestia 1.6.1 on Ubuntu 16.04 x64 works fine
using the source from http://packages.ubuntu.com/source/trusty/celestia
Process was:
1. Install build tools
sudo apt install build-essential fakeroot devscripts
2. Install dependencies (gtk build, qt untested so far)
sudo apt install libgnomeui-dev libgtkglext1-dev libtheora-dev chrpath autotools-dev libjpeg-dev libpng-dev dpkg-dev
3. Download the files from above site
celestia_1.6.1+dfsg-3.dsc
celestia_1.6.1+dfsg.orig.tar.gz
celestia_1.6.1+dfsg-3.debian.tar.gz
4. Unpack source
tar -zxvf celestia_1.6.1+dfsg.orig.tar.gz
cd celestia-1.6.1+dfsg/
tar -zxvf ../celestia_1.6.1+dfsg-3.debian.tar.gz
5. build unsigned binary
debuild -b -uc -us
The build process ran for about 5 minutes and produced many warning messages (201 of them) about redefining INT64_MAX, e.g.
Code: Select all
# define INT64_MAX (__INT64_C(9223372036854775807))
../celutil/basictypes.h:27:0: warning: "INT64_MAX" redefined
Other non INT64_MAX warnings pasted here: http://pastebin.com/8jReYAp2
But at the end the build created the following debian/ubuntu binary installer files:
celestia_1.6.1+dfsg-3_all.deb celestia-glut_1.6.1+dfsg-3_amd64.deb
celestia-common_1.6.1+dfsg-3_all.deb celestia-gnome_1.6.1+dfsg-3_amd64.deb
6. Installed Celestia with:
sudo dpkg -i *.deb
7. Then ran the program with a simple:
celestia
Spun Earth a few times then took the tour to Jupiter. Looks ok.
Are there particular tests likely to crash a dodgy build?
Will try to build from latest github repo tomorrow.
What is your plan to revive the development of celestia?
I'm not a pessimist but celestia has not been developed for a long time. Wikipedia indicates that version 1.6.1 was released in 2011. The dynamics of the old team has disappeared.
I praise your initiative to want to revive it. It is a very good initiative and I would like to help you to develop it further. You need a program to start software development and recreate a new dynamic.
And without any negative ideas, I ask your program!
For example, I can work on upgrading sources with the current version of GCC to compile it without warnings.
I'm not a pessimist but celestia has not been developed for a long time. Wikipedia indicates that version 1.6.1 was released in 2011. The dynamics of the old team has disappeared.
I praise your initiative to want to revive it. It is a very good initiative and I would like to help you to develop it further. You need a program to start software development and recreate a new dynamic.
And without any negative ideas, I ask your program!
For example, I can work on upgrading sources with the current version of GCC to compile it without warnings.
- Alexell
- Site Admin
- Posts: 303
- Joined: 07.10.2010
- Age: 30
- With us: 14 years 1 month
- Location: Moscow, Russia
- Contact:
Mira, A serious plan for the further development of Celestia I am not prepared, because now I alone do source code changes. In the near future I plan to make small changes in the source code (I've already started to do them), such as corrections in QT interface, small bug fixes, etc. After that, if people with expertise in programming in C ++ will joined, we will together make up the development plan, because it will be difficult for me one.
If you would like to help the development of the project, and you have the necessary knowledge of C ++, OpenGL, QT and work with GitHub, I will be very happy.
If you would like to help the development of the project, and you have the necessary knowledge of C ++, OpenGL, QT and work with GitHub, I will be very happy.
Admin of celestia.space
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
It's not a problem.
I try to compile on Ubuntu your Github sources.
I found in celestiacore.cpp
and winutil.h include
So with this line, all linux version will failed ?
I try to compile on Ubuntu your Github sources.
I found in celestiacore.cpp
Code: Select all
#include <celutil/winutil.h>
and winutil.h include
Code: Select all
#include <windows.h>
So with this line, all linux version will failed ?
- Alexell
- Site Admin
- Posts: 303
- Joined: 07.10.2010
- Age: 30
- With us: 14 years 1 month
- Location: Moscow, Russia
- Contact:
Mira, Frankly speaking I didn't work with MAC or Linux and didn't try to build Celestia on these OS. I collect only under Windows.
Admin of celestia.space
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
PC: Intel Core i7-8700 @ 3.20GHz, SSD, 16 Gb RAM, NVIDIA GeForce GTX 1080, Creative Sound Blaster ZxR. Windows 10 x64.
Phone: iPhone Xs 256 Gb. iOS 14.
- John Van Vliet
- Posts: 2944
- Joined: 28.08.2002
- With us: 22 years 2 months
i only made minor edits so that qmake4 and the current autotools / gcc and the current libpng16 build
and removed the kde3 code
now porting to qt5 should be mostly strait forward ??? maybe ?
using autotools with "with-gtk" also works if you have gtk2 development files installed
Gnome3 is using gtk3 so you might need to install the gtk2 files
https://github.com/JohnVV/MyCelestiaBuild
.
and removed the kde3 code
now porting to qt5 should be mostly strait forward ??? maybe ?
using autotools with "with-gtk" also works if you have gtk2 development files installed
Gnome3 is using gtk3 so you might need to install the gtk2 files
https://github.com/JohnVV/MyCelestiaBuild
.
When I did my changes for QT4->QT5 I only had to change six files.
All of these are cpp files in /src/celestia/qt
qtappwin
qtcelestialbrowser
qtdeepskybrowser
qteventfinder
qtsolarsystembrowser
xbel
The first and last I had to change 'toascii' to 'tolatin1' for string functions in params.
The rest were also simple.
'reset' as a single command replaced by
beginresetmodel
endresetmodel
with reset or clear in the middle.
I can send you the files to look at if you like, or just try a compile and it will point you straight to them.
I am not a real C/C++ programmer, and it only took me a couple of hours to puzzle my way through it.
So it is not hard, just weird.
If you copy the .pro file and rename it, you can make compile under QT4 & QT5 both at the same time.
Janus.
All of these are cpp files in /src/celestia/qt
qtappwin
qtcelestialbrowser
qtdeepskybrowser
qteventfinder
qtsolarsystembrowser
xbel
The first and last I had to change 'toascii' to 'tolatin1' for string functions in params.
The rest were also simple.
'reset' as a single command replaced by
beginresetmodel
endresetmodel
with reset or clear in the middle.
I can send you the files to look at if you like, or just try a compile and it will point you straight to them.
I am not a real C/C++ programmer, and it only took me a couple of hours to puzzle my way through it.
So it is not hard, just weird.
If you copy the .pro file and rename it, you can make compile under QT4 & QT5 both at the same time.
Janus.