
	Where results make sense

Topic: Interface bloat

Related Topics

Abstraction inversion

God object

Gas factory

Accidental complexity

Accumulate and fire

Design by committee

Lava flow (programming)

Big ball of mud

Continuous obsolescence

Voodoo programming

Magic (disambiguation)

CORBA

Black magic (programming)

VLSI

Deep magic

In the News (Sat 19 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Interface bloat - Wikipedia, the free encyclopedia
		In software design, interface bloat (also fat interfaces) is a term used to describe interfaces that try to incorporate all possible operations on some data into an interface, only to find that most of the objects cannot perform the given operations.
		One might consider using visitor pattern, interface separation instead.
		Interface bloat is an example of an anti-pattern.
	en.wikipedia.org /wiki/Interface_bloat (90 words)

	GEO World - Oct 2002 - Edge Nodes: How Can We Combat Application Erosion and Bloatware? (Site not responding. Last check: 2007-10-22)
		Concerns about bloatware include a steeper learning curve for neophytes, new interfaces for existing customers to learn and the recently recognized problem of application erosion, which can be defined as a steady decline in a system's used functionality.
		Bloat was assessed quantitatively by counting first-order functions (there were 265) and determining whether a significant portion was unused.
		McGrenere's study concluded that there was objective bloat (functions unused by almost every user) and subjective bloat (functions used only by certain subsets of users) in which one person's bloat is another's favorite function.
	www.geoplace.com /gw/2002/0210/0210ends.asp (1213 words)

	MacAddict Forums / Bloat vs. Features
		Bloat is not necessarily features, it is unnecessary repetition of program attributes, or poor placement of features.
		iChat's speech balloon interface would equate to bloat, because the repetition of the person's icon for every message sent is completely superfluous compared to AIM's constant and singular placement at the top of the window.
		Good bloat, is stuff like the way it looks (as long as it doesn't make it run slow, but ichat does not run slow on my 1ghz powerbook), as well as features that might not be useful to everybody, or you specifically, but useful to the majority of people.
	www.macaddict.com /forums/post/776356 (705 words)

	Abdominal Pain And Bloating -- Recommendations and Resources (Site not responding. Last check: 2007-10-22)
		For the symptom in humans, see Gas/bloat syndrome, flatulence, and burping.'' Bloat, also known as torsion, gastric torsion, and gastric dilatation-volvulus (GDV) is a medical condition in which the stomach becomes overstretched by excessive gas content.
		In dogs, the causes of bloat are unclear, and currently there is little agreement on the factors that may contribute.
		Software bloat is a derogatory term used to describe the tendency of newer computer programs to use larger amounts of disk space, more CPU power and/or more RAM than older programs.
	www.becomingapediatrician.com /health/0/abdominal-pain-and-bloating.html (1450 words)

	SIGCHI Bulletin Vol.30 No.4, October 1998: Too Much of a Good Thing?
		Blame for this bloat in the interface layout and controls is usually attributed to a steady increase in the functions and features built into each new version of software products.
		Bloat arises when the user expects the task to be simple and the device for doing the task is unnecessarily complicated.
		We concluded that even with these criteria for identifying bloat in the interface, software with a lot of features is not inherently bad, hard to use, poorly designed, or bloated.
	homepages.cwi.nl /~steven/sigchi/bulletin/1998.4/kaufman.html (1498 words)

	Object Oriented Programming Criticism - Part 2
		In this case these interfaces include "income", "filing", and "dependants".
		The reply was that he was creating an interface to a database entity, so that the programmer did not have to deal with the "raw" table and SQL data.
		Thus, he was essentially creating an interface to an interface.
	www.geocities.com /tablizer/miscoop.htm (6970 words)

	Cyrus' Blather : How do you decide what goes in an interface?
		Then offer other interfaces, possibly derivative, in case someone decides, for example, that there is a better way to count the elements in an array than by using enumeration and iteration (duh).
		But we must be clear that these other interfaces are for specialization (maybe hide them on the class as with IConvertible), otherwise users will demand to see them everywhere, and we'll end up with interface bloat yet again.
		Or, you often see interfaces that inherit from other interfaces for no sound reason besides convenience, like IDataReader, which is interface bloat again.
	blogs.msdn.com /cyrusn/archive/2004/06/20/160347.aspx (2270 words)

	Colt 1.0.3 - API Specification: Package cern.colt.matrix (Site not responding. Last check: 2007-10-22)
		Interface that represents a condition or procedure object: takes a single argument and returns a boolean value.
		To avoid interface bloat, it can be a good idea to separate algorithms from data structures.
		By using the common interfaces defined in abstract classes, algorithms can be implemented such that they generically work both on sparse and dense matrices and all their views.
	hoschek.home.cern.ch /hoschek/colt/V1.0.3/doc/cern/colt/matrix/package-summary.html (2509 words)

	QuEP 7: using the Visitor pattern to avoid interface bloat
		It has been argued [1] that functionalities that can be implemented by means of the public interface of a class should be made available as a non-friend, non-member function rather than another method of the class.
		This actually improves encapsulation since this enlarged class interface (meant as the set of the class methods and the additional non-member functions) is thus made less dependent on the class internals.
		However, there are situations where this simple approach would not be convenient, either because knowledge of the exact type of the instance is actually needed, or because it would prevent the developer from applying useful optimizations depending on the instance type.
	quantlib.org /quep/quep007.html (990 words)

	Features of Mozilla Firefox - Wikipedia, the free encyclopedia
		This means that the user interface is clean and uncluttered upon initial installation of the browser.
		Firefox's toolbars and interface are customizable; users can move and manipulate the various buttons, fields, and menus on the toolbars, and also add new toolbars or delete existing ones.
		Firefox and Internet Explorer both employ graphical user interfaces (GUIs), and in both cases there is the risk that a user may be fooled by misunderstanding the interface or the displayed information in a way that puts them at risk (this is a general risk of GUI-based web browsers).
	en.wikipedia.org /wiki/Features_of_Mozilla_Firefox (3662 words)

	[No title]
		This interface has no editor-specific functionality; it could just as well be called the ``FileManipulator'' interface and be used by a spreadsheet.
		The flip side of this, of course, is that implementation inheritance in CORBA is not standardized, normally requiring the object implementor to re-implement all the operations on an object.
		Not only does exposing low-level interfaces cause increased dependence upon the internal organization of a software system, but it also means you have to put more code into exporting your interfaces, introducing the risk for more bugs and increasing bloat.
	www.redhat.com /support/wpapers/redhat/ORBit/corba-you.html (1074 words)

	Document Object Model FAQ
		A similar interface to XSL stylesheets may be specified later on, perhaps not by the DOM WG.
		Interfaces are widely used in many object-oriented languages, for example Java, and have several advantages when designing an API.
		Adding new methods to existing interfaces where appropriate does not work in all languages, but those languages which need a different way of doing things are expressly allowed to do so by the DOM specification.
	www.jalix.org /ressources/internet/dom/~vrac/w3c-faq.html (3649 words)

	Jensen Harris: An Office User Interface Blog : Combating the Perception of Bloat (Why the UI, Part 3)
		Office 2000 introduced several new UI mechanisms designed to reduce this perception of "bloat." In many ways, this release marks the beginning of the road that eventually turns towards the redesign of the UI in Office 2007.
		The other new mechanism in Office 2000 designed to reduce the perception of bloat was "rafted toolbars." In this design, two or more toolbars could share a line on the screen.
		Office was known at the time for being very conservative about the user interface; as I discussed last time, until Office 2007, the top-level menu structure of Word hasn't changed since 1989.
	blogs.msdn.com /jensenh/archive/2006/03/31/565877.aspx (1813 words)

	Asa Dotzler - Firefox and more: on bloat and opera
		XUL is bloated, Gecko is bloated, Firefox is bloated.
		But bloat in the sense that Opera has too many features not needed by most users, and by that clutter up the user-interface too the point where it makes it more difficult to use (especially for the non-tech users just wanting to browse the web).
		The 'bloat' that remains seems to be the subjective bloat, or as I would call it the 'between the ears'-notion of the mail/news/chat client in the background, which you can't see.
	weblogs.mozillazine.org /asa/archives/008014.html (3906 words)

	Usability In The News: Combating the Perception of Bloat (Why the UI, Part 3)Usability In The News (Site not responding. Last check: 2007-10-22)
		All this new functionality came at a cost, however, and part of this cost was increased complexity in the user interface, mainly through the addition of new menu items and toolbar buttons.
		What had happened, however, was that the user interface had begun to feel bloated.
		Office 2000 introduced several new UI mechanisms designed to reduce this perception of "bloat." In many ways, this release marks the beginning of the road that eventually turns towards the redesign of the UI in Office 2007." continued...
	usernomics.com /news/2006/03/combating-perception-of-bloat-why-ui.html (353 words)

	Using the SAX Interface of LibXML
		This is generally quite an easy interface to use, but can use quite a bit of memory.
		An alternative is to use the SAX interface in libxml, which is a port of the Simple API for XML library for Java.
		If you keep with the DOM interface, your program will probably use a bit more memory, but it has the advantage that you can modify the tree, and then write the XML file back to disk with a single function call.
	developer.gnome.org /doc/tutorials/xml-sax/xml-sax.html (1361 words)

	Jensen Harris: An Office User Interface Blog : Combating the Perception of Bloat (Why the UI, Part 3)
		Office 2000 introduced several new UI mechanisms designed to reduce this perception of "bloat." In many ways, this release marks the beginning of the road that eventually turns towards the redesign of the UI in Office 12.
		Office was known at the time for being very conservative about the user interface; as I discussed last time, until Office 12, the top-level menu structure of Word hasn't changed since 1989.
		I think the reason why Office got the bloat name was, the displays were still small and the resolutions were 800*600 Office was adding more features, and with personalized menus Office 2k, it was just apparent that Office seemed like it had a bit too much.
	blogs.msdn.com /jensenh/archive/2005/10/10/479123.aspx (3021 words)

	[No title]
		This extends the flbox interface and provides facilities for some direct methods and block methods (dense matrices in lieu of vectors as arguments to fl box apply).
		LinBox::FieldArchetype in linbox/field/archetype.h specifies this interface in detail and sets it up in such a way that algorithms can be compiled once against the field archetype.
		This is simply the std::vector interface, where Elt is the element type of the field involved.
	www.eecis.udel.edu /~linbox/doc/html/archetypes.html (617 words)

	CS 485: Software Bloat (Site not responding. Last check: 2007-10-22)
		The future of Software Bloat is that its only an issue for poorly designed software applications.
		Size Bloat is a non-issue as long as advances in storage technologies continue their increase at the rate that they have been at for the last thirty-odd years.
		Microsoft Office 12 is now paving the way with a new style of interface that may replace a menu-driven style for applications that just have too much functionality.
	www.iit.edu /~popeale1/future.html (169 words)

	Mac News: Strategy: Interface Burdens and Mac Usability
		In other words, that Windows interface barrier is completely missing in the Apple world because the Mac OS transparently hosts the applications without imposing itself on the user's attention.
		One immediate corollary to the hypothesis that intrusive interfaces affect how we understand the work to be done is that the design assumptions in a tool that dominates a profession should eventually be reflected in nearly all the work done by the people using it.
		In theory, the thing was to be a connected series of alternating embarkation and arrival halls with each pair laid out in a crescent to interface parking space for super jumbos on the inside to passenger ground transportation on the outside.
	www.macnewsworld.com /story/34066.html (1473 words)

	Using the SAX Interface of LibXML
		The libxml library provides two interfaces to the parser: a DOM style tree interface, and a SAX style event based interface.
		Most users of the library choose the DOM interface due to its ease of use, however it does have a few drawbacks.
		In contrast, the SAX interface does not maintain the entire DOM tree in memory, which means that it can be quite efficient for large documents.
	www.jamesh.id.au /articles/libxml-sax/libxml-sax.html (2478 words)

	Hub: A Roadmap for a Shareable Runtime (Site not responding. Last check: 2007-10-22)
		There must be interfaces or conventions for the clients of the runtime to coordinate use of operating system resources such as threads and file descriptors.
		With a properly constructed runtime based on binary interfaces between compiled code, it is, in fact, possible to hook in a virtual machine which handles code that can't be run natively; for instance, to handle sandboxed/untrusted code, or dynamically loaded classes.
		Even with C++, you could avoid the unportable assembly code by generating static stubs for each interface; the bloat penalty for this is fairly substantial, but this bridge could be provided as a portable fallback.
	people.redhat.com /~hp/runtime-roadmap/runtime-roadmap.html (8287 words)

	: Index
		Adds an interface of the given class to the set of interfaces that the class implements.
		Adds an interface of a given Type to the set of interfaces that the class implements.
		Contains classes that are used to run benchmarks that measure the performance of BLOATed code.
	www.cs.arizona.edu /~collberg/Research/bloat/index-all.html (2347 words)

	Usability In The News: My not-so-invisible enemy - Page bloat is the visible culprit behind long load timesUsability In ... (Site not responding. Last check: 2007-10-22)
		My not-so-invisible enemy - Page bloat is the visible culprit behind long load times
		"Page bloat is so common most users don't even wonder anymore why their favorite Web sites take so long to load; they just wait it out.
		Conveniently, my cell phone is equipped with a fairly useful Web browser capable of downloading data at just over 10 kilobits per second.
	usernomics.com /news/2005/07/my-not-so-invisible-enemy-page-bloat.html (363 words)

	Microsoft: Office 2007 Addresses Bloat Issue
		Microsoft has been studying the problem of bloat for the past eight years and has done extensive usability testing over this time, with 1.2 billion data sessions collected.
		Alexieff also acknowledged that there were a lot of concerns about the new user interface, such as whether it actually worked, how much and what type of training was required, and how the help desk would be impacted during the transition.
		A majority of survey participants also predicted increased productivity once they became accustomed to the new user interface, with the majority of those in the study saying they expected to be back up to speed within one to four weeks.
	www.eweek.com /article2/0,1759,1975590,00.asp (1192 words)

	EditPad Lite Free Download-Convenient basic text editor
		Snapper reads the directory of a disk which is then saved as a "snapshot", so that later you can compare it with a new snapshot of the disk and see what has changed.
		The results are easy to see with colour highlighting in an Explorer-style interface.
		SOCKShell expands and enhances the Windows Explorer context menu by adding a number of new predefined options and allowing you to add any number of your own options, both to the main context menu and to the SOCKShell submenu.
	www.justdosoft.com /EditPad-Lite-14613.html (580 words)

	Mozilla Firefox (Site not responding. Last check: 2007-10-22)
		In October 2003, professional interface designer Steven Garrity wrote a web page review of everything he considered to be wrong with Mozilla's visual identity.
		One notable exception is the XUL spoofing vulnerability that was found in 1999, marked confidential in the Mozilla bugtracker until July 21, 2004, and fixed finally before the first official release of the product for end-users (the 1.0 release).
		http://www.kb.cert.org/vuls/id/713878 Firefox and Internet Explorer both employ graphical user interfaces (GUIs), and in both cases there is the risk that a user may be fooled by misunderstanding the interface or the displayed information in a way that puts them at risk (this is a general risk of GUI-based web browsers).
	www.33beat.com /Mozilla_Firefox.html (8631 words)

	Cyrus' Blather : Gah! Lack of covariant return types!! aaaaaaaaaaaaargh!!!!
		I don't really see why this Transform method should be part of the interface at all, is what I am saying, just static functionality that relies on the interface.
		The reason I generally prefer the existence of a static method is because it allows the basic interface to be simpler.
		You can even change the static method to be aware of this broader interface, and return the result of calling it if the runtime type of its argument supports the IMappableCollection interface (as well as providing an overload that compile-time binds to an IMappableCollection interface.
	blogs.msdn.com /cyrusn/archive/2004/06/18/159671.aspx (3344 words)

	Joanna McGrenere's Publications
		McGrenere, J. Bloat: The objective and subject dimension.
		Identifying and Resolving Bloat in the User Interface, Los Angeles, CA.
		Moore, G., and McGrenere, J. Are we all in the same 'bloat'?.
	www.dgp.utoronto.ca /~joanna/publications.html (377 words)

Try your search on: Qwika (all wikis)