Examples of Control

• com.cosmo.ui.controls.Control
  Clase abstracta que deben implementar los controles de p�gina. @author Gerard Llort
• com.google.code.timetrail.backend.Control
  Acts as the controller for the game as it contains all the objects that make up the game (will be a singleton in the future) @author Anuraag @version 1.1
• com.google.gdata.model.atompub.Control
• com.jada.jpa.entity.Control
  Control generated by hbm2java
• com.jme3.scene.control.Control
  An interface for scene-graph controls.

  Controls are used to specify certain update and render logic for a {@link Spatial}. @author Kirill Vainer

• com.nijiko.permissions.Control
  iControl.java Permission handler @author Nijiko
• com.sardak.antform.gui.Control
  Frame for holding the user form @author Ren� Ghosh
• com.sun.star.wizards.document.Control
• de.maramuse.soundcomp.control.Control
  A control logic taking parse trees, processing them to timing information and DSP objects and organizing their execution
• de.sciss.jcollider.Control
• java.util.ResourceBundle.Control
• javafx.scene.control.Control
• javax.media.Control
  sun.com/products/java-media/jmf/2.1.1/apidocs/javax/media/Control.html" target="_blank">this class in the JMF Javadoc. Complete. @author Ken Larson
• javax.microedition.media.Control
  A Control object is used to control some media processing functions. The set of operations are usually functionally related. Thus a Control object provides a logical grouping of media processing functions.

  Controls are obtained from Controllable. The Player interface extends Controllable. Therefore a Player implementation can use the Control interface to extend its media processing functions. For example, a Player can expose a VolumeControl to allow the volume level to be set.

  Multiple Controls can be implemented by the same object. For example, an object can implement both VolumeControl and ToneControl. In this case, the object can be used for controlling both the volume and tone generation.

  The javax.microedition.media.control package specifies a set of pre-defined Controls. @see Controllable @see Player

• javax.naming.ldap.Control
  etf.org/rfc/rfc2251.txt">RFC 2251.

  The LDAPv3 protocol uses controls to send and receive additional data to affect the behavior of predefined operations. Controls can be sent along with any LDAP operation to the server. These are referred to as request controls. For example, a "sort" control can be sent with an LDAP search operation to request that the results be returned in a particular order. Solicited and unsolicited controls can also be returned with responses from the server. Such controls are referred to as response controls. For example, an LDAP server might define a special control to return change notifications.

  This interface is used to represent both request and response controls. @author Rosanna Lee @author Scott Seligman @author Vincent Ryan @see ControlFactory @since 1.3

• javax.sound.sampled.Control
• oop13.space.testing.TestCollisionsInFrame.Control
  Models an achievement of the game. @author Mattia Capucci
• org.apache.abdera.model.Control

  Represents an Atom Publishing Protocol control element.

  The purpose of the control extension is to provide a means for content publishers to embed various publishing-operation specific control parameters within the body of the entry. For instance, the client may wish to mark the entry as a draft, or may wish to ask the publishing server to enable or disable specific extended features for a given entry.

  Per APP Draft-08:

   pubControl = element pub:control { atomCommonAttributes, pubDraft? & extensionElement } pubDraft = element pub:draft { "yes" | "no" } The "pub:control" element MAY appear as a child of an "atom:entry" which is being created or updated via the Atom Publishing Protocol. The "pub:control" element, if it does appear in an entry, MUST only appear at most one time.  The "pub:control" element is considered foreign markup as defined in Section 6 of [RFC4287]. The "pub:control" element and its child elements MAY be included in Atom Feed or Entry Documents. The "pub:control" element MAY contain exactly one "pub:draft" element as defined here, and MAY contain zero or more extension elements as outlined in Section 6 of [RFC4287].  Both clients and servers MUST ignore foreign markup present in the pub:control element. 

• org.apache.beehive.controls.api.bean.Control
• org.apache.click.Control
  Provides the interface for Page controls. Controls are also referred to as components or widgets.

  When a Page request event is processed Controls may perform server side event processing through their {@link #onProcess()} method. Controls are generallyrendered in a Page by calling their toString() method.

  The Control execution sequence is illustrated below:

  

  HTML Header Imports

  Control HTML header imports can be exposed by overriding the {@link #getHtmlImports()} method.

  For example a custom TextField control specifies that the custom.js file should be included in the HTML header imports:

   public class CustomField extends TextField { protected static final String HTML_IMPORT = "<script type=\"text/javascript\" src=\"{0}/click/custom.js\"></script>\n"; public String getHtmlImports() { String[] args = { getContext().getRequest().getContextPath() }; return MessageFormat.format(HTML_IMPORTS, args); } .. } 

  Please note multiple import lines should be separated by a '\n' char, as the {@link org.apache.click.util.PageImports} will parse multiple import lineson the '\n' char and ensure that imports are not included twice.

  Deploying Resources

  The Click framework uses the Velocity Tools WebappLoader for loading templates. This avoids issues associate with using the Velocity ClasspathResourceLoader and FileResourceLoader on J2EE application servers. To make preconfigured resources (templates, stylesheets, etc.) available to web applications Click automatically deploys configured classpath resources to the /click directory at startup (existing files will not be overwritten).

  To enable Controls to deploy static resources on startup this interface provides an {@link #onDeploy(ServletContext)} method.

  Continuing our example the CustomField control deploys its custom.js file to the /click directory:

   public class CustomField extends TextField { .. public void onDeploy(ServletContext servletContext) { ClickUtils.deployFile (servletContext, "/com/mycorp/control/custom.js", "click"); } } 

  Controls using the onDeploy() method must be registered in the application WEB-INF/click.xml for them to be invoked. For example:

   <click-app> <pages package="com.mycorp.page" automapping="true"/> <controls> <control classname="com.mycorp.control.CustomField"/> </controls> </click-app> 

  When the Click application starts up it will deploy any control elements defined in the following files in sequential order:

  • /click-controls.xml
  • /extras-controls.xml
  • WEB-INF/click.xml

  Click also supports an alternative deployment strategy which relies on packaging resource (stylesheets, JavaScript, images etc.) following a specific convention. See the section Deploying Custom Resources for further details.

  Please note {@link org.apache.click.control.AbstractControl} providesa default implementation of the Control interface to make it easier for developers to create their own controls. @see org.apache.click.util.PageImports

• org.apache.cxf.greeter_control.Control
  This class was generated by Apache CXF 2.4.9.jbossorg-1 2012-10-10T18:22:55.689+02:00 Generated source version: 2.4.9.jbossorg-1
• org.apache.directory.api.ldap.model.message.Control
  Protocol request and response altering control interface. Any number of controls may be associated with a protocol message. Each control may be associated with a Request, a response, or both. @author Apache Directory Project
• org.apache.directory.ldapstudio.browser.core.model.Control
  The Control class represents a LDAP control as defined in RFC 4511

   Control ::= SEQUENCE { controlType             LDAPOID, criticality             BOOLEAN DEFAULT FALSE, controlValue            OCTET STRING OPTIONAL } 

  @author Apache Directory Project @version $Rev$, $Date$
• org.apache.directory.shared.ldap.codec.Control
• org.apache.directory.shared.ldap.message.control.Control
• org.apache.directory.shared.ldap.model.message.Control
  Protocol request and response altering control interface. Any number of controls may be associated with a protocol message. @author Apache Directory Project
• org.apache.directory.studio.ldapbrowser.core.model.Control
  The Control class represents a LDAP control as defined in RFC 4511

   Control ::= SEQUENCE { controlType             LDAPOID, criticality             BOOLEAN DEFAULT FALSE, controlValue            OCTET STRING OPTIONAL } 

  @author Apache Directory Project @version $Rev$, $Date$
• org.apache.jetspeed.om.profile.Control
  Default bean like implementation of the control entry in psml @author David Sean Taylor @version $Id: Control.java,v 1.2 2004/02/23 03:05:01 jford Exp $
• org.araneaframework.uilib.form.control.Control
  @author Jevgeni Kabanov (ekabanov@webmedia.ee)
• org.eclipse.swt.widgets.Control
  ipse.org/swt/snippets/#control">Control snippets @see SWT Example: ControlExample @see Sample code and further information @noextend This class is not intended to be subclassed by clients.
• org.javatari.pc.screen.Monitor.Control
• org.joshy.gfx.node.control.Control
• org.nasutekds.server.types.Control
  This class defines a data structure that holds information about a control that can be included in a request or response.
• org.odftoolkit.simple.draw.Control
  This class represents control object, a shape that is linked to a control inside an form. It provides methods to get/set control properties, content, and styles. @since 0.8
• org.olat.ims.qti.editor.beecom.objects.Control
• org.omg.CosTransactions.Control
  Generated from IDL interface "Control". @author JacORB IDL compiler V 2.3.2 (JBoss patch 0), 23-Dec-2011 @version generated at Apr 17, 2012 2:17:22 PM
• org.parosproxy.paros.control.Control
  Overall control with interaction on model and view. Window - Preferences - Java - Code Generation - Code and Comments
• org.resmedicinae.resmedlib.component.control.Control
  This class represents a control. It is passed up the chain of Controllers to invoke a piece of presentation logic. Controllers match against the id of a Control passed into BasicController#handleControl. If the id is recognised then the Controller can execute some presentation logic. If the Control id is not recognised, the Control should be sent back on its journey up the chain of responsibility by passing it to the parent Controller. See Controller#passControlToParent Controls are received by a Controller from either a View or a child Controller. Controls can optionally contain an Object parameter. The Control id is used by Controllers to recognise a Control and also as a key to the user-readable version of the Control's name in UIStrings presented to the user by the default error-handling mechanism in BasicController. @version $Revision: 1.7 $ $Date: 2002-06-12 18:49:37 $ $Author: chrissy $ @author Christian Heller
• org.scopemvc.core.Control
• org.spoutcraft.api.gui.Control
• org.zkoss.openlayers.control.Control
  @author jumperchen
• osgi.enroute.logger.api.LoggerAdmin.Control
• prefuse.controls.Control
  ">jeffrey heer

Examples of osgi.enroute.logger.api.LoggerAdmin.Control

Examples of prefuse.controls.Control