Qt Celestia

[Christophe]

- why doubling the info listed in the columns in the contextual menu?

It's the same popup menu that's used in the main window.

- if a all in one browser is done, then it would be nice to see the type of planets like the type of stars (telluric, gas giant)...

That would be nice yes, but we don't currently have that information. For now the type displayed here can be planet, asteroid, moon, comet or spaceship.

[ElChristou]

- why doubling the info listed in the columns in the contextual menu?

It's the same popup menu that's used in the main window.

Ah ok, then to avoid doubling the info (not necessary) and because the layout for a search query give some blank space in the panel, the actual osX (and Windows?) buttons could be used this way:



The red squares near the mark options are supposed to call a color picker... (possible?)

- if a all in one browser is done, then it would be nice to see the type of planets like the type of stars (telluric, gas giant)...

That would be nice yes, but we don't currently have that information. For now the type displayed here can be planet, asteroid, moon, comet or spaceship.

Yep, too bad because having a "poor" "planet" is really not up to the detailed type for stars...

[ElChristou]

Just tested a Windows version, there is a slider to filter the number of hits; this feature seems not bad, so I wonder what was the reason to not use it under KDE...

[ajtribick]

In all this talk of KDE, are there any on the devteam who use GNOME?

[Christophe]

Just tested a Windows version, there is a slider to filter the number of hits; this feature seems not bad, so I wonder what was the reason to not use it under KDE...

It's just that when I "copied" it the slider wasn't there. Anyway, I'm not sure it's that usefull, 100 or 500 stars, we could just as well display all 500 by default.

In all this talk of KDE, are there any on the devteam who use GNOME?

The GTK/Gnome frontend is maintained by Pat. He hasn't submitted anything since about a year but he is still active on the mailing list.

[ElChristou]

Just tested a Windows version, there is a slider to filter the number of hits; this feature seems not bad, so I wonder what was the reason to not use it under KDE...

It's just that when I "copied" it the slider wasn't there. Anyway, I'm not sure it's that usefull, 100 or 500 stars, we could just as well display all 500 by default.

Ok, then there is a limit in the number of hits...
Is such limit up to date? I mean we have now some good DSOs catalogue, soon perhaps pulsars and other exotic objects, soon or later some revised and extended asteroids catalogues, so...

...if the browser become "stronger" (no limit in the number of hits to not lose some results), the criterions of the query would limit naturally the hits, but for a simple search (1 criterion) this slider could be useful, no?

[chris]

Here's the result of some further experimentation with Qt4:



This is not intended to show a final look for the star browser; it's primarily an experiment. Some interesting things:

- The star browser is a dockable widget: you can attach and detach it from the main window, and place it either to the right or the left of the 3D view. You can also hide it completely. The state is saved between runs of Celestia, so you can get the tools arranged the way you like and not bother with them again.
- You can select multiple stars and ranges, then mark all selected objects with a specified symbol. Optionally, you can also label the markers (thanks to a recent change by Vincent.) The screen shot shows stars with planets all marked.
- You can right click on a star in the browser and get the same popup menu you do when clicking in the 3D window. Goto, Center, Follow, etc. are done with the context menu rather than buttons. The KDE browser has the same behavior. It's nice because it's clearer what object the action affects, especially when multiple items are selected.
- Unlike the current Windows version of Celestia, special characters (Greek letters, superscripts, etc.) are shown in the star names.

--Chris

[chris]

Another another screen shot, this time with custom color selection for markers:



--Chris

[MKruer]

Christophe, is it possible to combined binary stars listings into a single group instead of three separate items.
somethign like

Code: Select all

+Rigel Kentarus A-B

Expands into

-Rigel Kentarus A-B
  -Rigel Kentarus A
  -Rigel Kentarus A-B Barycenter
  -Rigel Kentarus B

Note: Barycenter name I think should always appears in between the to stars that are orbiting around it. Example for multi star systems it would be like

Code: Select all

Star A
Star A-BC Barycenter
Star B
Star B-C Barycenter
Star C
Star BC-D Barycenter
Star D

In a nut shell this says that Star A orbits around Star B and C, Star D orbits around Star B and C, But Stars A and D do not orbit around each other.
VS.

Code: Select all

Star A
Star A-B Barycenter
Star B
Star AB-CD Barycenter
Star C
Star C-D Barycenter
Star D

Says that Stars A and B orbit around each other, C and D orbit around each other and that Stars AB and CD orbit around a common barycenter other.

Somethings you may want to add is what constellation the star is in and if it is part of the constellation itself, also the Declination and Right Ascension I think should be listed somewhere. Additional stuff like temperature, radius can be included, but I don't think it is necessary nor currently accurate.

Either way both of these are great so far. Also i believe Chris was going to add more descriptors for all objects such as Pulsars, Neutron Stars, Black Holes, Super Massive Black Holes, Dwarf Planets, KBOs, etc...

[ElChristou]

Another another screen shot, this time with custom color selection for markers:...

Nice so far!

Somethings you may want to add is what constellation the star is in and if it is part of the constellation itself, also the Declination and Right Ascension I think should be listed somewhere. Additional stuff like temperature, radius can be included, but I don't think it is necessary nor currently accurate.

Perso the question I ask myself is: shall the browser be and aid to browse the OGL window or almost a final doc where the graphical representation become useless?
What I mean is that to me the browser should only help the user to detect an object in the OGL window; once you select the object of interest in the browser all other info is on screen (const, Ra/Dec, temp etc...).
The only data that should be visible in the columns, should be the data used to sort object... (if a sorting system is implemented)

[MKruer]

Somethings you may want to add is what constellation the star is in and if it is part of the constellation itself, also the Declination and Right Ascension I think should be listed somewhere. Additional stuff like temperature, radius can be included, but I don't think it is necessary nor currently accurate.

Perso the question I ask myself is: shall the browser be and aid to browse the OGL window or almost a final doc where the graphical representation become useless?
What I mean is that to me the browser should only help the user to detect an object in the OGL window; once you select the object of interest in the browser all other info is on screen (const, Ra/Dec, temp etc...).
The only data that should be visible in the columns, should be the data used to sort object... (if a sorting system is implemented)

Sorry I didn’t mean to infer to add the columns to sort by, but rather be added as an info box like in Christophe example. This would be information that would be good to have, but not necessary sort by. I agreed if you are pointed in that direction, you should know what’s in the general vicinity via the actual OGL. With that said the only thing I would add to be displayed in the browser, but not to sort. Would be a B or an M for binary/multi star systems, and P for Planetary companions. This way if you sort it via something other then name, you know upfront that the star has companion(s). Then again would you want to search for all stats that have planarity bodies or are part of multi star systems. The tree and the list both have advantages and disadvantages so I don’t think there is one correct answer. Having both and being able to switch between then might be the best option.

[Vincent]

Another another screen shot, this time with custom color selection for markers:

Chris,

That looks good ! That makes me feel like installing MinGW and entering the Qt4 play ground...

[t00fri]

I am almost there to compile Celestia-Qt4 also without MinGW, with my good old VS2003.Net and with batch (nmake).

F.

[cartrite]

I recently built qt-x11-opensource-src-4.3.3 and kind of hacked a qt4 build on linux. First I had to run make Makefile.cvs and then ./configure for kde. After that I ran qmake on celestia.pro and then make from the top directory. Probably a better way to do it but a pretty cool screen.



There is a qt3to4 program and I was wondering if the kde programs and gui's could be ported to qt4 with that program.
cartrite

[t00fri]

The building under Linux I did already some time ago. Just take a fresh CVS copy. Type in the Celestia root directory

> touch config.h

then
> cd src/celestia/qt
> mkdir build
> cd build
> qmake ../../../celestia.pro
> make
> cd ../../../..
>ln -s src/celestia/qt/build/celestia-qt4 celestia
> celestia

Aaaaah!

Bye Fridger

NB: You dont need to run ./configure!