Dear Stellarium developers:
I'm a grateful user of Stellarium for many years. It's the best and
pretty application I have ever seen. I wish I could have made it .
My idea is to propose a complementary IDE for the
Stellarium script language as final project of a PhD courses subject. It would
an external and stand-alone executable and cross-platform C++ object
oriented application using wxWidgets as GUI library.
The main potential features for the editor are:
If everything's ok this project will be complete by july.
I hope you can consider my proposal.
Thank you in advance,
You seem to have CSS turned off.
Please don't fill out this field.
You have very nice proposal, but I have some questions about it.
How do you plan to teach your IDE set of Stellarium's API functions?
How do you plan development your IDE when Stellarium's API's changed?
This class is the key:
This sounds like an interesting project. Alex raises some important points.
With respect to changes to the scripting API, it would be possible to write a
script which parses Stellarium source code and generates a list of available
public slots for some named set of classes - this is how the API is built up.
Unless you are closely tied to wxWidgets, I would recommend QT - I feel is a
better API for this sort of program. Moreover, if I were to approach this
problem, I would consider implementation as a module for something like QT
Creator or KDevelop, or to enhance the script console feature of Stellarium
itself, rather than making a whole new IDE.
Having said all this, I don't want you to feel like I'm putting constraints on
what you do - this is just me thinking out loud. Whatever you decide to do,
one part of your project which would really benefit Stellarium directly would
be to enhance the documentation of the scripting API. Please do submit patches
for the Stellarium code for documentation improvements.
"...it would be possible to writea script which parses Stellarium source code
and generates a list of available
public slots for some named set of classes..."
It sounds nice, but could you be more specific or write an example for this
sentence? I really don't understand what this issue means. The question is I
have to implement a final project for a PhD Ruby's subject that processes
source code and generates and output. Would you have any proposal or "to do"
project in Stellarium to use Ruby inside/outside Stellarium source code
appliaction or plugin?
Well, the scripting API is something which any decent IDE needs to be aware of
- for implementing code completion, syntax highlighting and such... so
somehow, you need to tell your IDE program what keywords are relevant to
Stellarium scripting. How can you get a list? Well.. you can parse the source
The scripting API is made up of the public slots for some specific list of
objects in the program... one for each "module", and a few others too.
What I would propose is actually to use QT's moc command line tool and parse
the output of that tool. The reason for this is that "slots" are a QT-specific
thing. This is a reason why I would recommend to use QT instead of
wxWidgets... only with some small understanding of QT can you know what I'm
talking about. :-)
It might be helpful to have a real-time chat about this, rather than this
highly asynchronous and cumbersome forum mechanism. I'm often in the IRC
channel: #stellarium on freenode.
Just saw you in there in the history. If you don't use my full name, I don't
get a notification that you talked to me, so please do prefix messages
addressed to me with my full nick (matthewg42).
Sounds like a great idea!
The new scripting engine has so much more potential than the older
The only thing holding it back is it is much more complicated and not as user
friendly for the casual programmer
Anything that helps would be welcome
I like this "Line and columns indicators"
One frustrating thing with the script is errors, you miss a comma or a bracket
somewhere and get those parse errors and there's no way to find where your
error is except to search dozens or even hundreds lines of code.
As as for Help, Remember the KISS principle, which is unfortunately lacking in
the current manual
Anyhow, best of luck to you, I look forward to seeing what you come up with
Sign up for the SourceForge newsletter: