Home >> All

•	allensoft.bug.* (20)	•	allensoft.diff.* (14)	•	allensoft.gui.* (53)	•	allensoft.io.* (10)
•	allensoft.javacvs.* (175)	•	allensoft.mail.* (1)	•	allensoft.util.* (11)	•	allensoft.xml.* (1)

Package Samples:

• allensoft.bug.server
• allensoft.bug
• allensoft.diff
• allensoft.gui.treetable
• allensoft.gui
• allensoft.io
• allensoft.javacvs.client.event
• allensoft.javacvs.client
• allensoft.javacvs.client.ui.command.event
• allensoft.javacvs.client.ui.command
• allensoft.javacvs.client.ui.swing
• allensoft.mail
• allensoft.util
• allensoft.xml

Classes:

• CVSClient: This is the main class that implements the CVS client/server protocol. It is used to send requests to the server and process the server's responses. Typical usage is to create a batch of requests to perform and then perform them using the perfromRequestBatch method. For example, to perform a request that commits changes to a file with the log message "Added some new features" you could do this: // Create a request batch to add requests to CVSRequestBatch batch = new CVSRequestBatch(); // Add a request to the batch batch.addRequest (new CommitRequest (file, new CommitOptions ("Added some new features"))); ...
• FileSystemModel2: FileSystemModel2 is a TreeTableModel representing a hierarchical file system. This will recursively load all the children from the path it is created with. The loading is done with the method reloadChildren, and happens in another thread. The method isReloading can be invoked to check if there are active threads. The total size of all the files are also accumulated. By default links are not descended. java.io.File does not have a way to distinguish links, so a file is assumed to be a link if its canonical path does not start with its parent path. This may not cover all cases, but works for the ...
• CardPanel: A simpler alternative to a JPanel with a CardLayout. The AWT CardLayout layout manager can be inconvenient to use because the special "stack of cards" operations it supports require a cast to use. For example to show the card named "myCard" given a JPanel with a CardLayout one would write: ((CardLayout)(myJPanel.getLayout())).show(myJPanel, "myCard"); This doesn't work well with Swing - all of the CardLayout display operations, like show call validate directly. Swing supports automatic validation (see JComponent.revalidate()); this direct call to validate is inefficient. The CardPane JPanel subclass ...
• TextFileFormatter: Defines a text file formatter. This converts from one text format to another. This could be used to change the indentation of a source file, for example. The user can configure any number of these. The RepositoryDetails class can then be used to associate various formatters for a repository location. This is quite powerful and allows one to, for example, always ensure that C files in one repository location are indented so as to conform to coding standards. It also allows the user to check the file out in their preffered style. This allows individual developers to have different indentation styles ...
• RepositoryDetails: Defines details about how to connect to a repository given its location. A CVS repository location does not fully define how to connect to a repository for the ext or server connection methods. For example, what is the external command that should be executed? Should RSH or SSH be used? Because of this, this class defines these extra details when the ext or server is used. It also allows a name to be associated with the connection details thus allowing the user to refer to the settings by a simpler, or more obvious, name. This is much more flexible than the standard CVS way of doing it where the ...
• CrashHandler: Handles crashes (uncaught exceptions/errors) by reporting them to the user. By using the CrashReportingThread instead of a java.lang.Thread crashes are automatically reported to the global crash handler to be handled. Typically an application will install a crash handler by calling the install method supplying a name for the program and a version number and an optional BugSubmitter object for submitting crash reports: public static void main (String args []) { // Install crash handler that reports crashes using RMI to a server named "BugServer" // at somehost.somedomain CrashHandler.install ("Test ...
• FormPanel: A panel that uses FormLayout as its layout manager. Whilst FormLayout can be used in any JPanel , FormPanel provides a simpler interface for using FormLayout . Methods such as addField(Component, Component) 55 make creating a form much easier. FormPanel also exposes the methods from FormLayout .
• WorkingDirectory: Represents a working directory for a CVS client. A working directory contains a "CVS" sub directory that contains files such as "Entries", "Root" and "Repository". This class provides a high level view of these files and the entries that the working directory conatins. For efficiency purposes one cannot construct objects of this class directly but instead one uses the getWorkingDirectory static method to construct them. This allows a cache to be maintained so that the files are not constantly reopened and parsed every time they are needed.
• CVSIgnoreFileFilter: A file filter that decides if a file should be accepted based on rules for CVS ignoring files. The patterns in this filter are the default patterns to ignore. When determining if it should accept a file it will check these patterns as well as looking for .cvsignore files in the user's home directory or the parent directory of the file in question. The default patterns to ignore are retrieved from a setting called "defaultIgnoreFiles". If this has not been set then a hard coded set of patterns will be used instead which are common files for CVS to ignore.
• CVSIgnoreFile: Defines a pattern based file filter whose patterns are taken from a file. The patterns are separated by white space. Typically, these will be .cvsignore files in the user's home directory or directories being recursed by an import or add command. The file is automatically reparsed when it is modified externally. The patterns in this filter reqpresent the patterns in the file. Note that this filter accepts files only if a pattern does not match the file. This is because the patterns specify files to be ignored.
• CrashReportingThread: A Thread sub class that automatically reports any crashes (i.e uncaught exceptions/errors) that occurr during its execution. Use this class in place of the java.lang.Thread class to ensure all threads in your application will report their crashes. This class can be used exactly like the java.lang.Thread class except that instead of overriding the run method you must override the runThread method.
• DefaultKeywordSubstitutionModeClassifier: Classifies the keyword substitution modes for files. It is possible to explicitly set the keyword mode for a particular file. If this has not been done then it will determine if the file is binary by comparing it's name against a set of patterns for binary files. These patterns are stored in the "binaryFiles" setting. If this has not been set then default patterns will be used for binary files.
• TreeTableModel: TreeTableModel is the model used by a JTreeTable. It extends TreeModel to add methods for getting inforamtion about the set of columns each node in the TreeTableModel may have. Each column, like a column in a TableModel, has a name and a type associated with it. Each node in the TreeTableModel can return a value for each of the columns and set that value if isCellEditable() returns true.
• CVSRequestBatch: Defines a sequential list of requests that should be performed. This allows a client to open only one connection to the server and perform all the requests for that server in a batch. This reduces the number of times that the user has to authenticate theirself to the server. For example, you could add requests to add new files, remove files and commit the changes all in one connection.
• LoginManager: Responsible for obtaining login details from the user. Implementators of this interface can request login details in whatever manner they wish. For example, one implementation may be to get the login details by using a swing based dialog and another may ask the user to type it in on System.in. This allows the client package to be abstracted from the user interface.
• CVSRequest: The base class for all requests to a CVS server. A request is perofrmed by a CVSClient object using the CVSClient.performRequest method. Sub classes of this class can use the helper methods sendXXX to send specific commands and data to the server. These methods forward the request to the client to actually send it over the current server connection.
• Wizard: A Wizard is a dialog that guides the user through a series of steps they must perform to accomplish a task. Each step is represented by a page. When the user has finished with a page they can use the "Next" button to advance to the next page. Once all pages have been completed they can click on the finish button to complete the wizard process.
• XMLGUIBuilder: Builds toolbars, menus, menu bars and menuitems from XML based documents. This can be used to create user configurable menus. An example of the structure of the XML document is: . . .
• ASCIIInputStream: Takes a reader and converts it to an input stream which reads in ASCII characters. If any characters on not in the ASCII range then an IOException will be thrown to prevent corrupted values being read in. This is needed by a lot of stupid APIs that use InputStreams for reading text files (eg Properties and XML API) instead of Readers.
• TextFileContainsBinaryException: Exception thrown when a file is not marked as binary but contains binary. JavaCVS is tricter than cvs and won't allow a file that contains binary characters to be sent to the server if it is not pure text. This is beacuse the \r\n sequence gets changed to \n and this could corrupt a file if it is really a binary file.
• CrashReportingEventQueue: An event queue that reports any crashes to the global CrashHandler . This can be used to catch exceptions that occur in the AWT event thread. It is identical to the standard event queue but catches any uncaught exceptions and passes them on to the CrashHandler .
• RepositoryDetailsDialog: Dialog used to edit repository details. If no repository details are supplied then this dialog will assume it is editing a new one to be added which will be added to the details when the user clicks Ok. Otherwise it will allow the user to edit the details of the supplied repository.

Home | Contact Us | Privacy Policy | Terms of Service