Celestia Forums

I created an official Celestia channel here https://www.youtube.com/channel/UCW-L9ekZTPTrl1l8t4wwrBQ which can be used for future use. videos will be promoted inside the mobile Celestia apps

I wonder if we hooked up the wrong button here, the left, right arrow keys are hooked up to Roll.

JOS wrote:It does work since there is no access to the directory

I suppose you mean it *doesn't* work here. This is expected as I stated, Celestia has access only to /Users/jos/Downloads/nroutes/nroutes.celx (the file it opened), not /Users/jos/Downloads/nroutes/nroutes.csv

it is part of modern app development to have everything automated. it's not because it is difficult, it is rather because that local development are not reliable. One can generate a build and create an installer locally, but first your local environment could affect the output of installer. for exam...

let's clear up on permissions for Celestia (on macOS, it is similar on iOS). User permission to a directory does not equa Celestia app's permissions. Files and folders inside app bundle, (read access, no write access): Any things under /Applications/Celestia.app (could have different names)/Contents...

macOS version's Celestia's default directory is /Applications/Celestia.app (depending on where you put it)/Contents/Resources/CelestiaResources. So if you use relative path or file name, the actual path will be under this path. And this path is not writable!!! That's why you get permission issues. Y...

macOS versions of Celestia (after 1.6.1) are running in a sandbox, it cannot write to arbitrary file. The files that Celestia has access to is under /Users/your user name/Library/Containers/space.celestia.Celestia/Data/Documents If you use App Store version then it is /Users/your user name/Library/C...

selden wrote:If there's a pre-existing installation of Celestia, does it install to (or default to installing in) the pre-existing directory?

probably not, I've not tested but you can check

I've been adding automation to installer generation. code: https://github.com/CelestiaProject/Celestia/pull/1499 can test with the artifacts here: https://github.com/CelestiaProject/Celestia/actions/runs/3882535755 (installer is xxx.zip/installer/CelestiaInstaller.exe) Note that the 64bit installer ...

for star and dso name localization I believe you need to check https://github.com/CelestiaProject/CelestiaContent/blob/master/data/well-known-starnames.txt and https://github.com/CelestiaProject/CelestiaContent/blob/master/data/well-known-dsonames.txt . these are the list of them that are marked tra...

QT is cross platform (macOS, Windows, Linux) and any feature coming to QT, comes to all platforms. I believe onetwothree only meant that he won't be testing on windows or won't be tackling with very windows specific bug. With QT there are not many of them. Does the Qt frontend need any further devel...

john71 wrote:Will Markerz develop a Qt UI for Windows?

why? we already have that

john71 wrote:But can you help with the Qt frontend?

what you are asking just does not make sense here. you've been saying that we need a dev, we need a qt dev, nothing specific. what do we need to solve here?

Is it possible that we can maintain and develop a Windows UI? https://learn.microsoft.com/en-us/cpp/windows/walkthrough-creating-windows-desktop-applications-cpp?view=msvc-170 this link is basically about how to write an app with plain win32 calls, and is what the current version of celestia uses (...

Github actions has inno setup preinstalled in the runner images: https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md so probably we just need to pass the .iss file to inno via command line and it should generate an installer. registry changes should have been specifie...

cartrite wrote:I thought this already being done. That's why I got busy doing other things.

iirc only GitHub action is used for continuous integration now, which only generates necessary .exe and .dll s, not the installer

a good next step would be to automate the process for generating the installer, so that every commit to the Celestia repo will create an updated setup.exe.

I don't think that any 32 bit Windows OS has a future, so it is a non-issue in my opinion. win32 is a name of the UI toolkit. it's not tied to 32bit (Microsoft kept the name when they develop for 64bit). the non-qt version you run on windows 64bit is based on win32. The "inside" solution ...

2.) some useful functions, like video capture will be missing If there are new features and requires complicated UI, I don't think they'll come to win32 frontend. besides I've been wondering why video capture is a big ask, I never added this ability to macOS version of it even though adding is not ...

Windows only development is mostly dead (I mean in general, not specific to Celestia). The win32 version of Celestia (using raw Win32 API) is very outdated because Win32 is old and it is not a modern way to develop Windows apps. Very very few people write raw Win32 code now, so I do not see new deve...

looks like a good candidate to be hosted directly on https://celestia.mobi/tools