PropagatePreviews Script

[Enzo De Bernardini]

(en español abajo)

Hello,

Inspired by this post, I wrote this simple script (see attach) that copies all active image previews to all open images. There are many improvements that can be done, but it's a start. It has no GUI and, warning, it delete all existing previews and only leaves propagated previews from the active image.

Best regards,

Enzo.

EDIT Aug 19, 2010: GUI added, selection of previews to copy, selection of target images, and preserve existing previews option. New JS file version and screenshot attached.

-

Hola,

Inspirado en este post he escrito este sencillo script (ver adjunto) que copia todos los previews de la imagen activa a todas las imágenes abiertas. Hay muchas mejoras para hacer, pero es un comienzo. No posee interfaz de usuario y, cuidado, el script borra todos los previews existentes y deja únicamente los propagados desde la imagen activa.

Saludos,

Enzo.

EDITADO 19 Ago 2010: Añadido de interfaz de usuario, selección de previews, selección de imágenes de destino y opción de preservar los previews existentes. Nuevo archivo JS y captura de pantalla adjunto.

[Nocturnal]

Cool. As Juan would say, "Welcome to PJSR programming"

[Enzo De Bernardini]

Cool. As Juan would say, "Welcome to PJSR programming"

Thanks Sander! I hope to be improving my skills with time. 

Regards,

Enzo.

[peregil]

Hi Enzo,
Thanks for the script! Very useful!

Regards,
Pere

[Enzo De Bernardini]

Thanks for the script! Very useful!

Thanks Pere! I'm glad you find it useful. I update the script with some improvements, including the GUI for greater control.

[Niall Saunders]

Hi Enzo,

Thanks for this script - I'll download it when I get back to my PI machine

In the meantime, one suggestion, it can be easier if you just post a revision in a new message thread reply. That way, the latest revision level can be easier to find (IMHO, anyway). It might also be useful if the file attachment 'name' included the 'revision level' as well - then it is easier for prospective users to manage to download into their PC.

Trivial points - none of which detract from your excellent efforts.

Cheers,

[Nocturnal]

The problem with revision numbers is that PI only finds the first instance when prompted to scan for scripts. So the user needs to remove the old version before adding the new one. As long as a version number is embedded in the script itself I see no issue with the script being published with a single name.

[Enzo De Bernardini]

Hi Enzo,

Thanks for this script - I'll download it when I get back to my PI machine

In the meantime, one suggestion, it can be easier if you just post a revision in a new message thread reply. That way, the latest revision level can be easier to find (IMHO, anyway). It might also be useful if the file attachment 'name' included the 'revision level' as well - then it is easier for prospective users to manage to download into their PC.

Trivial points - none of which detract from your excellent efforts.

Cheers,

Thanks Niall!. You're right!, I too find useful the script revision in filename, perhaps only in the zip filename, and then simply overwrite the current js (for avoid the detail commented by Sander) In the future I think it would be interesting to have a script-repository, more organized.

Best regards, and thanks for the tips.

Enzo.

[Niall Saunders]

script-repository, more organized

I was going to mention exactly that in my last post.

Perhaps the detailed discussion of this should be moved into the Wish List section of the Forum - so that it is more 'visible'

Cheers,

[Nocturnal]

AstroPlanner has a nice built in user-submitted script interface. Of course it also has many many scripts

[Niall Saunders]

"Centralised Module Repository"

I have just opened a new message thread to this effect in the Wish List section.

Cheers,