For cli workflow: hooks (including plugin hooks) can access config.xml <preference>'s for things like the sqllite compile example (recompile only if settings changed would be nice), and access <preference> at runtime for the console example.
For old workflow, perhaps sqllite is documented to manually run the hook to recompile whenever you want to change the default setting? Just thinking about alternatives and/or solutions that are actually feasible short term. -Michal On Wed, Mar 5, 2014 at 4:03 PM, Jesse <purplecabb...@gmail.com> wrote: > Okay, you convinced me. args make sense for hooks for preinstall/install > hooks, everything else, the plugin scripts should be able to manage on > their own by writing some config/settings data to it's own plugin folder. > > I think the bigger discussion for now needs to be around the permissions, > security, and policy. > > > @purplecabbage > risingj.com > > > On Wed, Mar 5, 2014 at 12:48 PM, Jonathan Bond-Caron < > jbo...@gdesolutions.com> wrote: > > > On Wed Mar 5 02:54 PM, Jesse wrote: > > > I am a no to passing arguments, the use-case is really about doing some > > > extra > > > tasks for the current environment. > > > > > > > Not necessarily: > > > > > https://github.com/apache/cordova-plugin-console/blob/master/www/logger.js#L48 > > > > cordova plugin add cordova-plugin-console --use-console true (preinstall > > script tries to keep console.log on platforms where it exists) > > > > It's also about options to support different workflows. > > > > For sqlite (which would be awesome btw), it's also enabling/disabling > > default compile options: > > https://sqlite.org/compile.html > > > > I'm not saying this can be done short term or that the extra complexity > is > > worth it but should consider looking into it... > > > > >
