Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

arch.message.* (3)arch.module.* (9)arch.task.* (9)

Package Samples:

arch.task.supported: The task package holds the generic service or task definition that is used to describe a module specific service or task offered through the JD4X core module (JUNK).  
arch.message
arch.message.error
arch.message.request
arch.module
arch.module.icore
arch.module.major
arch.module.minor
arch.module.data
arch.task

Classes:

JXSupportedTask: Every JD4X module must list the possible supported services that it provides to the JD4X system. Each of the service that a module provides to JUNK is represented by an integer id with a variable object that describes the task to be performed by that id. Each module must provide a minimum string description of each service provided. An unique range of id values will be assigned to each major module of the JD4X system by the JD4X development team. Every other minor module will have to provide their own unique module task range such that JUNK is able to clearly identify them. This class is the parent ...
JXModule: In order to deal with the complexity of building a desktop system, JD4X is divided into modules and each module deals with a specific area of the desktop functionality. The whole JD4X system consist of major modules which implements the basic desktop features and minor modules which are designed to dynamically extend any other area of the desktop feature such as devices, functionality and much more. JXModule is the super class of all modules in the JD4X system. It defines the properties of a basic module. See the design and specification document for more details. The contract both explicitly and ...
JXRequest: A JXRequest represents a request to the desktop system. It encapsulates within itself 4 basic information, (1) who the request is for. (2) what is the task or service requested. (3) what is the priority level of the request. (4) The user (User's system ID) who made the request. Each set of the 4 basic information is considered to be a collection. In order to improve efficiency, an array of JXRequest object should be sent such that it will allow multiple sets of request with only one connection from the client. The priority level does not neccessary mean definite precedence but that it will have ...
JXMinorModule: A minor module in the JD4X system is not a required basic module such that without it the JD4X system can still be considered as a fully functional modern desktop. It can provide any specific area of functionality, extension and/or feature that is an enhancement to the current major modules or provide any customize facilities specific to its clients. It defines the common properties of a minor module and is subclass by all other specific minor modules that interact with JUNK. Minor modules do not need to be integrated directly into JUNK and is seperately distributed from the entire JD4X package. ...
JXMajorModule: A major module in the JD4X system is a required basic module such that without it the JD4X system cannot be considered as a fully functional modern desktop. It should provide a specific area of functionality that is considered to be a need and not an extension to the desktop. It defines the common properties of a major module and is subclass by all other specific major modules that interact with JUNK. Major modules has to be integrated directly into JUNK for security reasons and will not be distributed separately from the entire JD4X package. Independent developers intending to work on a major ...
JXMessage: JXMessage provides a generic message passing facility in the desktop system. It does not interpret the message passed but ensures that a set of common methods are provided such that different modules can talk to each other by passing the correct message objects that they understand internally within the recieving module. In order for the project team and independent developers to coordinate on a possible data object understood system wide, the JXMessage was developed. This class is designed for inheritance. The contract both explicitly and implicitly defined for all of its subclasses MUST be adhered ...
JXTask: JXTask represents a task that the requester wants a specific module to do on its behalf. A task here is defined as a service that is provided by a module through JUNK. It defines the main (minimum) information of what service is requested by the client. It is the parent class of all custom user defined requests. All service request to JUNK must therefore be a subclass of it or in other words this class was designed for inheritance. The contract both explicitly and implicitly defined for all of its subclasses MUST be adhered to strictly, in order to assure JD4X system compliance. Note that its subclass ...
JvmSupportedTask: This is JXJvm's list of the possible supported services that it provides to the JD4X system. Each of the service that is provided by JXJvm is represented by an integer id with a JunkTask object that describes the task to be performed by that id. JXJvm's unique range of id values are assigned to be 3000-3199 by the JD4X development team. In an event that there is a service or task ID request clash, JUNK will take priority against all other modules. The specific action taken to deal with an id clash exception will be to reject the service requested. The class has been made final for security reasons. ...
JXError: JXError defines an user customized error that describes what went wrong while performing a job. It provides the facility to associate a JVM stack trace to the error so that the error can be debugged. The error message object passed is not interpreted by the class but is left to the client Object to interpret it. Its main design is to provide a standardized system wide error object handling facility such that it will facilitate system message logging and response handling. Note: Most of the main abstract classes are designed to return an error object instead of throwing an exception for reasons ...
JXProcess: JXProcess is design to allow native programs to be executed within the JD4X environment. It holds status information about the executing native linux process. This class is not designed to replace the Process class in the J2SDK. It is merely used to manage process executed by the OS module, Linux. Developers should never use this class except for management purpose. The Process class in J2SDK should be sufficient for most developer's programming needs. Processes created in the OS module was design to support native GUI applications, daemon processes and other processes incompatible with the Process ...
LinuxSupportedTask: This is Linux's list of the possible supported services that it provides to the JD4X system. Each of the service that is provided by Linux is represented by an integer id with a LinuxTask object that describes the task to be performed by that id. Linux's unique range of id values are assigned to be 6400-9599 by the JD4X development team. In an event that there is a service or task ID request clash, Linux will take priority against all other modules. The specific action taken to deal with an id clash exception will be to reject the service requested. The class has been made final for security reasons ...
MothSupportedTask: This is Moth's list of the possible supported services that it provides to the JD4X system. Each of the service that is provided by Moth is represented by an integer id with a MothTask object that describes the task to be performed by that id. Moth's unique range of id values are assigned to be 3200-6399 by the JD4X development team. In an event that there is a service or task ID request clash, Moth will take priority against all other modules. The specific action taken to deal with an id clash exception will be to reject the service requested. The class has been made final for security reasons ...
JunkSupportedTask: This is JUNK's list of the possible supported services that it provides to the JD4X system. Each of the service that is provided by JUNK is represented by an integer id with a JunkTask object that describes the task to be performed by that id. JUNK's unique range of id values are assigned to be 1-3199 by the JD4X development team. In an event that there is a service or task ID request clash, JUNK will take priority against all other modules. The specific action taken to deal with an id clash exception will be to reject the service requested. The class has been made final for security reasons.
JXWindowManagerInterface: JXWindowManagerInterface defines the basic interface methods that a JD4X native window manager must support to ensure consistency within different windowing module implementations. The interface does not seek to constraint the desired behavior or the desktop management policy enforced by the native window manager. Its purpose is to allow a set of minimum facility that a Java implementation dependent window manager needs to be able to control regardless of the native window manager implementation. The interface was designed mainly to support the default windowing module, Moth.
JXWindow: JXWindow is a data type that defines a native window. This class is designed to be portable and platform independent. Unlike JWindow, it does not define any functional methods. All its functionality is isolated to the window manager and it merely keeps track of the state of its native peer component. It is meant to be used in conjunction with a JD4X window manager and should not be used by any application. Java applications should use the Swing components instead of this class because it is not designed to replace them.
MothTask: MothTask describes a service or task that is supported by the current JD4X windowing module implementation. Each service or task is represented by an integer id defined in the MothSupportedTask class and a detailed string description of what that service is as well as what it does. It is mainly used to define the JXTask in a JXRequest sent to the core module (JUNK). This class is an immutable class that is designed for thread safe operation.
JXCoreModuleInterface: JXCoreModuleInterface defines the basic facility that needs to be implemented by any JD4X compliant core module implementation. The interface is used to ensure that the facility will exist and therefore all compliant core modules will integrate flawlessly with the other major modules. However, depending on the individual implementations the method of handling the task maybe different and may result in inconsistant core module behaviour.
LinuxTask: LinuxTask describes a service or task that is supported by the current JD4X OS module implementation. Each service or task is represented by an integer id defined in the LinuxSupportedTask class and a detailed string description of what that service is as well as what it does. It is mainly used to define the JXTask in a JXRequest sent to the core module (JUNK). This class is an immutable class that is designed for thread safe operation.
JunkTask: JunkTask describes a service or task that is supported by the current Junk implementation. Each service or task is represented by an integer id defined in the JunkSupportedTask class and a detailed string description of what that service is as well as what it does. It is mainly used to define the JXTask in a JXRequest sent to the core module (JUNK). This class is an immutable class that is designed for thread safe operation.
JXBootInterface: JXBootInterface defines the minimum features that a core module needs to notify its boot class to carry out its desired action. This interface is useful for testing and automatic reboot after a new update such that new changes can take effect in the core module without ending the current desktop session.
JXControllerInterface: JXControllerInterface defines the minimum features that a GUI front end of Junk must provide in order to allow Junk to notify it of changes. All custom GUI desktop controller must implement these interfaces. Implementations of a custom GUI desktop controller must also extend the JXMinorModule interface.

Home | Contact Us | Privacy Policy | Terms of Service