sandboxing
hi
I just opened the v3 beta which is quick and I suspect it will be great.
However, the image sandboxing is problematic. Do you have a beta that respects relative addressing to my embedded image files?
thanks
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on 16 Aug, 2017 08:15 PM
I enabled Sandboxing for exactly this reason -- too many things sneak by when it's turned off and enabled in later testing.
Sandboxing compatibility should be finished in the next day or two.
Support Staff 2 Posted by Fletcher on 19 Aug, 2017 02:13 AM
v16 includes support for sandboxing access in the preview (e.g. images) and in file transclusion.
Let me know how it works -- it's been rewritten from scratch since Composer v2, so needs some more testing.
Fletcher closed this discussion on 19 Aug, 2017 02:13 AM.
Raymond Brock re-opened this discussion on 17 Sep, 2017 02:39 PM
3 Posted by Raymond Brock on 17 Sep, 2017 02:39 PM
hi
I eagerly just tried the new version from the app store. Looks great, but I’m still confused about sandboxing. My indirect referencing to image locations is not followed.
Thanks for the pro redemption but there was no way to apply it so I purchased pro as successive update from purchased standard.
thanks
Ray Brock
On Aug 18, 2017, at 10:13 PM, Fletcher <[email blocked]<mailto:[email blocked]>> wrote:
Support Staff 4 Posted by Fletcher on 17 Sep, 2017 02:47 PM
Send me an example of a file that is not working. If you use a proper
URL, Composer will ask for permission to access the necessary folder.
Sorry that you couldn't redeem the Pro token -- you redeem it in the App
Store app (all purchases handled by Apple). Instead, share it with
someone who you think would benefit from using Composer.
Fletcher
Support Staff 5 Posted by Fletcher on 17 Sep, 2017 02:52 PM
Hmm... I just checked on machine, and it seems that something broke in
the App Store build in regards to sandboxing....
Let me dig into it.
F-
Support Staff 6 Posted by Fletcher on 17 Sep, 2017 03:01 PM
I think I figured it out -- sandboxing is ok, there's an issue where
it's only finding images defined by reference:
e.g.
![foo][bar]
[bar]:/path/to/image
works, but this doesn't:
Can you verify that fixes it for you? I'll fix for next release.
Fletcher
On 9/17/17 10:52 AM, Fletcher T. Penney wrote:
> Hmm... I just checked on machine, and it seems that something broke in
> the App Store build in regards to sandboxing....
>
> Let me dig into it.
>
>
> F-
>
> On 9/17/17 10:47 AM, Fletcher T. Penney wrote:
>> Send me an example of a file that is not working. If you use a proper
>> URL, Composer will ask for permission to access the necessary folder.
>>
>>
>> Sorry that you couldn't redeem the Pro token -- you redeem it in the
>> App Store app (all purchases handled by Apple). Instead, share it
>> with someone who you think would benefit from using Composer.
>>
>>
>> Fletcher
>>
>>
>> On 9/17/17 10:39 AM, Raymond Brock wrote:
7 Posted by Raymond Brock on 17 Sep, 2017 03:14 PM
hi
Thanks for the quick response. I went through the App store, BTW. The upgrade buttons take you to the apple store with no redemption possibility. However, this is $30 well-spent if it fills my needs, which are intensive these days.
The file is actually a Jekyll-based document and functions fine in Typora and other markdown apps. Everyone deals with this apple sandbox security thing differently. I’ve attached it.
But actually, just sitting here doing something else the app crashed. When I brought it back up it said to send the crash report, two of which are attached. I’ve also pasted the Problem Report from the apple tool below. Tell me if there’s another multimarkdown-specific report?
thanks
Ray
PS Does Multimarkdown Converter go from LaTeX to mmd also? Or just the other way around. I’m converting hundreds of pages of a textbook I wrote to mmd and Pandoc is sometimes squirrelly.
Support Staff 8 Posted by Fletcher on 17 Sep, 2017 03:40 PM
Ray,
1. Correct -- there is no mechanism from Composer itself to redeem
tokens. You have to use the App Store app, and in the main window there
is a "redeem" link.
My apologies for not making that clear, that was not my intent. And I
certainly hope the $30 feels well spent after a couple of days
2. Your doc uses explicit images (``). If you change
one of these (at the "highest" directory level, e.g. closest to the
drive root) to a reference image (`![foo][bar]`, and `[bar]:
/path/to/image`), that will trigger the sandboxing and it should work.
You will need to save, close, and reopen your document (maybe twice).
I'll fix explicit links for next release.
3. Thanks for sending crash reports -- I've never seen an issue there,
so not sure what happened. I added a fix that should prevent the issue
in next release. But this occurred during synchronized scrolling (e.g.
when you scroll the editor, the preview scrolls with it). You can
disable that functionality in the preferences to avoid another crash
until the next version is released (later today??)
4. I don't create any tools to convert LaTeX to MMD. LaTeX is so
complex, there's no way to do it "right." You can guess at the basics.
I've got an idea that would allow this (for the basics), but it's part
of a more complex project that may or may not make it off the ground.
For the moment, pandoc is probably the best bet.
F-
9 Posted by Raymond Brock on 17 Sep, 2017 06:02 PM
hi
Thanks…in-line question:
On Sep 17, 2017, at 11:40 AM, Fletcher <[email blocked]<mailto:[email blocked]>> wrote:
Support Staff 10 Posted by Fletcher on 17 Sep, 2017 06:13 PM
Tender does strange things to inline editing -- was there another question that you had? I couldn't see one.
11 Posted by Raymond Brock on 17 Sep, 2017 06:19 PM
Sorry… It was in response to:
2. Your doc uses explicit images (``). If you change
one of these (at the "highest" directory level, e.g. closest to the
drive root) to a reference image (`![foo][bar]`, and `[bar]:
/path/to/image`), that will trigger the sandboxing and it should work.
You will need to save, close, and reopen your document (maybe twice).
I'll fix explicit links for next release.
and was:
“
I’m not sure what you mean. First, many of the images in this file are html <img src… as the only way I could figure out to control the size of the image in the preview of most apps, like LightPaper and Typora. But should I go back to the markdown call to images (previous chapters have this mostly as I wanted to stay as close to mmd as possible and gave up at this point…) to something like
{:width="500px"}<br>*caption*
How explicitly … and where in the file …are you suggesting the foo bar changes? I couldn’t parse your suggestion.
"
thanks for staying with me on what must be a busy day for you,
Ray
On Sep 17, 2017, at 2:13 PM, Fletcher <[email blocked]<mailto:[email blocked]>> wrote:
Support Staff 12 Posted by Fletcher on 17 Sep, 2017 06:43 PM
1. HTML links won't work (unless there's another link to trigger asking
for sandbox permission, like below).
2. If you trust that I am not doing anything nefarious, add something
like this to your document:
![fake]
[fake]: /Users/<myusername>/fake.png
This should trigger Composer to ask for read permission of your home
directory. Any images inside that folder should now work (you may need
to close and reopen to reset the cache).
3. If you don't trust me, you can be more specific with the image path:
[fake]: /Users/<myusername>/some/folder/that/is/isolated/fake.png
(But only images inside that folder will work -- the "higher up" that
Composer can access, the more folders you can use without worrying about
it).
F-
13 Posted by Raymond Brock on 17 Sep, 2017 07:57 PM
hi
Thanks. That indeed works, but of course I don’t have such an image and so I’ll always have a broken image in each file.
I hate to say it, but this seems sort of cumbersome. I can’t even use it to point to a legitimate folder/image since your second suggestion is an absolute path and I work on multiple computers where my home directory doesn’t always sit on the volume where references point.
I’ve had other apps ask for permission…and then that works from that point on without any skulduggery …that’s visible to the user. I see what the hidden skulduggery is now with your suggestion. Can you do something like that without going to Apple Jail?
thanks…sorry,
Ray
BTW. I am not pointing to URLs (“links”) for images, just using HTML commands/tags inside of the markdown document. All pointing at the same image folders that I reference with mmd commands.
On Sep 17, 2017, at 2:43 PM, Fletcher <[email blocked]<mailto:[email blocked]>> wrote:
Support Staff 14 Posted by Fletcher on 17 Sep, 2017 08:01 PM
Once you get the permission, you can delete the link. It's a one time
thing (or until you reset preferences, or the permission expires). You
don't have to do it in every document.
And again, the next release fixes the issue with explicit vs reference
links.
F-
15 Posted by Raymond Brock on 17 Sep, 2017 08:04 PM
ah. and hence the skulduggery.
Thanks
Ray
On Sep 17, 2017, at 4:01 PM, Fletcher <[email blocked]<mailto:[email blocked]>> wrote:
Support Staff 16 Posted by Fletcher on 18 Sep, 2017 10:19 PM
4.0.1 is out, and this should be fixed.
Thanks!
Fletcher
Fletcher closed this discussion on 18 Sep, 2017 10:19 PM.