Yes, that was the reason I did it that way. Smaller downloads make less trouble for some people, to be sure, but software updates only require downloading the piece that changed. This will get to be a bigger deal as I add more modules. (If the number of modules ends up really big, this could get to be really important.) The other reason I split them up was so that if I had 10 modules but somebody only wanted to import/export, then they only had to download that module (+ the base) and they wouldn't have to mess with any of the other pieces.EricNoah said:
You could be right there. But I expect there'll be a number of folks that only want to use what others have done and have no interest in "building their own" stuff. And some of these modules could get large. And if you want to get into some of my "blue sky" ideas, there could be quite a variety of things out there that the "masses" wouldn't be interested in (because they don't need anything that special or want to learn anything too complicated). (For an idea of what I consider "blue sky", start with everything on the old list of WotC/Fluid's "expansion ideas" for eTools, and go up from there. Assuming, of course, that they don't do it first.)EricNoah said:
Not a bad idea for the released version. It would double the hosting space needed (and perhaps confuse potential downloaders a bit), but it wouldn't be too hard maintenance-wise.
