[scribus] feature request

Tue Dec 7 13:11:23 UTC 2021

Hi DL 

And thanks for the lengthy comment, the script throws an error here of ‘Unable to load Python library” - I have no idea what Python is BTW.  And do not have the time or the know how to write scripts

Just the image name showing some where would be so useful

kind regards
Colin

> On 7 Dec 2021, at 12:00, scribus-request at lists.scribus.net wrote:
> 
> Send scribus mailing list submissions to
> 	scribus at lists.scribus.net
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.scribus.net/mailman/listinfo/scribus
> or, via email, send a message with subject or body 'help' to
> 	scribus-request at lists.scribus.net
> 
> You can reach the person managing the list at
> 	scribus-owner at lists.scribus.net
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of scribus digest..."
> 
> 
> Today's Topics:
> 
>   1. Re:  feature request (Colin Madwolf)
>   2.  Scribus Roadmap? (David Burleigh)
>   3. Re:  feature request (dl)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 7 Dec 2021 08:49:36 +0000
> From: Colin Madwolf <colin at madwolf.co.uk>
> To: scribus at lists.scribus.net
> Subject: Re: [scribus] feature request
> Message-ID: <1925715C-99A4-479D-805D-7261F289E3ED at madwolf.co.uk>
> Content-Type: text/plain;	charset=us-ascii
> 
> Hi
> As you know I am designing a large book with over 300 pages
> 
> There are 687 images - so far
> 
> It is quite slow - but, one of the things that would REALLY help my workflow would be if the image file name was visible in the Image Frame content properties
> 
> When I have to insert a new image it would be good to be able to see the file name here, so that I know what the next one is - instead of having to scroll through all the images repeatedly to look for the correct one
> 
> At a later date if that image needs editing, it would make finding it so much easier if you could see the filename
> 
> Thanks in advance
> Colin
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 07 Dec 2021 03:55:01 -0500
> From: David Burleigh <david.burleigh at saphar.net>
> To: scribus at lists.scribus.net
> Subject: [scribus] Scribus Roadmap?
> Message-ID:
> 	<f852c3ec20be73b228d5067ceec354d0731607e6.camel at saphar.net>
> Content-Type: text/plain; charset="utf-8"
> 
> The "Scribus Roadmap" seems to have become rather static. Is a new
> release of Scribus coming any time soon?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.scribus.net/pipermail/scribus/attachments/20211207/597c17d4/attachment.htm>
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 7 Dec 2021 11:17:34 +0000
> From: dl <dl.lists at ntlworld.com>
> To: Colin Madwolf <colin at madwolf.co.uk>
> Cc: scribus at lists.scribus.net
> Subject: Re: [scribus] feature request
> Message-ID: <60f3fff8-a607-6c53-6da8-129e7aea97c5 at ntlworld.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> 
> 
> On 07/12/2021 08:49, Colin Madwolf wrote:
>> Hi
>> As you know I am designing a large book with over 300 pages
>> 
>> There are 687 images - so far
>> 
>> It is quite slow - but, one of the things that would REALLY help my workflow would be if the image file name was visible in the Image Frame content properties
>> 
>> When I have to insert a new image it would be good to be able to see the file name here, so that I know what the next one is - instead of having to scroll through all the images repeatedly to look for the correct one
>> 
>> At a later date if that image needs editing, it would make finding it so much easier if you could see the filename
>> 
>> Thanks in advance
>> Colin
> Any workflow automation question interests me whatever the application.
> Currently I am not a frequent user of Scribus.
> But I develop custom automation scripts to apply to other similar 
> complex workflows.
> 
> In Ubuntu 20.04 > Scribus 1.5.5 (it helps to declare user environment) 
> my first thought was to explore Scripter.
> 
> Sure enough there is a script DirectImageImport.py in
> /usr/share/scribus/scripts/DirectImageImport.py
> 
> I noticed that I last played with this script in 07/2019.
> 
> I open a blank Scribus document, inserted an image frame, highlighted 
> it. and applied through toolbar:
> 
> Scripter > Scribus Scripts > DirectImageImport
> 
> This launches a GUI to select the image to be imported.
> 
> I chose in left navigation panel $HOME/Pictures folder since it contains 
> images. You could create a project folder with a tree structure 
> (subfolders) to hold your 600 and growing images repository.
> 
> In Image Import GUI tick ?Show Preview?.
> 
> You now have a preview of each selected image and some properties below 
> each preview.
> 
> Now I suggest that this is a launchpad. A starting point. You could 
> customise the Python script to do much more .. such as printing more 
> metadata to suit your workflow.
> 
> For example has the image been imported previously and so on. You might 
> wish to tag imported images as you suggest for future editing.
> 
> Admittedly, this script does not display the Image File Name in the 
> Image Frame properties. But if you need this a popup note launched from 
> within DirectImageImport.py could easily display this overlay 
> information. In Ubuntu I would call Xpad tool. 
> https://linuxhint.com/install-and-use-xpad-ubuntu/
> 
> To conclude, leverage Scripter for custom workflows and consider writing 
> your own scripts which perhaps work _in concert_ with other 
> tools/scripts. You can print a log of such imports.
> 
> Automation is the keynote for your workflow. I could see the Python 
> script interfacing to say GoogleSheets through Python API.
> 
> DL
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.scribus.net/pipermail/scribus/attachments/20211207/2e3acfb3/attachment.htm>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> scribus mailing list
> scribus at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus
> 
> 
> ------------------------------
> 
> End of scribus Digest, Vol 165, Issue 2
> ***************************************