Yep, you're correct. It says 64bit.
I must have been blind.
thanks!
Op 11-11-2018 om 14:59 schreef Sean Cole (Pi) via use-livecode:
The release notes for 9.0.0 stable state otherwise as quoted below
referring directly to the IDE, not Standalones.
To quote:
The *IDE* is now 64-bit by default
The release notes for 9.0.0 stable state otherwise as quoted below
referring directly to the IDE, not Standalones.
> To quote:
>> The *IDE* is now 64-bit by default on Mac
I also checked on my versions here and it is definitely 64bit so I’m not
sure why your machine is not saying the same.
Try th
Yes i know the standalone can be 64bit.
I also know how to check in Macos if a program is 64bit.
I was talking about the IDE itself. That's 32-bit.
Op 10-11-2018 om 22:41 schreef Pi Digital via use-livecode:
https://downloads.livecode.com/livecode/9_0_0/LiveCodeNotes-9_0_0.pdf#page32
To quot
https://downloads.livecode.com/livecode/9_0_0/LiveCodeNotes-9_0_0.pdf#page32
To quote:
> The IDE is now 64-bit by default on Mac
> Moreover, the "Build for Mac OS X 64-bit" is checked by default on newly
> created stacks in the standalone settings for OS X. Existing stacks will
> retain their c
JJS wrote:
> In Mojave i got a a message "you are running a 32bit program" (the
> livecode ide).
>
> Within a certain amount of time it's going to "force" to use 64bit
> programs
Yep, and the team has come through: several months ago they delivered
v9.0, which now allows standalone building fo
By the way.
In Mojave i got a a message "you are running a 32bit program" (the
livecode ide).
Within a certain amount of time it's going to "force" to use 64bit programs
Op 10-11-2018 om 20:08 schreef Richard Gaskin via use-livecode:
Bob Sneidar wrote:
> People cannot remember commands, e
Bob Sneidar wrote:
> People cannot remember commands, especially not terminal commands,
> with all the arguments and caveats and different ways to put it all
> together.
For end-users, the awareness of that principle is very powerful.
But where are we, here in this discussion? On a mailing lis
In the release notes of LC is a line that states: LC is actually a
command line tool.
Op 10-11-2018 om 13:18 schreef Pi Digital via use-livecode:
Hi
Just to follow on from Andre, you can of course also run terminal scripts from
LC. That’s exactly what I did in the aforementioned OSX Package
Hi
Just to follow on from Andre, you can of course also run terminal scripts from
LC. That’s exactly what I did in the aforementioned OSX Package Maker (soon to
be reissued as the iOS/macOS Package Maker). You ‘could’ make a GUI for every
terminal command available including every nuance and pa
Bob,
I am hijacking this thread to express some personal opinions about the
terminal, it is not related to the topic of the original message but a
different perspective on the subject you brought up on your reply.
When I first for my mac (A G3 running Mac OS 8.x) and started developing
for i
I agree that the LiveCode Application Builder should handle all the details.
The stacks that others have built work great … until they don’t. That’s why my
instructions are all Terminal based. If something errors out, you can see the
error and perhaps deal with it. When everything is hidden beh
It's funny you should say that. Long ago when the first Apple MacIntoshes came
out, I fell in love with the GUI simply because I could use a computer without
having to type in commands. For years, I would not even work with a PC, because
all their was to work with was DOS, and even when Windows
Hi Kee,
Thanks for that. Although I’ve been down that
lane for sometime now. Why Apple keeps
making things worse and worse instead of
the other way around I don’t know.
In principle, I believe that no LiveCoder should
ever have to be subjected to using the Terminal.
Ideally we should have a st
The URL to start the enrollment process to be an Apple Developer is
https://developer.apple.com/programs/enroll/
Will add that to the lesson, thanks
Kee
> On Nov 9, 2018, at 12:17 PM, Rick Harrison via use-livecode
> wrote:
>
> Hi Kee,
>
> If you had read far enough down on my original messag
Hi Kee,
If you had read far enough down on my original message you
would have seen that I have looked at that lesson.
One of the important things it says is:
To upload to the App Store you need an Apple Developer
account and corresponding developer certificates. This article
does not cover that
Did you try this checklist? If you did and it didn’t work, please let me know
so I can fix it.
Kee Nethery
http://lessons.livecode.com/m/4071/l/876834-signing-and-uploading-apps-to-the-mac-app-store
___
use-livecode mailing list
use-livecode@lists.r
Dear LiveCoders,
I am using LiveCode Indy 9.0.1, Xcode 9.3, and macOS 10.13.6 High Sierra.
I have an old LC 32 bit iOS app that was removed from the App Store
because it was 32 bit. I was so mad at Apple for screwing me on
it that I stayed away from it for quite a while.
Recently I decided tha
17 matches
Mail list logo
