Markerz wrote:which means the need for windows dev is not that strong (other than testing).
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 too hard. macOS has screen recording feature (you can also specify the area for recording) built in, and bundling video capture in celestia will only make the app size grow quite a bit (ffmpeg is a heavy dependency) and I suppose it should be easy to find similar programs on windows.john71 wrote:2.) some useful functions, like video capture will be missing
if we are only adding new features, there will just be UI changes, not messing around with the rendering code, then there should not be performance issue related to rendering.john71 wrote:3.) the Windows version will be somehow slow and will have some kind of strange latency.
Markerz wrote:I don't think they'll come to win32 frontend
Markerz wrote:I suppose it should be easy to find similar programs on windows.
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.john71 wrote:I don't think that any 32 bit Windows OS has a future, so it is a non-issue in my opinion.
video capturing inside celestia has performance penalty as well. the system level video capturing could be more performant.john71 wrote:The "inside" solution is better for video recording, because Celestia slows down when recording in order to not to lose any frames.
Markerz wrote:win32 is a name of the UI toolkit.
Markerz wrote:If there are new features and requires complicated UI, I don't think they'll come to win32 frontend.
Art Blos wrote:Celestia is useful not only for beautiful views. So I strongly disagree.
john71 wrote:Is it possible that we can maintain and develop a Windows UI?
https://learn.microsoft.com/en-us/cpp/windows/wal ... applications-cpp?view=msvc-170
Markerz wrote:we need devs that have expertise in developing UI (or those who are willing to spend significant time learning building UI, not just any developer)
yes, OBS exists, its free and easy to use while still having lots of functionalityMarkerz wrote:and I suppose it should be easy to find similar programs on windows
i agree on this. win32 is old and is missing tons of features compared to other frontends like Qt, and microsoft doesnt seem to have much interest in developing win32 to be more advancedMarkerz wrote:If there are new features and requires complicated UI, I don't think they'll come to win32 frontend
it does occur on lower-end and/or older hardware. but screen recording in general requires a fairly decent computer regardless, especially at higher resolutions and frameratesjohn71 wrote:What about the dropping of frames?
that link appears to talk about winUI which does not work with openGL even through the use of small hacks like using ANGLE, as previously stated in this threadjohn71 wrote:Is this link relevant?
TheLostProbe wrote:i agree on this. win32 is old and is missing tons of features compared to other frontends like Qt, and microsoft doesnt seem to have much interest in developing win32 to be more advanced
TheLostProbe wrote:that link appears to talk about winUI which does not work with openGL even through the use of small hacks like using ANGLE, as previously stated in this thread
i dont know what lev is doing regarding Qt frontend development. as far as i know he prefers to stick to just mac and mobile developmentjohn71 wrote:OK, now I don't get it. Will Markerz develop a Qt UI for Windows?
yes. can i do it now? no. can i do it quickly enough for 1.7's release? probably not. the only thing im good for at the moment is bug reports and fancy concept images. i can design a nice looking frontend in GIMP but i cant make it come to lifejohn71 wrote:Can you learn to build a UI for Windows?
Markerz wrote:what you are asking just does not make sense here.
john71 wrote:Does the Qt frontend need any further developing?
So Celestia 1.7 under Windows will use the Qt frontend?
QT continues to be slower under same load. If the situation does not improve, for now it is necessary to leave the native interface as the main.Markerz wrote:No decision has been made as to what frontend official Celestia 1.7.0 will be used. But I assume both Win32 and QT will be available if Win32 is not lagging too much behind or has significant issues.
