Sullyman Posted December 29, 2017 Posted December 29, 2017 Quick question.... Is there a way you can make your macros un-editable? Let say in the case of wanting to sell them without giving away your magic sauce? Quote My portfolio | Youtube Channel: Pixel Moshpit | Email: john@johndrawsfor.me
v_kyr Posted December 29, 2017 Posted December 29, 2017 How should that work for a sequence of recorded and stored actions, which in turn must be able to be reloaded, possibly edited and reinterpreted again? - AFAIK there is nothing like a macro compiler or sort of an obfuscator for such things, at least not in AP. Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
walt.farrell Posted December 30, 2017 Posted December 30, 2017 I suspect that to truly hide one's magic sauce one would want to implement and distribute a plugin, rather than a macro. Paul Mudditt 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.2.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
v_kyr Posted December 30, 2017 Posted December 30, 2017 That's right, plugins would offer this and could also have their own license manager etc. incorporated. Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Sullyman Posted December 30, 2017 Author Posted December 30, 2017 For me it just seems overkill to have to code a plugin and have to then involve license management, keeping in mind I'm a designer first and very limited coder/non-programmer. Being able to tick an option to keep macro's editable or not, in theory, seems a much more simple route. But then again, what do I know, it could be massive work on their end Quote My portfolio | Youtube Channel: Pixel Moshpit | Email: john@johndrawsfor.me
Sullyman Posted December 30, 2017 Author Posted December 30, 2017 Also, where would one go to look into programming a plugin for Affinity? Any know where to start? Quote My portfolio | Youtube Channel: Pixel Moshpit | Email: john@johndrawsfor.me
walt.farrell Posted December 30, 2017 Posted December 30, 2017 6 hours ago, Sullyman said: Also, where would one go to look into programming a plugin for Affinity? Any know where to start? AP seems to support one of the Photoshop plugin formats, so I would start by looking for PS documentation for that format. Or, possibly, GIMP documentation. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.2.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
v_kyr Posted December 30, 2017 Posted December 30, 2017 7 hours ago, Sullyman said: For me it just seems overkill to have to code a plugin and have to then involve license management, keeping in mind I'm a designer first and very limited coder/non-programmer. Being able to tick an option to keep macro's editable or not, in theory, seems a much more simple route. But then again, what do I know, it could be massive work on their end Well that's usually why such apps have or do offer macros or even better a sort of scripting API access, since those are overall easier to deal with for non programmers/developers. However the problem there with macros and scripts would be how to hide their implementation steps. As a designer you for sure know the Adobe apps which do offer action recording (ATN files) and JS like scripting engine capabilities here. But there too (in the Adobe world) it's difficult to hide those things from being altered at all! Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
v_kyr Posted December 30, 2017 Posted December 30, 2017 7 hours ago, Sullyman said: Also, where would one go to look into programming a plugin for Affinity? Any know where to start? Good question! - Affinity itself doesn't offer here any public informations or samples how to make correct use of the Adobe PS API and which Win/Mac versions of those best to use. So it might be more or less try & error here, meaning you have to find out by yourself! Quote ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.