View Single Post
Old 11-22-2014, 08:52 AM   #74
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 29,008
Karma: 210162574
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by varlog View Post
In my opinion, if the plugin uses independently developed piece of software, it should be written as a wrapper around this software - thus making a library of it. Than it is possible to update only library, only wrapper or both of them.
That is exactly how the current KindleImport is designed. It is a wrapper around the KindleUnpack command-line tools. It doesn't have a way to automatically update just the KindleUnpack "library" files, but then again, it's early days. A tool to update just the KindleUnpack "library" isn't out of the question.

Honestly, I'm not quite sure what your point is here. The plugin is written in a way you've just indicated you think such plugins should be written (a wrapper around a "library") ... and there's absolutely nothing stopping any plugin developer from creating the update function function you desire.

Last edited by DiapDealer; 11-22-2014 at 09:05 AM.
DiapDealer is online now   Reply With Quote