Re: FxPlug versioning
Re: FxPlug versioning
- Subject: Re: FxPlug versioning
- From: Martin Baker <email@hidden>
- Date: Fri, 29 Mar 2013 12:15:20 +0000
| While I can appreciate Apple's philosophy on wanting to keep FCP streamlined, in the real world this throws up a ton of issues for third party developers and isn't a workable proposition for many products.
1. Customers buy plug-ins based on what can be achieved. It significantly complicates the sales proposition to say that they get X feature as standard, but have to do more work to get Y feature. 2. Requiring customers to have Motion installed to "unlock" the full power of a third party plug-in adds another layer of complication. 3. Customers want convenience and they would inevitably ask "Why do I have to spend time manually modifying the Motion template to get access to all the parameters? Feels like an unfinished product." 3. The increased customer support burden for all of the above, which would be significant.
Even having the ability to publish parameter groups would go a long way to improving the UI usability of FxPlugs in FCP.
Martin ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396
Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE
VAT registration number: GB 736 0989 03
On 28 Mar 2013, at 16:56, Darrin Cardani wrote: Also, the idea with templates is that they will not just contain a copy of every parameter in every plug-in, but that developers will think through specific tasks that users need to perform and will provide templates for those tasks rather than raw plug-ins with dozens of parameters that most users won't understand. |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden