Hi Juan,
- Make this thread a sticky in the New Scripts and Modules section.
How do I do this? Do I ceck the 'Lockthis topic' checkbox or is that for something else? I believe I have just earned the
right of the Newbie classification.
- Incorporate this script into the set of standard scripts in all PixInsight Core distributions.
This sounds like something only you can do. If you feel it's ready, then please do so.
- This script deserves and needs a wide distribution to the whole PixInsight community. For this purpose:
Everybody should be aware of its existence. I'll be glad to send an email circular to all PI users, pointing them to this thread.
It should be distributed through the update system, along with its documentation. Are you planning to set up your own PixInsight repository? Do you need help with this? — I'll be glad to support you, as needed.
I agree to both of these items, especially the update system. Using attachments is ugly! You do realize that after you send out the Email circular,
I will be swamped with posts to respond to!
I do not now have a web site nor do I forsee one in the near future so your help with this will be greatly appreciated.
If you want, I can help you to make this script instantiable. It is an essential feature IMO. What do you think?
I do like this idea but at this point implementing this type of feature is beyond me. I accept your offer for help.
[Another feature that would be very nice, is an option to work in two modes: simplified and extended. In simplified mode, only a reduced set of critical parameters would be available to the user. For example, you usually don't need to tweak the RANSAC Tolerance parameter of StarAlignment, etc. In extended mode, all parameters would be available, as now happens.
Good idea. This would reduce the amount of scroling currently required. This is going onto the TODO list. Thanks.
Along with that, there are a few things of minor importance, such as some buttons not well rendered on Mac OS X (that's a common problem with OS X's Aqua style) —I can fix this for you if you want—
Please do. And if it's something that can be coded in the script, please post a code snippet so I can do the same in future scripts(yes, I have more ideas).
and the fact that all images in your documentation have .PNG file extensions, which prevents them from loading on case-sensitive platforms (all but Windows).
Would changing them all to lower case take care of the problem? I used the Snippit tool in Vista which produced the upper case extension.
One last thing before I forget, thankyou
very much for the Documentatoin Compiler tool. It is an excellent addition to the developer's tool
chest and without it I would not have even tried to tackle the HTL code and style sheets(ugh).
John