Quote:
Originally Posted by eschwartz
No point -- they share a common intertwined codebase. Separate packages would have to include most of the same code anyway, and even that is after some brave soul refactored it to separate them all. There are no significant gains over reimplementing fom scratch.  |
There speaks a true geek. Most ex-geeks and non-geeks have a different perception of reality I'm afraid.
For Windows:-
Why not just repackage what already exists. Don't ship outer components... i.e. the ones that end up in the main install folder... that are not needed by the editor and viewer programs. But probably leave the inner folders... ie DLLs, Microsoft.VC90.CRT, plugins2, qt_plugins and resources... as is, which should make it easier to upgrade the 'Calibre EditView' package to the 'Calibre Library Manager' package.
Ideally one would probably tweak the editor to disable the update metadata preference if calibre.exe not found.
And create a couple of whatevers (shortcuts, symlinks, aliases) to launch the viewer and editor.
Guess what, I already do it for three writer/micro publisher friends who don't need the library manager and who are 'paranoid' about having s/w on their computers that they don't use.
I use the portable package as the base, after removing what's not needed, I create and upload a zip to mediafire and send them the link, they know how to unpack the zip and 'deal' with it manually. I only make a new package if there are substantive changes to viewer or editor.
And no, I won't make it available to anyone else as I am not prepared to support it for anyone else.
How did I determine what to leave out - intuition, bit of experimenting, aided and abetted by Kovid's (usually) common-sense naming of things
BR