Sorry for the delayed response, skatebiker, to your review of Mephemeris. I thank you for doing so, even though I am not sure I agree with some of your evaluation

1) True, any 'load up' settings need to be controlled by editting the 'ini' file. If you can suggest some of them that would greatly benefit from 'remembering' from one session to another, please suggest it. I figured that most/all were fairly 'static' and did not need this feature i.e. set it up once, and leave it alone after that.

2) In this thread, and also in the README, it mentions how the sky plot screen can be 'refreshed' without having an explicit 'button' marked to do so. One of the ways is simply to 'touch' the plot itself. Did you see that in the README file?

3) I agree that the 'text' in the 'location' setter looks bad -- but (believe me) I tried a zillion combinations in PyGTK and this was the best that I could do. I suspect a bug in the libraries.

4) TA-t3 speaks for me re: Pluto, and I made a similar comment about this in your same comment for the 'MOrrery' program

As far as being 'beta' software, well, I had always thought that this meant that the software was still 'buggy' and not ready for practical use. Here is what Wikipedia says:

"unstable and not yet ready for release"

[http://en.wikipedia.org/wiki/Beta_version#Beta]

I suppose this is rather subjective, but I tried to make sure that I did not declare Mephemeris to be version '1.0' until I had taken all the known 'bugs' out, and introduced sufficient 'functionality' that it would be 'usable'. So, IMHO, Mephemeris is no longer 'beta' software