RE: [Mav-user] Commands vs. Controllers

[Schnitzer, Jeff]

Title: Commands vs. Controllers

Keep in mind that I have the javadoc generation configured to only show public classes and interfaces.  This is the subset of Maverick that is of specific interest to anyone who wants to develop with Maverick, and leaves off a lot that would be of interest to people who are developing Maverick itself.  If you would like to generate javadocs for everything, include the attribute Private=”true” on the javadoc ant task.   Everyone’s comments were right-on though.  Command is the internal structure that determines what Maverick does when a particular command (ie blah.m) is executed.  ControllerWithParams is a decorator that adds controller params defined in the config file to runtime controllers.   Jeff Schnitzer [EMAIL PROTECTED]     -----Original Message----- From: Thompson, Kris [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 7:23 AM To: [EMAIL PROTECTED] Subject: [Mav-user] Commands vs. Controllers   What is the deal with the  Command interface, it doesn't appear to be used in the src code... according to the Javadocs at least?  Is this some old code that is just laying around or is it part of some future plan? Next question, what is the purpose or use of the ControllerWithParams Controller? Thanks Kris Thompson