I’ve been using Interfaces a couples of time now when needed but I never fully understood those down-sized Class construct wannabes. I knew they are useful when it is required to have an universal type for different objects but I haven’t fully grasped to scope why they are so useful otherwise. Also the fact that they can’t contain properties and only public method declarations confused me.
[ad#ad_content]This has changed instantly today when I read a sample eBook chapter of Joey Lott’s Advanced ActionScript 3 with Design Patterns on Adobe Labs new Digital Editions Service , a book that I actually ordered already a couple of days ago (takes a bit to ship to Japan though).
What can I say? This small chapter explains it extremely easy and logically. I’ve read EAS 2.0 and Head First but this sample chapter made me getting it for the first time really! It also explains about the difference of Abstract Classes and Interfaces, something that has not been mentioned in any other ActionScript book I’ve read so far.
Full respect to the author! If the rest of the book is of similar quality and clarity I shall be damned if I will not be an OOP Pattern Master in near future!
On a side note, the sample books are being downloaded of what looks like an Apollo app. I’m not sure how far this is related to Apollo but it works like a standalone eBook reader is downloaded and installed and sample chapters open in it.
