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

Quick Search    Search Deep

junk.gui.* (13)junk.images.* (1)junk.system.* (10)junk.util.* (11)

junk: Javadoc index of package junk.


Package Samples:

junk.gui
junk.gui.applet
junk.gui.box
junk.gui.chooser
junk.gui.dialog
junk.gui.window
junk.gui.menubar
junk.gui.background
junk.images
junk.system
junk.system.io
junk.system.jvm
junk.util
junk.util.ds

Classes:

Junk: The JD4X core module is known as the Java User's Network Kernel or JUNK. JUNK is the central operation kernel of the entire JD4X desktop system. It is a high level abstraction of the low level operating system kernel that is designed to manage the system on the network layer. JUNK consist of all the predefined interfaces and communication protocols that the rest of the other modules conform to and therefore it must exist throughout the entire desktop session. See the design and specification document for more details regarding JD4X compliant modules. JUNK is dynamic by nature such that the system ...
JXProcess: JXProcess is design to allow native programs to be executed within the JD4X environment. Each created JXProcess can be tracked and administered to by JUNK. The JXProcess uses a Java thread to wrap around each native process execution that was requested. JXProcess does not work well with scripts of any form and therefore scripts should not be used in a JXProcess. According to Sun's Java, a native process is executed outside the JVM's control and security, therefore the use of JXProcess is recommended to be kept to the minimum. The execution path of a JXProcess actually jumps outside of the Java ...
JXJvm: JXJvm is an abstract representation of a Java Virtual Machine running on a Linux process. It will provide all the JVM and class management features offered by Junk. In order to enhance the interaction between the desktop clients and the often neglected JVM, Junk provides a GUI interface to the features that the JXJvm offers. These features will allow multiple classes to be loaded into the JXJvm's runtime domain such that each JVM can host multiple programs using separate classloaders. Some basic JVM administration features will also be provided for the clients so that they can directly manipulate ...
PriorityQueue: Text Reference : Data Structures & Other Objects Using Java/ Michael Main, ch7 Class : Cmpt 115 (U of S) Implementation of an Object queue collection class used with an internal single linked list that can be traverse in a single direction (next Node of the linked list). Note that the use of List class must maintain the integrity of PriorityQueue class implementation. All insertion into the queue are done at the rear to easily maintain the order of entry, so that the first entry found with the highest priority is the first to be dequeued. List class implementation must maintain the integrity of ...
JXLookAndFeel: JXLookAndFeel provides the Java cross platform metal look and feel support on the JD4X system as a default. However, once the JD4X windowing module can support its own look and feel, this class may be deprecated. The advantage of keeping this implementation is that it depends on the J2SDK AWT and therefore it will be more portable than the JD4X windowing module. The disadvantage is that it is undependable and may result in inconsistant heavy weight component behaviour because the AWT depends on an existing desktop windowing manager that do not exist in the JD4X system without the windowing module. ...
JXDefaultWM: JXDefaultWM is the default Java window manager for the JD4X desktop. It has to be first registered with Moth before it can take effect. JUNK is responsible for selecting the desired window manager and registering it with Moth. Once the window manager has been determined, Moth will notify it whenever an event of interest occurs. The Java window manager is free to make any decisions regarding window behaviors. In this way the Java window manager controls the desktop without lossing too much performance. The degree of control that the Java window manager has, will depend on the specific platform implementation ...
JXWindow: JXWindow is a window with a custom drawn border and custom mouse handling behaviour. All custom components using it must define an empty border that do not overlap the custom drawn borders so that the custom border will retain its design. The client defined empty border should be a width of 5 or more if the client has altered the design. The design decision to include this custom heavy weight is so that some GUI can be platform independent such that porting it is easy and its behaviour can remain consistant in varying systems. One such example is the GUI of the JXController, which needs to exist ...
JXConfigMenus: JXConfigMenus provide a utility for setting up menus defined in a String[]. It uses '*' to indicate separators for the menu items, '*' must be the first char. It also uses '#' to indicate if the item is a JMenu, if it is not then it is assume to be a JMenuItem, '#' should follow after '*'. The '~' charactor is use to indicate an IconImage in the Junk image directory that will be use for the menu item. The charectors defined by the class should not be used in the users String[], other than to use the functions defined. Even though the methods in this class break the common parameter length guideline, ...
JXClassLoader: JXCLassLoader provides the capability to load classes into the current JVM runtime. This is a basic implementation of a network class loader. The boot strip class loader is not over written because over writing it will introduce security problems. The client should ensure that each Java application program is only loaded into 1 JXClassLoader for reasons regarding security and JVM guideline compliance. This implementation of the class loading mechanism is used system wide by all JXJvms. Note: findClass(...) is reserved for the JVM to do dynamic loading and it should not be directly called by a client ...
JXController: JXController is a GUI front end of Junk. It communicates the client request to Junk and Junk process them accordingly. Its main task is to present the information that Junk has and feed it back through a GUI. Because Junk is meant to be a high performance server, its front end is designed to be simple and fast to load. This class serves as an example of how to write a JD4X desktop controller and how to interface with JUNK. It also doubles up as the default JD4X desktop controller implementation. Implementation Hints: The desktop GUI controller can be customized as desired or even be totally rewritten ...
JXBackground: Provides the background of the desktop. It also allows images and wall papers to be drawn as user desires. On the XWindows/Windows System, it provides a layer that isolates the OS's components so that all functions is redefined by the JD4X desktop and not be detected by the system behind it. All components like the program frames and desktop icon should be place on top of this layer and not be added to it as a component. A full platform window manager has to be written to support the JXBackground such that the desktop background still remains within the Java environment and is customizable in Java. ...
List: Text Reference : Data Structures & Other Objects Using Java/ Michael Main, ch4 Class : Cmpt 115 (U of S) List is a collection class implementation of a single linked list. Only the minimum required methods needed to support PriorityQueue are implemented. Note that the use of List class must maintain the integrity of the PriorityQueue implementation. Objectives of List class & methods: -Provide methods to support the PriorityQueue class implementation. List class Limitations: - Beyond Int.MAX_VALUE, elements (priorityList) that deals with integer values will be wrong. - List with large Nodes produces ...
JXThread: JXThread is design to allow for a parallel execution environment. Each created JXThread can be tracked and administered to by JUNK. JUNK uses the JXThread to dedicate each task that was requested by a client into a separate execution path such that parallel computation is achievable. It will also reduce the possibility of a performance bottle neck situation in JUNK. A JD4X thread is defined by a valid module and a valid task request to that module. If both the module and the task is valid than useful work can be done else the state of the thread is considered to be invalid and no useful work can ...
JXTheme: JXTheme is the class that controls the current theme and allows for the GUI icons, borders and colors to change at runtime. It provides a system wide color theme and a centre resource for color changes and coordination. Direct variable access is allowed for performance reasons. The order of the icon names should never be altered because automatic parsing assumes that their fixed positions correspond to their predefined functionality. Anyone modifying this class should ensure that all values are final, unless runtime changes are required or desired.
JXInstaller: JXInstaller provides a custom installer and uninstaller for the JD4X system. It looks for necessary components that is needed to run JD4X and confirms user's options. It reconfigures the .Xclients file and backup the old file as .Xclients_jbak. It only backup to 1 level deep and subsequent old files are overwritten. Any failure to backup the old configuration files will also result in over write. Note that it is targeted at installion on Linux only.
JXMixComponent: JXMixComponent provides static utility tools that are commonly use in the junk desktop GUI development. It is mainly use to mix the swing components in a frequently arranged order, such as a JLabel followed by a JTextField and finally by a JButton to form a user input pad. Many of the algorithums in this class was refactored out after cutting and pasting the code multiple times during the desktop development.
JXConfigJButtons: JXConfigJButtons provides a utility for building large number of JButtons with the same set of properties. The null value is used to represent an empty attribute that does not want to be set. Even though the methods in this class break the common parameter length guideline, its advantage outweight the cost and therefore the design disadvantage is bore by the client.
JXClassLoaderManager: JXClassLoaderManager provides classloader management for the JXJvm. It allows the selection of all existing classloaders under its management. All the classes loaded into any of its classloaders can also be invoked to create an instance of that class. Reflection facilities are also available to retrieve a break down of the individual class instances.
JXListDialog: JXListDialog is a common GUI dialog that displays a JList. It is mainly used for the GUI listing of classloaders and loaded classes in a JXJvm. Clients are allowed to add their own custom defined button functions to the dialog to provide the appropriate functionality they desire with the dialog. Hopefully, this will make the dialog more re-usable.
JXConfirmDialog: JXConfirmDialog provides the basic commonly used confirmation dialog boxes on a windowing desktop. The desktop can use this dialog boxes for all its confirmation and communication with the client. This is to achieve a common desktop feel. All of JUNK's GUI interaction uses this class for confirmation purposes to ensure a standard desktop theme.
JXInputDialog: JXInputDialog provides the basic commonly used input dialog box on a windowing desktop. The desktop can use this dialog box for all its input communication with the client. This is to achieve a common desktop feel. All of JUNK's GUI interaction uses this class for input purposes to ensure a standard desktop theme.
JXSystem: JXSystem is the boot class of the entire JD4X system. It takes care of the command line options and passes them to JUNK. If no options are passed, it starts JUNK with the default settings. It also handles request for reboot or termination of the current desktop session Possible options are: None yet.
JXMenuBar: JXMenuBar provides a simple menu bar to organize all the facilities in the JD4X desktop. It has a set of drop down menu for all category of facilities build into the desktop. By this approach to the desktop facilities, the GUI tries to escape stereotype desktop designs such as Redhat or Windows.

Home | Contact Us | Privacy Policy | Terms of Service