At 7:48 AM +0100 on 12/30/00, lcs@... wrote:

>It is lacking doc and menus menus but it has heirarchical
>folder processing and post-launch D&D.

I'm considering adding that myself to the one I'm working on.  It 
would come in handy.  I can select a single file from an open dialog 
box using StandardGetFile but I'll need to make a custom one to 
handle selecting folders.  That adds a lot of code.  I'd like to use 
NavServices if it's available but again that adds a lot of code.

Post-launch D&D is always available with AppleEvents.  It wouldn't 
take that much extra code to recursively deal with folders.  Right 
now I'm just logging the file data I get from a FSSpec, name, dirID 
and volume number.

>So, on the balance you have done as much programming as my
>demo (and in key respects more). And the size is the same.
>
>Impressive.  A real challenge to the notion that
>FB^3 will be significantly less space-efficient than FB2.

Looks like I've got to pare down my code a little ;-)

Actually, I've got 1024 bytes in one 8bit icon by itself.  But I also 
have a nice scrolling about box where you can put credits or simple 
instructions. :-)

While the PPC is about 27k and the 68k is about 28k, I still think 
that for most people the FBII runtime version will get more use.  It 
would be about 10 times larger though.  Adding things like 
NavServices, standard windows and a few other niceties I have in mind 
would quickly close the gap between the Tech/Ultralite runtime size 
and the FBII runtime.


Actually, since with the FBII runtime I'd have very little to do 
codewise, I'm wondering just what features others might want in such 
a shell.  Any suggestions as to what a multi-purpose drag & drop 
shell should do even if it weighs in at over 200k?


Heather