Flash: Interface
May 6th, 2005 by LuisThis is probably one of the best articles about the definition and use of Interface in OOP written by a non-professional programmer.
Pages
Archives
- March 2012
- February 2012
- December 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- March 2011
- December 2010
- November 2010
- October 2010
- September 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- December 2008
- November 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
Categories
- apps (2)
- Barcelona (1)
- Better things to do (88)
- blackberry (0)
- children (0)
- Design (111)
- General (59)
- Installation (16)
- Motion (22)
- Print (10)
- Director and Lingo (5)
- education (0)
- Events (9)
- Flash (205)
- Gaming (43)
- General (423)
- HTML (14)
- Cross-browser (10)
- Design (0)
- Learnings (1)
- Japan (13)
- Java (1)
- Hibernate (1)
- Javascript (3)
- Ajax (3)
- land of me (0)
- PHP (2)
- playbook (0)
- Social Networking (2)
- Software (15)
- test (0)
-
-
-
Joblet
May 8th, 2005 at 7:20 pm
Actually the example he gives would be more one for abstract classes which Flash doesn’t provide, but that’s another issue… Interfaces are mainly good to let completely different classes that don’t have a common ancestor act in a similar way. A book and a bar of chocolate are completely different things, but they’re both “Buyable”. To be a valid “Buyable” item, you need to define a couple of common properties, e.g. getPrice().
See also Java-Docs on abstract classes and interfaces (not java specific, common OOP theory):
http://java.sun.com/docs/books/tutorial/java/concepts/interface.html
http://java.sun.com/docs/books/tutorial/java/javaOO/abstract.html
May 9th, 2005 at 11:09 am
Abstract Class in AS2.0
http://www.actionscripts.org/tutorials/advanced/AbstractClassin_AS2/index.shtml
http://www.design-nation.net/en/archives/000411.php