Quantcast

automating enabling of plugin settings on new versions

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

automating enabling of plugin settings on new versions

Dan Friedman 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; linux will be similar and depend upon variant)

This changes the mode (chmod) recursively; the ls finds the version with
the latter date stamp.

However, even though the mode changes, I still can't write, and have to
manually load the application browser.

Isn't that folder the only thing we used to need to changer am I missing
something?
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: automating enabling of plugin settings on new versions

Dan Friedman 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 interested, see
http://quality.livecode.com/show_bug.cgi?id=17757 for more details on this.

Best,
Panos
--

On Fri, Feb 10, 2017 at 9:36 PM, Dr. Hawkins via use-livecode <
[hidden email]> wrote:

> 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; linux will be similar and depend upon variant)
>
> This changes the mode (chmod) recursively; the ls finds the version with
> the latter date stamp.
>
> However, even though the mode changes, I still can't write, and have to
> manually load the application browser.
>
> Isn't that folder the only thing we used to need to changer am I missing
> something?
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



--
Panagiotis Merakos <[hidden email]>
LiveCode Software Developer

Everyone Can Create Apps <https://livecode.com>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: automating enabling of plugin settings on new versions

Dan Friedman via use-livecode
On Mon, Feb 13, 2017 at 7:51 AM, panagiotis merakos via use-livecode <
[hidden email]> 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) of the Application Browser, I suggest you
> put a copy of it in your Plugins folder.
>

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 to happen is to be writing to ~/Library/Application\
Support

In fact, my understanding is that *not* writing there is, by apple's
definition, a bug/wrong/heresy/etc.

Copying plugins on each release opens its own can of worms.

--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: automating enabling of plugin settings on new versions

Dan Friedman 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 to happen is to be writing to ~/Library
 > /Application\Support

Even better, the plugin should ideally stay where it is but write its
prefs out to a separate file in some user-writable folder.

You may want to contact the author to see about modernizing the prefs
handling. I've found the team very receptive to handling updates of
bundled plugins, but v9 DP is approaching, so the sooner the better.

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: automating enabling of plugin settings on new versions

Dan Friedman via use-livecode
In reply to this post by Dan Friedman 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 report.

If you don't have a user plugins folder, create one in the My Livecode
folder. (Whoever named that, I'll find them some day.)

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: automating enabling of plugin settings on new versions

Dan Friedman via use-livecode
On Tue, Feb 14, 2017 at 4:12 PM, J. Landman Gay via use-livecode <
[hidden email]> 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.
>

But as I understand, that is "incorrect" behavior--preferences should be by
user, not shared.

And I'm not sure about doing it from the finder, but in general on unix,if
you move (mv) or copy (cp) folder b to a and there si already a folder a/b,
young  up with a/b/b rather than replacing b.


--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: automating enabling of plugin settings on new versions

Dan Friedman 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 the change will apply to all users. I
always install for just me so that's what I'm familiar with.

If LC updates their plugin then you'd have to replace your copy, but as
they promised me in the report, they'll tell us if that happens.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com



On February 14, 2017 6:57:10 PM "Dr. Hawkins via use-livecode"
<[hidden email]> wrote:

> On Tue, Feb 14, 2017 at 4:12 PM, J. Landman Gay via use-livecode <
> [hidden email]> 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.
>>
>
> But as I understand, that is "incorrect" behavior--preferences should be by
> user, not shared.
>
> And I'm not sure about doing it from the finder, but in general on unix,if
> you move (mv) or copy (cp) folder b to a and there si already a folder a/b,
> young  up with a/b/b rather than replacing b.
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Loading...