More serious (to some) than the hassle, is the obvious roadblock the templates cause with ever using the App Store for plugins. Maybe there are harder problems too (e.g. does the plugin app currently work if it’s sandboxed?) Back to the original question, I found it works well to put the whole template under version control. Git works well so it doesn’t have all those .svn folders in each subfolder. Move the new template into your source code hierarchy and then revert all the PNG files at once.
On Mar 4, 2015, at 10:13 AM, Christoph Vonrhein <chv@chv-electronics.de> wrote:
On Mar 4, 2015, at 1:07 PM, Paul Miller wrote:
On 3/4/2015 12:07 PM, Peter Litwinowicz wrote:
Yes, and I guess I’m asking why that needs to be the case (what I’m told to do is exactly what I said I’m already doing. ).
Makes workflow very tedious.
The whole template process is very tedious. The most time consuming part of my releases in fact.
...which brings us back to the many years old request that FCP X should be capable to load FxPlug plugins directly without the use of restricting templates. This would solve a variety of problems instantly.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarch...
This email sent to garrick@digitalanarchy.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com