Re: automating enabling of plugin settings on new versions

2017-02-14 Thread J. Landman Gay via use-livecode
Instructions are in the bug report, but basically you make a copy of the plugin, do whatever you want with it, and put it in your user extensions folder. It will override the LC copy. If you've installed for "this user" then that's who it will apply to. If you installed for everyone I assume

Re: automating enabling of plugin settings on new versions

2017-02-14 Thread Dr. Hawkins via use-livecode
On Tue, Feb 14, 2017 at 4:12 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > > I did that and it works fine. The user plugins folder is shared with all > copies of LC you have installed. I put my own copy in there some months ago > after submitting the bug report. >

Re: automating enabling of plugin settings on new versions

2017-02-14 Thread J. Landman Gay via use-livecode
On 2/14/17 4:46 PM, Dr. Hawkins via use-livecode wrote: Copying plugins on each release opens its own can of worms. I did that and it works fine. The user plugins folder is shared with all copies of LC you have installed. I put my own copy in there some months ago after submitting the bug

Re: automating enabling of plugin settings on new versions

2017-02-14 Thread Richard Gaskin via use-livecode
Dr. Hawkins wrote: > The issue is that as shipped, there is an option in the plugin > settings to save changes/choices--and it just plain doesn't work, > failing silently due to the permissions. > > Rather than saving inside of the application bundle, it seems that the > "correct" way for this

Re: automating enabling of plugin settings on new versions

2017-02-14 Thread Dr. Hawkins via use-livecode
On Mon, Feb 13, 2017 at 7:51 AM, panagiotis merakos via use-livecode < use-livecode@lists.runrev.com> wrote: > I think that changing the permissions of the app bundle may cause issues > with OSX's Gatekeeper. If you want to customize or change the settings (and > make sure the changes do stick)

Re: automating enabling of plugin settings on new versions

2017-02-13 Thread panagiotis merakos via use-livecode
Hi Richard, I think that changing the permissions of the app bundle may cause issues with OSX's Gatekeeper. If you want to customize or change the settings (and make sure the changes do stick) of the Application Browser, I suggest you put a copy of it in your Plugins folder. In case you are

automating enabling of plugin settings on new versions

2017-02-10 Thread Dr. Hawkins via use-livecode
WE went through parts of this a while ago, and being naturally lazy, I came up with chmod -R u+w `ls -rtd /Applications/LiveCode*/Contents/Tools/Plugins/revapplicationoverview.rev | tail -1` as an invocation to write enable the plugin folder and its contents for the most recent version (OS X;