J040603a: Peano Numerals ALPHA Compiling Diary & Job Jar

Status	Date	Description





	2004-12-13	Go through and find out which strumenti are relied upon in Numbering Peano so far and create the appropriate configuration-management anchors for those dependencies. Even if they are mere place holders, we will have a start on compiling important information that we need. It is important to have that covered for the dependencies listed in manifest files, in particular.
	2004-12-02	We will put the techniques of identifying in Zips and in the code and manifests in J040602d. Then we will use J040603d here as the place for dealing with the latest 0.11x version and let those be rebuilt there as long as they need to be. The .htm should indicate the most recent manifest so that someone would know to look at it.
	2004-12-02	The need to recompile with different J2SE SDKs and with other changes in platforms puts a kink in our versioning and labeling scheme. We could do triples, we could do generation numbers, we may need both. Some of this matters in the way we set up the com.orcmid package tree, some of it doesn't. How do we handle this?
done 2004-12-02	2004-09-27	Harmonize the J040603c material with J040602b on Organization. [dh:2004-12-02 This is handled with J040602c on Situating Peano Numeral.]
	2004-09-25	Retrofit the linkage information that is settled on for J040603d into the ~~J040603b and~~ J040603c .zip files and the .txt descriptions for them. [dh:2004-12-02 Don't do that. Instead, create a J040603d.zip and J040603d.txt for 0.11 and beyond within the 0.1x progression.]
	2004-09-25	Create J040603d to identify the links we will use in packages. Start with J040603c.txt and what we see as needed for the 0.11 versions of the Java source files.
	2004-09-19	Ensure that J040601 and A040601 cross-reference each other.
	2004-09-19	Link J040603c 2.1 to where we entertain more than 3 basic methods on the interface. Notice, when there, that some of the base class methods that are exposed don't accomplish anything except to assert that these class methods must be defined in a way that satisfies what we say are the constraints on the interface. It's a device for that.
	2004-09-19	Link J040603c 1.7-1.8 to further materials as available
	2004-09-19	Link J040603c 1.6, 3rd bullet to wherever we cover that.
	2004-09-19	Find out if the factored conditional in J040603c 1.4 actually works
	2004-09-19	J040603b should link to the J040603c materials (see also 2004-09-18 on obsolescence).
	2004-09-19	Identify material here that should be used as the basis for material on Situating Java and also Strumenti information, other consolidations on Java lore.
	2004-09-19	Update the J000001-log to reflect the versions here
	2004-09-19	Move J040603.htm to 0.11. [dh: 2004-12-02 This only happens when J040603d is created.]
	2004-09-19	Review the links from J040603 to collateral materials and refresh those as appropriate
	2004-09-19	Make version J040603c 0.11 and incorporate J040603c.htm into J040603c.zip [dh:2004-12-02 We're not going to do that. Instead, We expand on the packaging of J040603d.zip to include the additional information about the behavior of the interfaces.
	2004-09-19	Review the job-jar items from earlier days to see how many can be completed with version 0.11.
	2004-09-19	Complete the materials in J040603c.zip, with updated J040603c.txt. See 2004-09-18 items about this.
	2004-09-19	Add the 0.11 versions of the key files to Section 4, renaming the last 0.10final versions as needed. Emphasize ALPHA in all of the descriptions and links.
	2004-09-19	Make sure the 0.10 files are labeled 0.10final in VSS before we rename/upgrade to new versions.
done	2004-09-19	Elevate J040603.htm to version 0.10 as well and we will track that artificial way from now on.
done	2004-09-19	Do what can be done to make J040604c.txt into a version 0.10 in the archive for now.
done	2004-09-19	Add WinZip to the software that is used. Add IE 6.0 also, with regard to MHT files.
	2004-09-19	Add an explicit license to the material.
done	2004-09-19	Caption tables, make finer paragraph identification, and provide bookmarks for fragment-access to all of them.
done	2004-09-19	Walk through J040603c and attend to every spell-checker indicator.
done	2004-09-19	Make an edit pass over the material in J040603c 0.00 and elevate it to 0.10 before completing section 4. Have attention on what is here, what we accomplish with it, and what is not here but to be dealt with elsewhere: Section 1, 2, 3, 4.1, 5
fixed	2004-09-19	Section 3.3 StubbyRun $Header was updated in the web page instead of being frozen for the code.
fixed	2004-09-19	Section 3.2 compilation code has garbled cd command lines at the bottom.
fixed	2004-09-19	Section 3.1 bullet (4) needs clarity around making up requirements as I go along
fixed	2004-09-19	Section 3.1 bullet (3) below the code has funny language.
fixed	2004-09-19	Sectioh 2.1 first sentence is really clumsy
done	2004-09-19	In the last list in section 1, fix the first entry, "for is for"
done	2004-09-19	Add J040603c 0.00 section 4 subsections to the contents table at the beginning of the page.
done	2004-09-19	Make first list of J040603c 0.00 into bullets.
done	2004-09-19	Stitch J040603c into J040603!
	2004-09-18	Include a lessons-learned and questions-surfaced treatment somewhere, especially for more questions about Java rules. The links back to source in error messages matter, for example. What happens when the current source is out of sync with the class file that was used? Can that happen or is there tighter coupling than that?
	2004-09-18	At least J040603c.txt should provide information on how to compile things, or it should be in StubbyRun, in the way I have done this in the past. This is more important than for J040603b.
	2004-09-18	Place an obsolescence notice in J040603b.zip and J040603b.txt, indicating that the material is preserved for reference purposes. There should be reference to the initial successor and a better place to find out more.
done	2004-09-18	Have the http://orcmid.com home page link to the com.orcmid material as advertised in J040604c here.
done	2004-09-18	Capture the Num.class that is produced for checking that cosmetic changes have no material impact.
done	2004-09-18	Make the basic 0.10 version of Num-0.1x.java and verify that it compiles.
done	2004-09-18	Publish everything and then cycle back and make the Zip agree with the non-Zip material that refers to it.
done	2004-09-18	Tie the J040603b.txt and the J0406503b.zip into the J040603b.htm better and make that version of J040603b.mht the one that we also stuff inside the zip.
done	2004-09-18	There should be text in J040603b.zip and maybe even a copy of the J040603b.htm material. There needs to be a .txt file or something similar to provide the equivalent of a readme and/or manifest.
done	2004-09-18	Hook in J040603.txt.
	2004-09-15	0. The whole progression here probably belongs somewhere else, such as on the work item list of an overall project description here. It's really what goes in J040601. Create it up there and then move any items that we can from here to there, appropriately. [dh:2004-09-15 I'm looking at that and that's part of the answer but there's more to do about that, including having a subproject here just for the 0.10 stage, then the next stage, etc.]
	2004-09-15	15. Then we look at building different implementation classes and have them work with each other and also map somehow into the basic Java classes. (There might be some kind of linear transformation for that, which would be interesting.)
	2004-09-15	14. Then we're going to deal with the serious baggage. What about "=" and what about the implicit methods and features of the Num interface? We get to deal with comparisons, toString, and possibly other interfaces that must be supported along with Num, and can people get to them from Num? We have already had to deal with exceptions too and what ones are the only ones that Num methods could throw. We go through the deal about explicitly identifying them or not.
	2004-09-15	13. So now we add JavaDoc to the picture. We will tie this into my site in some useful way, and we'll key to the principle Java API JavaDocs too.
	2004-09-15	12. We will blend in the how do we use this with the trial implementation and a really-simple command-line program as we have been going along here. We should have gotten about as far as we can get on that score. [dh:2004-09-19 This is done with StubbyRun]
	2004-09-15	11. The next step is to add two URLs to the file. One is about Astraendo and what we are doing, around the intention and what things mean, and the other is about the URL into the ALPHA section and what that provides. We get to point out that none of this changes the compilation of the Java interface class, except where it does. [dh:2004-09-19 This happens in 0.1x too.]
	2004-09-15	10. We will then introduce a version of Peano axioms and the addition of dim() and allo() and why we need those. There will be some talking about that. [dh:2004-09-19 This should be up in J040601 as part of requirements work, as well as maybe discussed more over at Astraendo.]
	2004-09-15	9. Then I will start to talk about the identification of place and the mapping of nomenclature in the interface definition and some "place" and some identification of something. [dh:2004-09-19 This seems to be where 0.1x leaves off, everything up to having the axioms.]
	2004-09-15	8. On Astraendo, initiate the discussion about what is identified and what we know about what is identified. I will disclose what the names mean and I will start the conversation about the com.orcmid. path and how that all works by agreement.
	2004-09-15	7. Create a Numbering Peano note that refers to the Astraendo note that refers to here. That can be commented on in the Numbering Peano note, referring to points of contact that can then not be moved.
	2004-09-15	6. Create the Astraendo note that shows the Num-0.10 source code and links to where it is found here, adjusting as needed. [dh:2004-09-19 That is Num-0.1x source codes, I think.]
done 2004-09-18	2004-09-15	5. Have this note and the Num-0.10 material easy to find and not too bogus if some one comes right here from Astraendo.
done 2004-09-18	2004-09-15	4. With that success create the necessary materials right here to reflect that and have the materials be available. (That is going to have to be a Zip, I think).
done 2004-09-18	2004-09-15	3. Confirm that a little application that uses Num and the simple class also compiles there. See if it has to be in the package or not. [dh:2004-09-18 and run it, of course. Twit!]
done 2004-09-18	2004-09-15	2. Confirm that a class that supports Num can compile in the same place in a separate file. [dh:2004-09-18 It needs a classpath to anything it accesses, such as Num.class, though.]
done 2004-09-18	2004-09-15	1. Confirm that Num-0.10 compiles.
in progress 2004-09-18	2004-09-15	Create an initial post that won't require any rework. The first thing we will show is Num-0.10 and say that we aren't going to say much. This will be a note in Astraendo but it will tie to material here. Let's prepare the material for here. The steps are above.
	2004-09-15	There is also going to be JavaDoc. I am going ot move to the use of JavaDoc at some point, and I want to keep the class file still of a reasonable size.
	2004-09-15	The same thing happens for the web and documentary side of all of this. There's FrontPage, the screen-capture utility, Visio 2003, and things like that.
	2004-09-15	I want to use configuration information to tie in the 4NT, Java, and Windows versions. I need at least place-holders for those three elements of the Compagno configuration. Also, IIS, VSS, jEdit, jEdit plug-ins, etc. Initiate that activity. [dh:2004-12-02 Also include WinZip and Internet Explorer versions in manifests (done) and in the strumenti information. I think maybe I would link to that in the Manifest too, so that someone could fully deal with the configuration management aspect of things.]
done 2004-09-27	2004-09-15	Characterize the associated hierarchies (the local Java2 directory, the local inetpub directory, and the web site (image) directory. I am describing this for my own sanity. [dh:2004-09-26 This is in J040602b.htm]
done 2004-09-18	2004-09-15	Can the Java2 project path at Java2\projects\com be used in classpath and end up working? Can I get by without it. [dh:2004-09-18 It works just fine and jEdit's JCompiler will figure it out when I am compiling package material down there. A class path directive is required to access the material properly.
done 2004-09-18	2004-09-15	Make some kind of test class that exercises things enough so that we can show that the instantiated class and interface works just fine, thank you very much.
done 2004-09-18	2004-09-15	Find out about the class path and whether I can compile a class that uses the interface without difficulty, still in the local directory even with the package directive. [dh:2004-09-18 the class path must be set up for access to package and package-internal material, although it isn't always needed to compile into a package.]
done 2004-09-18	2004-09-15	Confirm that the Num-0.10.java file compiles properly, and save the Num.class that is produced for it. This is the key one, since this is the start of a progression of successive improvements, most of which won't impact the compiled class file one wit.
done 2004-09-18	2004-09-15	Re-rationalize this material and maybe tie the subpages to the versions of Num-0.xx ALPHA versions that we take ourselves through.
done	2004-06-28	Put this project into the catalog
done	2004-06-14	Use UTF-8 for pages with code displays so that blot-characters can be presented correctly.
done 2004-09-18	2004-06-14	What is the default for the method names. Does public have to be explicit? [dh:2004-09-18 Not for methods on an interface. Interface members are automatically public.]
done 2004-09-18	2004-06-14	Figure out what happened with the package name and how that impacts the platform, if at all. [dh:It is relevant for locating the Num.class and other materials, even when package-internal.]
done 2004-09-18	2004-06-14	Look up the appropriate passages of the Java language specification about package-relative-internal.
in progress	2004-06-14	Show the .class file and notice what appear to be platform dependencies in it, especially the use of ASCII codes.
done 2004-09-18	2004-06-14	Document compiling the 0.01a file. Capture everything, bring it to ALPHA, and stitch into project page.
done	2004-06-14	Make Num-0.01a.java as a file to experiment with different solutions.
done 2004-09-18	2004-06-12	Document the complication and compiling the 0.01 file
done	2004-06-12	Fork Num-~~0.10~~0.01.java as a way of showing what is going on.
done	2004-06-12	Create subproject for ALPHA organization.