If you're referring to LiveCode settings that determine how to manage the plugin (i.e. cREVLoadInfo), it would be good if this info was stored outside the plugin. But obviously it needs to be configurable on the author's side, as well as the user's side, and somehow loaded in the user's LiveCode installation. Maybe you (the developer) want some plugins to open normally, maybe some invisibly, maybe some just to sit in the plugins folder without launching.
(Not trying to get in a debate on what is the correct way to develop a plugin, just sayin' :-) It would be a bit of a chore to have to include a separate "default prefs" file with each plugin, but I imagine one could write a "first launch" script as part of their plugin's startup that checks to see if its configuration stuff is where it should be, and if not, writes a new file. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 3/23/14 12:23 PM, "Richard Gaskin" <ambassa...@fourthworld.com> wrote: >For the long term, should plugin settings be stored separately from the >plugin itself, so that the plugin isn't modified? > >This raises many question. Desirable, but not simple. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
