Thomas, Please file a bug about the documentation for this component. I know that some documents we use internally will have change markers on them. It might be possible to do the same for public documentation. (I don't know for sure, but it seems like it might be.) But without a bug, nobody will work on it, so please file one! Darrin On Dec 4, 2012, at 11:51 AM, Thomas - Mindtransplant <thomas@mindtransplant.com> wrote:
Hi all,
I hope Apple reads this message too.
It would be really nice for us developers to have some type of "Changes Log" which gives us a detailed description about the changes made in fcpxml 1.2. I´m aware of the Notes in the fcpxml 1.2 documentation but it´s tedious to scroll through the whole PDF to find these Notes (and further changes not mentioned in Notes). By accident I noticed some new attributes here and there which mess up the parsing process in my app. I only came across these changes because some beta testers reported bugs about features behaving strange and in my opinion this is a "no-go" and much too late!
Why is this so annoying? The review process in the Mac App Store currently takes 20+ days. 10 days passed since I´ve submitted an update (which makes my app 10.0.6 compatible) when a tester reported a bug that was related to the new "rateConform" attribute in the <timeMap> Node (not mentioned in any kind of Note but has it´s own paragraph). As a result I had to "developer-reject" my app, bugfix it, submit it to the Mac App Store and start from zero with waiting for getting reviewed in 20+ days. That´s a lot of time for the customers to wait for an update!
Ok, some might say: rtfm. Well, I´ve completely read the docs for version 1.1. I have a basic understanding what´s going on. Do I have to read the docs from front to back again (40-50 pages) and compare it with the prior version just to make sure not having missed a new attribute or a new node?
So please Apple, give us some type of changes log or some kind of overview from where we start and make our way to the detailed description in the docs. Thanks.
Thomas _______________________________________________ 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/dcardani%40apple.com
This email sent to dcardani@apple.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