Content Properties not transferred/viewable when a file created from a Template

[abi]

When we are creating a page using a Template using Python script

 scribus.saveDocAs

- the content Properties dialog does not show in the new file created.

pfa
1. The video of a template file where the Content properties are loading - clickhere
2. The .sla file created by using saveDocAs function - where the content properties dont load - clickhere

Thank you

[a.l.e]

can you list the exact steps you're going through in the second case?

something like:

• create a scribus file
• make sure that the properties palette is not shown
• use scribus.saveDocAs('abc.sla') to save it
• show the properties palette

...

btw, i've tried the actions above, in the order, and the PP is there.

[abi]

To give a quick background - we have written a script in Python where we have a menu created using which we have following functions
1. Open - a file (which will read folder structure and load data)
2. Create - which will create a new file in a folder structure and file has to be created based on an existing template
3. Save - which saves and also exports into different formats and meta data files
4. Load Content - this runs an API connecting to a CMS and loads text and media files which gets added to the open file

What we have figured out is - if this menu is running while the page is open, the Content Properties are not showing. But if we close that menu which is running in background and then try to load content properties it opens.

Now we are thinking of docking the menu so it stops running from the background and only loads when we want to perform some function.

Any ideas on how we can dock the menu will be helpful

Thanks

[a.l.e]

i guess that for what scribus is concerned, it would be better to create a "scripts" toolbar, with one button for each script you want to launch.

working in a similar way as the new "Script > Scripts..." menu entry in scribus 1.7.

i would use the same preferences settings for detecting the directories with the script and place some sort of manifest in there, that defines the script one wants to attach to a directory.

the alternative, would be a more complex preferences dialog, where one could add and define each button...

[abi]

To give a quick update on this ticket - what we have noticed is that scribus does not allow running multiple scripts simultanously

1st script - the plugin that we have created
2nd script - is loading Content Properties

If we dont close the Plugin, Content Properties stays locked. But closing the Plugin and loading it again from scripts is not a very user friendly solution. If anyone can suggest a work around for

1. How can we close the script by minimising or something like that
OR
2. A quicker way to load the Plugin using some keyboard shortcut or adding it in the menu toolbar icon

Thanks

[AdmFubar]

I wonder, are the "content properties" locked because the "content properties" window is open? "content properties" window is waiting for user input at all times while open and locking out scripts as it may cause a conflict?

try the script with the "content properties" window closed.

Not sure this is the solution. just speculation on mypart

[abi]

The plugin has an add button which reads text from a CMS via API and loads on the page, once the text block is loaded, we can right click on it and load Content Properties.

Since our plugin is also running and simultanously we try and open "Content Properties" it shows as locked. If we close the Plugin, immediately the "Content Properties" are unlocked and we can modify font and other options from content properties

[a.l.e]

in the bug tracker, martin mentioned his plans to create a customizable toolbar.

i've shortly summarized it in this new ticket:

https://bugs.scribus.net/view.php?id=17366

i think that it's the simplest way to solve your issue.

if your company has (c++) developer resources to spend on this, you might want to get involved in the discussion and see how the new toolbar can be developed so that it you get to use it as soon as needed in your setup.