How to create a standalone application to control Stellarium

[PotatoTroll]

I would like to create a standalone application that would control the Stellarium similar to Stellarium Console: move Stellarium to second monitor, focus on selected planets, toggle Stellarium options like atmosphere and fog on and off, chage time and so on. This would be an interesting project to work on and I would make it open source if I will manage to create it.

However the issue is that none of the documentation is clear enough on how could I achieve that, Could someone help me on achieving this or tell what is the best way to approach this?

[gzotti]

What is Stellarium Console? OK, yes, I have seen their website before. You will not find any information about this program or interface or internals from our side.

The RemoteControl plugin allows pretty much control of the program via HTTP interface from your web browser. The interface can of course be extended/improved, adapted to various screen sizes (FullHD monitor, 10" tablet, 7" tablet, 6" smartphone screen, ..., or some adaptive do-it-all solution?) Requires HTML/CSS/Javascript skills, and may require thorough study of the available classes and scriptable module properties (our API and Doxygen).

[PotatoTroll]

I get that Stellarium Control is not your project, never implied that it is :)

If we are talking about developing the a new GUI using React the only involvement is that it will probably require a new repo that will contain just the js code that later is compiled to plain html/js to be used in RC and respectively the build pipeline should be adjusted for that(or just manually copy the files to RC). But that could be to much for Stellarium for the existing functionality, unless you plan on really expanding the RC web app capabilities.

Anyway I get your point, I will try to look around and do something later, and if I will manage I'll get back here :)

[gzotti]

Ah OK. Then you would use a React-only repo for developing, and then we can either (1) optionally copy over/install the HTML/JS into the user's RC directory in a separate user download/install process (i.e., keep it outside the Stellarium project but e.g. recommend its usage in the User Guide) or (2) deploy this build as external dependency in our build process as default component as long as it works. If delivered with the regular install, I think the default visual style (color selection) should be close to our current style, but of course technically you can then use what React has to offer, and show what UI design in the 2020s has to offer.

If the repo is not owned by us, I see some danger of eventual deprecation. I hope you are prepared for a decade or more of maintenance. Not many people use the RC interface (the HTML was built for an exhibition operator originally, but the API is now used by other programs), but I know a few planetarians who would like to see more/better interfacing for their installations. I also have ideas, but not enough time.

There is still the ancient Text User Interface. Maybe I can extend the RC plugin to incorporate the text display along the dome perimeter (and possibly other unique features), then the plugin could be phased out. Too much code for too few maintainers...

[PotatoTroll]

In terms of visual style, it would be helpful if you had someone who could sketch a design to follow :)
Also an interesting fact, Stellarium Console uses almost only red color, it looks ugly, but is probably used to help somehow by reducing the light inside the small planetariums or something, not sure..

[gzotti]

I only mean the color scheme, appearance (round corners etc) and icons of our own existing main GUI. This is encoded in our CSS files, and I think it should by default harmonize to appear as integral part. Alternative color schemes for daylight use, dark dome use etc., are possibly useful extensions, and radically redesigned UI elements could also find new friends. Our GUI can be tweaked by loading a customized CSS, but it's for experts -- see User Guide.

Regarding menu layout, you can probably either replicate the current UI panels (so that all users know what's where; this strategy has been largely followed in RemoteControl's current web UI) or design something fresh that should be consistent, but may be entirely different as long as it is useful (speaking of Responsive web interface that looks good on all screen sizes including smartphones). The definition of useful may be a problem, though...

[gzotti]

@PotatoTroll any updates on your project?