PhotoLine Forum

Hallo,

es gibt wieder eine neue Testversion 20.40b9.

Windows:
http://www.pl32.com/beta/pl2040b9.zip


Mac OS:
http://www.pl32.com/beta/plx2040b9.zip



Neues:
- wir haben damit begonnen PhotoLine "Scriptingfähigkeiten" zu spendieren.
Dazu liegen im Verzeichnis "Defaults > Automation" einige "Versuche"
Das Ganze ist noch sehr Alpha, aber uns würde interessieren, ob das überhaupt jemand haben will.

diverse kleine Fehler beseitigt

Scripting!!! That explains the silence for a while.

Downloading now. I will check this out this upcoming weekend.

Ist das ne doofe Frage: Was unterscheidet Scripting von den Aktionen in PL (bei denen auch Skripte erstellen werden)?
Und wie funktionieren die neuen Scripte?

I found the "script" menu entry, but it is empty - no submenu.

Shouldn't it be populated with the scripts in that automation folder?

Herbert123 hat geschrieben: ↑Do 01 Jun 2017 09:22 I found the "script" menu entry, but it is empty - no submenu.
Shouldn't it be populated with the scripts in that automation folder?

"Filter > Script" should be (and is here) a submenu with the examples of the automation folder.
Sorry, but I don't know if this works on macOS at the moment.

gmhofmann hat geschrieben: ↑Do 01 Jun 2017 09:09 Ist das ne doofe Frage: Was unterscheidet Scripting von den Aktionen in PL (bei denen auch Skripte erstellen werden)?
Und wie funktionieren die neuen Scripte?

Compare Photoshop's actions with its built-in scripting: if implemented with full exposure to custom user-built interface elements, we should be able to expand PhotoLine's functionality with completely new features relatively easily.

And scripting allows for FAR more control and advanced program flow than linearly recorded actions (basically, we can control the flow with considtions, loops, variables, and so on). If PhotoLine would provide the same level of scripting as Blender, for example, us users would be able to create entirely new tools and functions.

gmhofmann hat geschrieben: ↑Do 01 Jun 2017 09:09 Ist das ne doofe Frage: Was unterscheidet Scripting von den Aktionen in PL (bei denen auch Skripte erstellen werden)?
Und wie funktionieren die neuen Scripte?

Scripte sind flexibler. Hier kann man "richtig" programmieren, also z.B. alle Seiten eines Dokuments durchlaufen, auf jeder Seite die Vektorebenen suchen und deren Farbe ändern. Solche Sachen lassen sich mit Aktionen nicht realisieren.

Gerhard Huber hat geschrieben: ↑Do 01 Jun 2017 09:28

Herbert123 hat geschrieben: ↑Do 01 Jun 2017 09:22 I found the "script" menu entry, but it is empty - no submenu.
Shouldn't it be populated with the scripts in that automation folder?

"Filter > Script" should be (and is here) a submenu with the examples of the automation folder.
Sorry, but I don't know if this works on macOS at the moment.

I am on Windows, and the list shows up empty.

Herbert123 hat geschrieben: ↑Do 01 Jun 2017 09:31 I am on Windows, and the list shows up empty.

Don't know why, but you can start the scripts from the Windows Explorer, too.
The best way would be to create a script in Visual Basic inside Visual Studio.

Herbert123 hat geschrieben: ↑Do 01 Jun 2017 09:31 I am on Windows, and the list shows up empty.

Works OK here on Win10 -- all the scripts show up in the submenu.

Gerhard Huber hat geschrieben: ↑Do 01 Jun 2017 09:43 The best way would be to create a script in Visual Basic inside Visual Studio.

Would it be possible to allow creating a script in C# inside Visual Studio? (At least on Windows?)

Windows 7: das Menü bleibt leer

gmhofmann hat geschrieben: ↑Do 01 Jun 2017 12:10 Windows 7: das Menü bleibt leer

am Windows 7 kann es nicht liegen, damit habe ich auch getestet. Da muss etwas anderes Probleme machen, z.B. Umlaute oder Leerstellen im Dateipfad zu PhotoLine?

C:\Program Files\PhotoLine\Defaults\Automation

photoken hat geschrieben: ↑Do 01 Jun 2017 11:23

Gerhard Huber hat geschrieben: ↑Do 01 Jun 2017 09:43 The best way would be to create a script in Visual Basic inside Visual Studio.

Would it be possible to allow creating a script in C# inside Visual Studio? (At least on Windows?)

Yes, but technically speaking this wouldn't be a script, but a compiled application

And currently the scripting/automation interface is a moving target, so you might have to recompile your code with every new version of the interface.
But C# and VB.NET are much faster than VBScript, so it might be possible to realize more complex tasks using one them. And at least VB.NET offers things like code completion, error checks while editing and so on.

Martin