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

Quick Search    Search Deep

normal.packetui.census.* (1)normal.packetui.packet.* (6)normal.packetui.surfaces.* (9)
normal.packetui.triangulation.* (11)

normal.packetui: Javadoc index of package normal.packetui.


Package Samples:

normal.packetui.triangulation: Provides interfaces through which the user can interact with packets.  
normal.packetui.census
normal.packetui.packet
normal.packetui.surfaces

Classes:

PacketCreator: An interface through which a user can create a new packet. This interface can be any component, although usually it will be a container. The PacketCreator does not itself need to be the interface component, but it must be able to provide the component upon request. This is done through the getCreator() method. Often the PacketCreator will be the component itself, with the getCreator() method simply returning this . The interface will be placed within a NewPacketDialog , which will provide a mechanism for selecting the parent packet beneath which the new packet will be placed, as well as a label ...
PacketUI: An interface through which a user can interact with a specific packet. This interface can be any component, although usually it will be a container. The PacketUI does not itself need to be the interface component, but it must be able to provide the component upon request. This is done through the getInterface() method. Often the PacketUI will be the component itself, with the getInterface() method simply returning this . Each PacketUI object works with a single packet. Thus it is okay to have many different PacketUI objects in existence, some of the same class, but each referring to a different ...
PacketInfoUI: An interface through which a user can interact with a specific set of details for a specific packet. Several PacketInfoUI interfaces may be open for the same packet simultaneously within a single PacketUI . An example is when a larger PacketUI uses a tabbed pane, each tab containing a single PacketInfoUI . Only one PacketInfoUI within a single PacketUI should be editable at any given time. Preferably, when one such sub-interface is being edited, the others will blank out their details and disable editing accordingly until the initial editing has been cancelled or committed to the engine. The parent ...
PacketTabbedEditor: A packet viewer or editor containing a header and a tabbed pane of sub-interface components for specific packet details. The header is a label that will be displayed above the tabbed pane and should contain general information regarding the packet in question. Its value will be determined by calling the abstract method getHeader() . The sub-interfaces to be contained in the tabbed pane will be inserted during a call to the abstract method fillWithInterfaces() . Other than implementing this method, no further component initialisation needs to be done by subclasses of this viewer/editor. Note that ...
NewPacketDialog: A dialog through which the user can create a new packet. The dialog provides standard mechanisms to choose a parent for the new packet in the tree structure as well as a label for the packet, and provides OK and Cancel buttons to begin or abort creating the new packet. All other information gathering, as well as the packet creation itself, is done through a PacketCreator that is associated with this dialog. In the newPacket() function, all of the work is done for you. This function will create from scratch a new NewPacketDialog with the requested details, process the user's input and return a new ...
PacketInfoTabbedPane: A tabbed pane consisting entirely of PacketInfoUI tabs. Only components implementing the PacketInfoUI interface should be added to this tabbed pane. This interface is capable of both viewing and editing packets. The interface reported to the rest of the world as responsible for any event, packet change or the like will always be this interface and not one of its sub-interfaces. If any additional behaviour is required of this main interface when editing begins or ends in a sub-interface, the routine update() should be overwritten. However, super.update() should always be called to ensure the notification ...
PacketComboBox: A combo box through which a user can select a packet. The packets presented in the combo box may be an entire packet tree or subtree, or may be filtered using a packet filter. The actual objects stored in the combo box will be either PacketTreeNode or NPacket objects. This combo box may contain a NullObject (from package btools.utilities ); it will be displayed appropriately, and if such an object is selected then both routines getSelectedPacket() and getSelectedNode() will return null .
PacketListCellRenderer: A renderer for packets that can be used in lists. Each packet will have a cute icon placed next to it according to the packet type. A null packet or a NullObject (from package btools.utilities ) will be rendered by displaying the message <None> . Precondition: Only objects derived from NPacket are rendered by this renderer, aside from the exceptions mentioned above.
DefaultPacketEditor: A skeleton PacketUI that is capable of both viewing and editing packets. The decision as to whether packets are allowed to be edited must be made when the constructor is called. This interface will be an empty panel. Note that some routines from the PacketUI interface are not implemented.
TriangulationTableModel: An internal data model for a table containing triangulation data. This mirrors a triangulation in the engine, allowing the user to play with the model triangulation first before committing changes to the engine. This class is used by NTriangulationEditor .
GluingEditor: An interface through which a user can view or edit gluings of tetrahedra in a triangulation. The central component of this interface is a table that uses a TriangulationTableModel as its model.
DefaultPacketViewer: A skeleton PacketUI that is only capable of viewing packets. This interface will be an empty panel. Note that routines getPacket() and reflectPacket() are not implemented.
TetrahedronModel: A temporary model for a single tetrahedron in the triangulation. The user may play with this model before committing changes to the engine. See TriangulationTableModel for further details.
CoordinateViewer: An interface through which the user can view the individual coordinates of a normal surface set. The set that is currently being viewed can be changed by calling updateSet() .
Coordinates: Contains routines to handle the variety of available coordinate systems. Whenever a new flavour of coordinate system is introduced, only this class should need to be edited.
TetrahedronFaceEditor: Used to edit cells containing face gluings for tetrahedra. These are buttons which, when pressed, will bring up a dialog in which the user can specify a new gluing.
NSurfaceFilterEditor: An interface through which a user can view or edit a normal surface filter. See PacketUI for more details regarding user interfaces.
NNormalSurfaceListCreator: An interface through which a user can create a new normal surface list from a triangulation. See PacketCreator for more details.
TetrahedronDescriptionEditor: Used to edit cells bearing descriptions of given tetrahedron. This is simply a text field into which the user can type a new description.
NTriangulationEditor: An interface through which a user can view or edit a triangulation. See PacketUI for more details regarding user interfaces.
NCensusCreator: An interface through which the user can create a census of triangulations. See PacketCreator for further details.
NSurfaceFilterCreator: An interface through which a user can create a new surface filter packet. See PacketCreator for more details.

Home | Contact Us | Privacy Policy | Terms of Service