I thankyou for your past work
+1
And for any future work you may do.
I'll try to be more conscientious about documenting and reporting any bugs I come across - there's an issue sometimes where fluff closes unexpectedly which I haven't taken the time/effort to nail down to where I can reliably reproduce it, but I'll do that and report. Seems the least I can do if I'm going to adopt your effort as my file manager of choice...
I had already invested some time in setting up emalfm2 to my liking before fluff came along. Extension size usually isn't a limiting factor for me, but I do like to keep an eye out for smaller and faster if sufficient functionality is there. I am following fluff, even reinstated it onto my wbar, and look forward to seeing it develop. With fluff included in base, it was a no-brainer to start the process of switching myself over from emelfm2 to fluff. With fluff as an extension, I have actually think about it and consciously make the decision to switch.
I was a bit surprised when fluff was initially included in base, not so much because of its size but because including it did seem to violate the fundamentals of Tiny Core. Useful as it is, it would have to be -awfully- tiny to justify being include in base instead of being an extension. I liked having it there in base because it gave a new user some capability to browse the base system without installing -any- extensions.
In a similar vein, I was surprised -and ecstatic- when "editor" was included, even though it too might be thought of as extension fodder. Leaving users of a base system saddled with busybox's vi (or any vi) seems cruel and unusual punishment even though the general run of Linux distros makes it not unusual at all.
Welcome
FAQ
Downloads
Wiki
