crunch@well.UUCP (John Draper) (09/19/87)
A Description of the "Crunched Shell"
-------------------------------------
A bunch of us guys here on the Programmers Network are collaborating
on a group project that will be of interest to students, teachers, or
anyone serious about writing Macintosh Application programs in C or Pascal.
This group project is to "Hack" together a very large and perhaps useful
Macintosh Example program covering EVERY use of the extensive Mac Function
calls. This includes Device drivers, and how to call them.
A very preliminary conference has been estrablished on the WELL where
the organization of the project will take place. We are currently mapping
all of the functions the program is to haveand are just now starting
the project. So anyone interested in participating in
the project should contact me so I can build up a mailing list for those
interested. Direct participation will be taking place on the WELL, but
we plan on periodically posting to UseNet our progress, and taking mail
from those who want to give us feedback on what you think we should include.
I suspect that we will be making incremental "Upgrades" starting from
a more "primitive" shell, and progressing with newer and newer "Features".
Then, whan a good solid "Application" is written, we plan on posting
it in source code form to "net.sources" for ALL to use and enjoy.
However, I suspect there might be as many as 50-60 source files, and
I suspect that a "Gradual" posting process is in order so the
sites won't get peeved by the excessive traffic. If we wind up posting
source on "net.sources" or wherever it goes, it will be self-contained
modules which can be integrated into a library and be useful unto itself.
And usually be less than 20-30k in size.
I'll probably be making up diskettes and sending them to people who
want them for some small fee to cover our costs. Another idea was to
put the $$$ into my defense fund to be used for my legal defense against
a rediculous crime I was accused of. In either case, this "Crunched
shell" will be a very useful tool for the Mac consultant, and free to
use anyway one wishes for either commercial or instructional use.
A Hypercard Stack will probably be created to allow the user to quickly
"Index" into a particular piece of code and show ALL of the pieces needed
to do a particular function, such as MDEF, WDEF, custom menu stuff,
and all the other pieces of code that's lacking.
We will stress on making the code modules compile on LightSpeed C, and
MPW C, and will also include some number crunching stuff using the in-line
68881 co-processor for Mac II users. The code will clearly show the
Differences between LightSpeed C and MPW (There are more than you think)
and the same source code will compile on BOTH. I have LOTS of experience
writing code that compiles on BOTH MPW and LightSpeed C on a VERY LARGE
application program containing 110 Source code modules.
The diskettes should contain:
1. 50-60 Source code modules that compile on MPW and C (Pascal comes
later).
2. A MPW Makefile, and a Worksheet containing various commented utility
commands.
3. An un-loaded LightSpeed C project which runs on the Ver 2.01 LSC.
4. A Hypercard "Stack" containing a "referencing" and "locating" system
for Quick access for whose wanting to hack up a quick application,
and full documentation on how it's put together.
5. A Resource file both Resed and De_resed.
6. A Nosey .snt file
7. An Xref file
8. A MAp file.
9. MDEF and WDEF source files and Make code to create it, and
code in the main application that tests for these file before
attempting to use.
10. Source code for a device driver. I'm trying to get a MIDI driver
and source code in main program that tests for this before attempting
to install it and use it.
We will do the very best we can to modularize it, and will be using
Mac App source code as a guide, because I suspect that no set standard
will exist for both MPW and LightSpeed C if and whenever they get a
Mac App for C, I think that following this guideline will be useful.
Remember!! I'm posting this to give YOU a chance to give us our feedback
so we can make this more useful to everyone.
For anyone wanting to help us out, become involved, or just be a casual
observer, please let us know. I suspect the levels of involvement might
look like this:
1. Direct participation - Must have account on the WELL
2. Idea contributor - Just respond with some of your ideas
3. Source code example contributor - We'll take Anything at this time
4. Casual observer - Just look but don't touch
5. User of the "Crunched shell" as a useful tool for your collection.
When responding, please indicate a little about what you would like
to Know about, and what you can do to help us out.
As we progress through the project, we will be posting periodic progress
reports for those unable to directly participate.
Thanx:
John Draper & Kenton Hoover - Programmers Network
"The Programmers Network guys"
WELL: crunch
BIX: crunch
UUCP: ihnp4!ptsfa!well!crunch