
	Where results make sense

Topic: Interface pattern

Related Topics

Fundamental pattern

Behavioral pattern

Structural pattern

Design pattern (computer science)

Creational pattern

Software design pattern

Concurrency pattern

Scheduler pattern

Proxy pattern

Bridge pattern

Marker interface pattern

Adapter pattern

Delegation pattern

Factory method pattern

Immutable pattern

	Interface pattern - Wikipedia, the free encyclopedia
		In computer science, the interface pattern isn't a specific pattern amongst design patterns.
		In general, an interface is a class which provides the programmer with a simpler or more program-specific way of accessing other classes.
		Other kinds of interface patterns are: delegation pattern, composite pattern, and bridge pattern.
	en.wikipedia.org /wiki/Interface_pattern (93 words)

	Marker interface pattern - Wikipedia, the free encyclopedia
		This pattern allows a class to implement a marker interface, which exposes some underlying semantic property of the class that cannot be determined solely by the class' methods.
		Whereas a typical interface specifies functionality (in the form of method declarations) that an implementing class must support, a marker interface need not do so.
		interface, as it indicates that the cloning functionality is actually supported in a proper manner.
	en.wikipedia.org /wiki/Marker_interface_pattern (382 words)

	Design Pattern Synopses
		The Filter pattern is a special case of the Decorator pattern, where a data source or data sink object is wrapped to add logic to the handling of a data stream.
		The Composite pattern also allows the objects in the tree to be manipulated in a consistent manner, by requiring all of the objects in the tree to have a common superclass or interface.
		The Interface pattern can be used with the Façade pattern to allow different sets of façade and implementation classes to be used without client classes having to be aware of the different classes.
	www.mindspring.com /~mgrand/pattern_synopses.htm (4381 words)

	Testing Interfaces (Site not responding. Last check: 2007-09-20)
		Interfaces and Abstract Classes are language constructs that appear over and over in many design patterns and even just in good design techniques.
		Once the interface or abstract class is specified, we need to write a JUnit test case that will test the functional compliance of any class that implements this interface.
		Since the pattern indicates that we should create a Concrete Test class for every implementation of the interface, there is a strong likelyhood that we will end up with a proliferation of Concrete Tests.
	www.placebosoft.com /abstract-test.html (1838 words)

	Unix Interface Design Patterns (Site not responding. Last check: 2007-09-20)
		The term “compiler-like interface” for this pattern is well-understood in the Unix community.
		Some other interface tropes associated with this pattern include: (a) the use of one-item-per-line menus, with the currently-selected item indicated by bold or reverse-video highlighting, and (b) ‘mode lines’ — program status summaries carried on a highlighted screen line, often near the bottom or at the top of the screen.
		As a result, a traditional but now archaic part of the roguelike pattern is the use of the h, j, k, and l as cursor keys whenever they are not being interpreted as self-inserting characters in an edit window; invariably k is up, j is down, h is left, and l is right.
	www.catb.org /~esr/writings/taoup/html/ch11s06.html (5191 words)

	Experiences -- A Pattern Language for User Interface Design
		The computer interface can be an unfamiliar and unnatural thing, but a well designed interface will minimize the gap between a user's goals and the knowledge required to use the interface.
		Users want a consistent interface that is always present and easy to reach, an interface they can use to instruct the application to do their bidding.
		An interface with a series of pushbuttons, which are labeled F1 through F8, is an example of a very literal translation of a hardware solution, but is not as helpful or friendly as it could be.
	www.maplefish.com /todd/papers/experiences/Experiences.html (5117 words)

	Design Pattern Synopses from Patterns in Java, Volume 1 Second Edition
		The Marker Interface pattern uses the fact that a class implements an interface to indicate semantic boolean attribute of the class.
		The Decorator pattern extends the functionality of an object in a way that is transparent to its clients, by implementing the same interface as the original class and delegating operations to the original class.
		The Guarded Suspension pattern is used in the implementation of the Double Buffering pattern to coordinate the actions of data-requesting threads with the read-ahead thread.
	markgrand.com /pattern_synopses1_2ed.html (5418 words)

	Functioning Form - Interface Design Pattern Levels (Site not responding. Last check: 2007-09-20)
		At the application level, Microsoft has identified a set of archetypes: "something that serves as the model or pattern for other things of the same type.” The Aero User Experience Guidelines briefly outline eight application patterns from document editor applications to information/reference applications that are meant to serve as adaptable guidelines or design inspiration.
		Function level patterns are widely documented and combine interface elements (input fields, buttons, text, etc.) to enable actions such as Login and Search.
		Though higher and lower level patterns may exist (for instance, application suites) function, module, and application level patterns are common enough to provide a substantial return on investment for those who take the time to document and utilize them.
	www.lukew.com /ff/entry.asp?79 (284 words)

	SAP Design Guild -- User Interface Patterns - Components for User Interfaces
		Pattern elements themselves can be combined into even more complex components, the user interface patterns.
		A pattern such as this may consist of a search area, various function buttons in a tool bar, and a collection area for the hit list.
		The approach of configuring user interfaces with user interface patterns only works if there are a small number of "generic" tasks, which can describe very many different business activities.
	www.sapdesignguild.org /editions/edition8/patterns.asp (2160 words)

	Software Pattern Synopses
		The Explorable Interface pattern is often used with the Conversational Text pattern.
		The Explorable Interface pattern is often used with the Form pattern.
		The Explorable Interface pattern is often used with the Supplementary Window pattern.
	www.mindspring.com /~mgrand/pattern_synopses2.htm (4236 words)

	Transformation Interface
		Consequently, this paper focuses on how the Transformation Interface pattern resolves the forces that appear in the context of implementing such a three-tiered architecture, rather than discussing too much the nature of the transformation interface itself, or in studying examples of all its incarnations.
		The Transformation Interface is a simpler pattern, with less classes required to implement it – though the pattern does require that the transformation methods be re-implemented for each new format.
		The Transformation Interface pattern encourages the transformational method code to be customising to the transformational task at hand, which may involve things like taking object attributes and storing them in GUI widget attributes or even may involve special calculations and drawings onto a graphic canvas area.
	www.atug.com /andypatterns/TI.htm (4676 words)

	Automated Dress Pattern in Interface Age Magazine 1978
		We took the Dress pattern and layed it on a large sheet of 132 Column printer pager.
		We then found the x and y grid point of the pattern and designed a program to load the x,y data and print it on a a 132 column printer.
		Interface Age evolved out of the club newsletter for the Southern California Computer Society: SCCS Interface.
	www.artsci.net /bill/interface-age (212 words)

	The Case for HCI Design Patterns
		Look at an interface you like, and see if what you like about it can be captured by some of these patterns -- keep in mind that a pattern language can serve not only as rules for building a design, but also as a system for deconstructing an artifact and classifying its pieces.
		This pattern is unusual in that the artifact is merely a mediator between people, not a direct participant in a dialogue with the user, nor a passive provider of content.
		Patterns that tend to use this a lot are interactive ones with a heavy visual component, including Navigable Spaces, WYSIWYG Editor, and Form (particularly for controls like Forgiving Text Entry and Editable Collection).
	www.mit.edu /~jtidwell/common_ground_onefile.html (16317 words)

	User Interface
		Interfaces that force you to jump back and forth between different style of interaction (text editing to form fill out to tabular presentation to direct manipulation) violate this sense of easy flow.
		One of the marks of a good interface is that everyone feels like they can work the way they want to, that the system does not impose any particular method of solving a problem.
		Interface design tends to fall into one of two camps- the "everything in one window" camp and the "everything in separate windows" camp.
	c2.com /ppr/ui.html (1035 words)

	Yahoo! Makes User Interface Pattern Libraries Public \| davidsturtz.com
		This is an excellent resource not only for useful patterns and code, but also as insight into the reasoning behind user interface choices and a great example of how to document design patterns.
		Case Study, in which Yahoo!’s user interface designers explain how they developed and operate their pattern library.
		That article is a great overview of what patterns are, and provides some good methods for creating your own pattern library.
	www.davidsturtz.com /weblog/archives/000389.php (214 words)

	read-only interface concept from the Object Oriented Software Engineering knowledge base (Site not responding. Last check: 2007-09-20)
		has definition A pattern in which an interface is used to restrict which classes have privileges to call update methods of a class
		All classes that need to modify the class, often called «Mutator» classes, must be put in this package.
		Then create a public interface we will call the «ReadOnlyInterface», that has only the read-only operations of «Mutable» - i.e.
	www.site.uottawa.ca:4321 /oose/read-onlyinterface.html (320 words)

Try your search on: Qwika (all wikis)