Important release note:

This is the new MiscKit.  It uses new names for all it's classes, with the ªMiscº prefix.  I've added the new top-level files that will be used to convey verious bit of information, fixed up the license notices that appear in the source code, and so on.  The code itdelf hasn't really changed yet.  I'll have to get to that next; I need to fold Scott's ClockView into the kit and move my Tree and InfoController classes in.  Also, I need to finish off the Preferences system I've been designing.

Here's the daymisckit.
Please excuse the ugliness of this file; as you can see I know nothing about real typesetting!  ;^)

First, here's how to install the goods:

Install the lib files into /usr/local/lib.  In daymisckit-1/3.0 you will file 3.0-compatible libraries for Motorola CPU's.  In daymisckit-1/3.1 are 3.1-compatible fat libraries.  If you need a debugging library, then copy the daymisckit_g.a file as well as the daymisckit.a file.  After copying the appropriate library, be sure run ranlib on the file(s) in /usr/local/lib.
Copy the contents of the directory Headers to /LocalDeveloper/Headers.

If you wish to rebuild the libraries and install them, first edit the Makefile to taste (note comments on compiling fat/thin, etc.) and then type ªbuilditº in the daymisckit-1 directory to run my clean build+install script.  Both the regular and debugging libraries will be built and the libraries and headers will be installed for you.  (Installation of libraries is in /usr/local/lib and headers are placed in /LocalDeveloper/Headers.)  The script attempts to play a sound when it completes; you will most likely not have that sound on your system, so ignore the error that is generated by its absence.  You cannot build without the package "Makefiles.compressed" from ftp.byu.edu in /pub/next!  You have been warned!

NOTICE:  To  suggest improvements in the kit, direct your comments to the original author of the object(s) in question, as listed in AUTHORS.rtf.  To suggest ideas for new objects or general comments for the entire development team, or to get on the team yourself, send mail to the MiscKit mailing list at misckit@byu.edu (for list traffic) or, if you're not yet on the list, send mail to misckit-request@byu.edu (to either get on or off; this address will actually forward to Don_Yacktman@byu.edu).

This should be considered release 0.00.  This is just a collection of generally useful objects.  They are required for use in the GameKit, for example, but aren't included there since they are of a more general nature.

What's here will be useful to some, and very lacking for others.  The best thing to do is to bug the various authors about features that you need fixed or implemented.  Let us know if you have an idea for a nifty object, too.  The areas most frequently requested will, of course, receive more attention.  If there's something you'd like added, let us know.  If you find a bug, let us know.  If you think anything at all about this, let us know.

In spirit, license/use is utterly free.  Commercial, shareware, and freeware apps can all use this stuff as much as they want as long as they follow the whims as detailed in the file LICENSE.rtf.  That means there's no warranty, no support, and you are on your own.  Note:  It would be considered really slimy for someone to take this code, package it into their own objects/kit, and then turn around and sell it.  If you want to sell a object that makes use of any of this code, or sell one or more of these objects as part of a kit, then contact the author(s) of the object in question to work out something special that would fit the circumstances.  This is mentioned because you never know what some folks might try, and since this released is one of free objects, I'd get really pissed to find that someone had to pay for any of this!  Shoot, anyone can mail me a disk with return postage and I'll return it with the latest version and anything interesting to fill it up the rest of the way!

Despite the lack of official support, your feedback if very important.  The .m files all recap the license:  basically, if you use this stuff, you should acknowledge that fact in your app somewhere and provide info about how to get the latest versions of the objects.  It would be appreciated if you would send any changes you make to the original author of the modified object so that others may benefit, too.

Again, bug us about any questions and/or problems you have!

Share and enjoy!1

±Don_Yacktman@byu.edu

1Douglas Adams, The Hitchhiker's Guide to the Galaxy.  :-)