Home >> All >> org >> jempeg >> [ empeg Javadoc ]

•	org.jempeg.empeg.core.* (8)	•	org.jempeg.empeg.emplode.* (126)	•	org.jempeg.empeg.emptool.* (22)
•	org.jempeg.empeg.logoedit.* (6)	•	org.jempeg.empeg.protocol.* (92)	•	org.jempeg.empeg.util.* (4)

• org.jempeg.empeg: Javadoc index of package org.jempeg.empeg.


Package Samples:

• org.jempeg.empeg.core
• org.jempeg.empeg.util
• org.jempeg.empeg.emplode.action
• org.jempeg.empeg.emplode
• org.jempeg.empeg.emplode.dialog
• org.jempeg.empeg.emplode.model
• org.jempeg.empeg.emplode.model.predicate
• org.jempeg.empeg.emplode.plaf
• org.jempeg.empeg.emplode.util
• org.jempeg.empeg.emptool
• org.jempeg.empeg.protocol.event
• org.jempeg.empeg.protocol
• org.jempeg.empeg.protocol.packet
• org.jempeg.empeg.logoedit

Classes:

• BmpToLogo: Converter program to turn 24bit per pixel grayscale bitmap to 4bpp empeg logo. To use it compile the file, add it to your CLASSPATH and then run > java bmpTo4bpp player-type home-logo car-logo output-file The first parameter should be either 'empeg' or 'rio' and determines if the empeg should boot with the empeg graphic/animation or the rio graphic/animation. The second parameter is the home logo. The third parameter is the car logo. The fourth parameter is the output file to create. All bitmaps must be 24bit, uncompressed, grayscale images. This program will warn you if you try to feed it something ...
• ConnectionIfc: A ConnectionIfc is the interface that must be implemented to provide basic communication capabilities to the Empeg. Each implementation of this interface defines a different channel that can used to communicate to an Empeg This probably needs to be "cleansed" of its C heritage by getting rid of not stream-based communication (i.e. send and receive).
• AbstractChangeablePanel: AbstractChangeablePanel provides some convenience methods for tracking changes on various components (like buttons, checkboxes, comboboxes, and textfields). This is extended by things like the Empeg configuration dialog and properties dialogs that need to know when the user has modified various components in the dialog.
• Emplode: Emplode is the main class for the Java Emplode clone. Much like Emptool, the various methods of Emplode implement the various functions that can be executed by the user. The binding of these methods to buttons and panels is done through the .dialog and .action packages.
• EmplodePlaylistManager: Emplode is the main class for the Java Emplode clone. Much like Emptool, the various methods of Emplode implement the various functions that can be executed by the user. The binding of these methods to buttons and panels is done through the .dialog and .action packages.
• EmplodeConnectionManager: Emplode is the main class for the Java Emplode clone. Much like Emptool, the various methods of Emplode implement the various functions that can be executed by the user. The binding of these methods to buttons and panels is done through the .dialog and .action packages.
• PropertiesManager: PropertiesManager provides a series of type-safe interfaces to a Properties file (that is a multiple line "key=value" format). The primary use in Emplode is that this interface is used to save runtime configuration properties for future sessions.
• FileMagic: This class parses audio files to determine their format and tagging, and exposes that information through a common interface. It uses the TFF Enterprises music tagging classes as its implementation of the ID3v1 and ID3v2.2/2.3 standards.
• AbstractEmpegDiscoverer: AbstractEmpegDiscoverer is the base class for the various implementations of ways that an Empeg can be automatically located. Each implementation would provide a different type of connection on which the Empeg might be found.
• PlayerDatabase: PlayerDatabase is the primary interface to manipulating and querying the database of songs and playlists on the Empeg. It also provides the low-level implementation of downloading and synchronization to the Empeg.
• Uploader: Uploader is similar to Upgrader, but rather than upgrading an Empeg, it simply uploads a chunk of data to a particular address of the Empeg. This is basically equivalent to Hugo's download.c and Tony's upload.exe.
• TreeTableConnector: TreeTableConnector hooks tree selection events up to the right-side table so that as the tree selection changes, the table model will be updated with the contents of the corresponding tree node.
• CompoundEmpegDiscoverer: CompoundEmpegDiscoverer provides an implementation of AbstractEmpegDiscoverer that encapsulates discovery across a set of sub-discoeverers. This proxies events of each of the sub discoverers.
• ProtocolClient: ProtocolClient defines the protocol communication layer at a higher level than Request. ProtocolClient exposes all of the core processes that can be performed via the Empeg protocol.
• NetworkEmpegDiscoverer: NetworkEmpegDiscoverer implements discovery over a Socket-based TCP/IP network. Discovery is based on broadcasting a datagram to over port 8300 and listening for the Empeg to respond.
• UnicastNetworkEmpegDiscoverer: UnicastNetworkEmpegDiscoverer implements discovery over a Socket-based TCP/IP network. Discovery is based on communicating over port 8300 and listening for the Empeg to respond.
• AbstractFileDropTargetListener: AbstractFileDropTargetListener defines the capabilites that are common to dragging-and-dropping files from the native filesystem onto either the playlist tree or playlist table.
• AbstractPropertiesDialog: The abstract superclass of the various properties dialogs (like tune and playlist). This builds a tabbed pane inside of a modal dialog along with the OK/cancel buttons.
• EmpegScreen: An EmpegScreen is a renderer for the GrabScreenPacket. This basically grabs the bytes off of the Empeg's screen and displays them in a JComponent of configurable size.
• ProgressDialog: ProgressDialog is an implementation of DatabaseProgressListenerIfc that renders a set of labels and JProgressBars to represents the status of a download or upload.
• NodeTags: NodeTags is the datastructure that keeps track of a set of key-value pairs of MP3 tags (like title, album, etc.) There is one NodeTags for each FID that is loaded.
• BasicEmpegPlaylistTreeNode: BasicEmpegPlaylistTreeNode is the most simple implementation of EmpegPlaylistTreeNodeIfc (basically nothing :) ). This is used for the root node of the Empeg tree.
• SearchesPlaylistTreeNode: BasicEmpegPlaylistTreeNode is the most simple implementation of EmpegPlaylistTreeNodeIfc (basically nothing :) ). This is used for the root node of the Empeg tree.
• DatabaseTags: DatabaseTags is a doublely-hashed datastructure that maps Empeg MP3 tag names to Empeg MP3 tag IDs (and vice-versa). There is one DatabaseTags per PlayerDatabase.
• EmpegOutputStream: EmpegOutputStream is an OutputStream that implements the type conversion (both endianness and signedness/unsignedness) that matches that of the Empeg's protocol.

Home | Contact Us | Privacy Policy | Terms of Service