I tried that but I don't keep Xcode in the root of the Applications folder
and the stack gave a warning. When I moved it there, the Xcode commands
couldn't find it because I'd set the Xcode default to a copy in a subfolder.
Maybe a future update can determine the user's Xcode location. I have
Couldn't you search for the ASC provider in the helper stack pressing the
"Loupe" icon in the general settings?
-
Matthias Rebbe
Life Is Too Short For Boring Code
> Am 14.04.2021 um 01:12 schrieb J. Landman Gay via use-livecode
> :
>
> Cool. Thanks. I do keep NotarizationHelper in my
Cool. Thanks. I do keep NotarizationHelper in my plugins folder since I use it
frequently.
I probably will continue with the manual method for a while though, since I have three
different apps to notarize and I have to update the General settings each time. Maybe later
I'll revise your script
Jacque,
and if put the that NotarizerHelperStack into the plugins folder and if you add
the below code to your stack script
then you can directly code sign and notarize the created macOS standalone right
after it was built. ;)
on standaloneSaved pFolderSavedIn
if the
On 4/13/21 10:43 AM, Keith Martin via use-livecode wrote:
On 13 Apr 2021, at 11:28, Andre Garzia via
use-livecode wrote:
On the other hand, I think that the SB should create standalones that can
actually be deployed, this means that it should be able to handle notarisation
on the mac
> On 13 Apr 2021, at 11:28, Andre Garzia via use-livecode
> wrote:
>
> On the other hand, I think that the SB should create standalones that can
> actually be deployed, this means that it should be able to handle
> notarisation on the mac out-of-the-box.
Oh boy, THIS! And everything
> On Apr 13, 2021, at 5:28 AM, Andre Garzia via use-livecode
> wrote:
>
> I like all that I read here. There are things that are really hard when
> building standalone apps that I don’t think should be handled by LC HQ, such
> as “adding AppleScript dictionary” to your app. This is harder
I like all that I read here. There are things that are really hard when
building standalone apps that I don’t think should be handled by LC HQ, such as
“adding AppleScript dictionary” to your app. This is harder than it seems and
it involves plist manipulation, fancy sdef xml creation, etc.
On Mon, Mar 29, 2021 at 4:35 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I think we're all on the same page here.
>
:thumbs_up
--
Trevor DeVore
ScreenSteps
www.screensteps.com
___
use-livecode mailing list
Trevor DeVore wrote:
> We agree that LiveCode should include a sensible baseline for building
> a standalone. We also agree that they shouldn't try to write solutions
> for all possible ways that someone may need to distribute a
> standalone. My 2 cents is that LiveCode should provide a way for
On Mon, Mar 29, 2021 at 3:56 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> Here's the bottom of the post you were replying to:
>
> One suitable solution in the box is all that's needed,
> with the option for folks to turn it off if they prefer
>
Trevor DeVore wrote:
> On Mon, Mar 29, 2021 at 1:24 PM Richard Gaskin wrote:
>
>> Trevor DeVore wrote:
>>
>> > On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin wrote:
>> >> Add-ons to the product experience can be a useful temporary
>> >> workaround for long-time users, but if we step back and
On Mon, Mar 29, 2021 at 1:24 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Trevor DeVore wrote:
>
> > On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin wrote:
> >> Add-ons to the product experience can be a useful temporary
> >> workaround for long-time users, but
Trevor DeVore wrote:
> On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin wrote:
>> Add-ons to the product experience can be a useful temporary
>> workaround for long-time users, but if we step back and look
>> at the gestalt of the user experience they're not a true solution.
>>
>
> Do you think
On Mon, Mar 29, 2021 at 12:31 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Trevor DeVore wrote:
>
> > On Mon, Mar 29, 2021 at 10:57 AM Richard Gaskin wrote:
> >
> >> TL/DR:
> >>
> >> We don't need a generic player.
> >>
> >> What we need is an updated
Trevor DeVore wrote:
> On Mon, Mar 29, 2021 at 10:57 AM Richard Gaskin wrote:
>
>> TL/DR:
>>
>> We don't need a generic player.
>>
>> What we need is an updated Standalone Builder, to provide
>> more complete tooling and better guidance for building a
>> modern standalone.
>
>
> An easy way to
On Mon, Mar 29, 2021 at 10:57 AM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> TL/DR:
>
> We don't need a generic player.
>
> What we need is an updated Standalone Builder, to provide more complete
> tooling and better guidance for building a modern standalone.
>
An
The days of distributing apps without a cost to the developer are unfortunately
over (Mac/Win). If you want someone to be able to open an app on their Mac
without jumping through hoops, then you need to be a paid developer and do the
sign/notarize dance. LC could help automate parts of the
YES . . . What he said!
> On Mar 29, 2021, at 8:55 AM, Richard Gaskin via use-livecode
> wrote:
>
> TL/DR:
>
> We don't need a generic player.
>
> What we need is an updated Standalone Builder, to provide more complete
> tooling and better guidance for building a modern standalone.
>
>
>
19 matches
Mail list logo
