On 11/05/2010 02:00 PM, DM Smith wrote: > IIRC: Troy said these were there to satisfy a publisher's request that > some info from a module's conf be shown for modules installed this way. > It only ever worked in BibleCS. Is that still a valid concern?
Well, almost. There is a feature in the engine where you can specify in your module repository: [Globals] AutoInstall=newmods where newmods is a folder which lives at the same place as mods.d/ and modules/ on loading of a module repository, SWMgr does a scan of this folder for .conf files and will copy them to the mods.d folder, but first will call a hook method SWMgr::AddModToConfig which allows a fontend to display a nice dialog box: "Hey, you've installed a new module! Here's the About information..." or whatever. This mechanism was, as DM mentions, added at the request of a publisher when BibleCS was the only frontend available. Permission to use their module was predicated on us showing their about information upon installation of their module. I'd definitely like to remove the Win32 specific InstallShield module install packages. BibleCS InstallMgr is undergoing some "play nice with other frontends" updates right now looking toward an eminent update of BibleCS compiled against 1.6.2 and with av11n support. I suggest after this release we remove the windows installer files. Do we have any feedback on the MacOSX installer files? Troy _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page