Comments on: What Is Interface?

By: How Interface Helped Me | iface thoughts

How Interface Helped Me | iface thoughts — Sat, 06 Oct 2007 06:57:18 +0000

[...] I cannot deny that it gave me a chance to improve my designing ability. It is not the keyword, but the concept of an interface that helped me. To an extent that it has been my channel of thinking for understanding newer [...]

By: vikram

vikram — Sat, 21 Jul 2007 11:57:13 +0000

Very beautifully explained. really very very helpful

By: Abhijit Nadgouda

Abhijit Nadgouda — Fri, 29 Jun 2007 06:13:24 +0000

Thanks Sonali.

By: sonali

sonali — Thu, 28 Jun 2007 11:57:09 +0000

great observation and relation to real life mate…
very simple n clear to me now…
thnx n keep it up…

By: More On Interface on iface thoughts

More On Interface on iface thoughts — Wed, 27 Dec 2006 18:12:51 +0000

[...] One of my favorite authors has written on one of my favorite topics. Martin talks about role interface and header interface. A header interface is an explicit interface that mimics the implicit public interface of a class. Essentially you take all the public methods of a class and declare them in an interface. You can then supply an alternative implementation for the class. [...]

By: OOP In Procedural Programming on iface thoughts

OOP In Procedural Programming on iface thoughts — Sat, 02 Dec 2006 04:15:41 +0000

[...] The key is that the interface abstraction is designed using the hook system. Node is the abstraction for any content type. The core of Drupal system uses these abstractions and is hence able to handle any extended content types without code modification. The use of node_invoke() to invoke any node hook. This means that the interface for communication with any node is designed using this abstraction. Node and hook system together enable Drupal to comply with Open-Closed Principle. [...]

By: Code Quality As An Asset on iface thoughts

Code Quality As An Asset on iface thoughts — Fri, 24 Nov 2006 04:43:15 +0000

[...] Another reason that I have seen is inability to identify dependencies between various modules, components, or subsystems while developing. If module B depends on module A then A has to be ready before A can be developed. However, this linear development is not practical. What is required is to decide the communication between A and B, decide what A and B expect from each other or design their interface. Unless this is done it more than just probable that more time will be spent in redoing or rewriting code – one of the biggest hurdles in productivity. Identifying dependencies and designing interfaces is something that can help parallel development without having to rewrite. [...]

By: Abstraction, Indirection, Simplification And Encapsulation on iface thoughts

Abstraction, Indirection, Simplification And Encapsulation on iface thoughts — Fri, 17 Nov 2006 05:52:47 +0000

[...] Abstraction is not data-hiding, it can be considered as a byproduct of separating what and how. Encapsulation is data hiding, but hiding only the unnecessary data. The user needs to know only the specifications to be able to use something. Which is where the significance of interface comes in. [...]

By: Interface Segregation Principle on iface thoughts

Interface Segregation Principle on iface thoughts — Mon, 13 Nov 2006 13:02:51 +0000

[...] All the basic design principles converge on the use of abstraction for incorporating flexibility using loose coupling behaviour. Interface Segregation Principle (ISP) is a guideline for designing different interfaces. [...]

By: Open-Closed Principle on iface thoughts

Open-Closed Principle on iface thoughts — Mon, 13 Nov 2006 12:58:46 +0000

[...] The answer, again, is abstraction. Abstraction enables you to have an interface which separates the intent from the implementation, or the what from the how. This opens possibilities for multiple hows for the same what. [...]