Import improvements 3 You should be able to say "import x.y.z;" without _requiring_ double quotes around the "x.y.z". A semicolon _should_ be required to be more in line with Java conventions in the mjPackage syntax, and to exploit Emacs' JDE-mode automatic indentation. 2 2000-09-18 Support private data members 4 All data members are written out as protected but there is a case for making them private so not even classes in the same package or subclasses can get to them. 12 2000-11-28 Per David, the chaining of codes is read from SARA via ODBC, but the codes themselves are not. 2000-09-20 In the future, train will be broken down into hours, refresh, or train (current, perished or soon to perish, not qualed). For sims, we could indicate similar. 2000-09-18 Killer would be something like "LAT222,223,224 would otherwise expire 10/1 for an overall CRP loss of 0.9". 2000-09-18 This is much related to the "print rationale behind missions" item, but is for missions that the scheduler cares about and that could not be scheduled. 2000-09-19 We can really only do this with repsect to an algorithm that takes into account - may be very different for he Marbles scheme than it is for the current algorithm. 2000-09-19 We can simply do this by concatenating the individual XML files into a single "monster" XML file, just as I do for my WebScripterized to-do list. To that end it would be helpful if all input and output files have the same unique string in them, such as "Hardy1". 2000-09-19 Per David, we need to pass the time interval of validity back from the pilot agent to the mission controller to make this work (then it can be intersected with the time intervals it can fly). May not happen before Oct. 11th Yuma visit. 2000-09-19 Such a specification already exists in the pilot annotations file, but is not bound to a time horizon. 2000-09-19 Also, snap moved from being under na to being at the same level as na. 20 2000-11-28 We can *run* for a month but the output is not pretty - some pilots fly the same mission every day all month long while others barely fly anything at all, in addition SNAP schedules everything at the beginning of the month regardless of what the user specifies, and sequences of build codes are scheduled out of order. 5 2000-11-28 Not done because I convinved myself that this separation is worth the overhead it induces in defining new requests and resources, but just barely. With the separation in place, pure listeners such as the starfields and the ATTEND listeners need only include the API. 0 2000-11-28 They oked the new name. The technology disclosure number for Meta-Java is USC file #3108. 1 2000-11-28