At 11:30 PM +0100 on 12/14/00, lcs@... wrote:

>A FB D&D shell does not do anything but lets the
>programmer insert the code for file processing. It
>should have an apple menu about ... item and also a
>setup that allows simple documentation insertion. No
>flash screen if there are >=1 incoming D&D items,
>since that wastes time. But, maybe if there are none,
>that would be a good idea.

Thanks, that's exactly what I wanted to know.

>It would be great if you would cook up something for
>FB^3 while I do the same for FB2.  If you can get the
>compactness of the FB2 Mini-app I'll latch onto FB^3
>right away.

I looked at the different runtimes to see which makes the smallest 
application.  I compiled them without any real code so they are as 
small as would ever be.

The smallest was the Tech runtime and then the Mac Toolbox.  Neither 
one supports 'HandleEvents' but that is a plus since a drag and drop 
wouldn't need all of the events.

I threw together a small working Tech runtime project.  It doesn't 
have an about box and only a quit menu item.  I don't think I have to 
handle the Edit menu but it should be there for desk accessories, if 
I recall.

It responds to dropped files with a small alert so far so.  I'll make 
it write to a log file like you mentioned.

Here's how big the applications are:

68k 17,551 bytes
PPC 22,721 bytes
FAT 39,060 bytes

FB^3 can make small applications but you don't get HandleEvents.

I'll probably look at the DropShell.c source to see what I should 
support as far as menus and events.  My thinking is that a D&D app 
doesn't need windows, except for an about box.
-- 
Heather Donahue
PGP Public Key at: http://pgpkeys.mit.edu
See X-PGP-fingerprint in headers.