extended finder attributes cause code sign to fail, but of course, clearing
them with xattr mean little if the app is not signed in the first place.
basically,
if you don’t sign a built application, you have no choice but to ask the end
user to disable gate keeper for the app, and install it
Hi James,
I agree with what Chuck Miller posted (I think he was quoting my reply to your
previous thread: http://kb.4d.com/resources/inug?msgid=GmailId1607a1da70d0a99b).
Definitely start signing your application if you are not already doing so - and
then make sure to distribute your signed
to be clear,
you don't need a "v16" SDK to support v16 or v16 R releases.
the SDK version is only bumped when there is a major change to the architecture,
in my 10+ years of using it,
that has only happened 4 times:
v2004 (mach-o bundle)
v11 (unicode mode)
v12 (64-bit for windows)
v14 (64-bit
One thing I would for sure do is get your application signed so you do not
get into instance where OS won’t lety it run. Here are notes from
My assumption is that the application is falling victim to Gatekeeper and
being translocated to a read-only location. Apple documents how to get
around
They just announced (on the forums) that it will be available on github.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Jan 30, 2018, at 3:32 PM, Seth Leeper via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> To the best of my knowledge, 4D has not released the v16 SDK.
I’ve never managed to find a reliable way of installing a built application on
our client Macs.
Our network is 15 Macs running latest versions of 10.10 or 10.12. 4D is version
15.5 and I’m compiling an app using 4D Volume Desktop. The data is all stored
in a MySQL database, accessed via the
Unfortunately, Orchard has made the decision to only support base releases in
the Win32API and not R releases.
As Peter mentioned, the code will remain freely available to the 4D community
to modify as needed.
To the best of my knowledge, 4D has not released the v16 SDK.
Regards,
Seth Leeper
On Jan 30, 2018, at 2:00 PM, Jim Dorrance wrote:
> Find a mac mini late 2012 i7 with ssd and 16 gb ram
I agree. This is a fantastic little machine for running 4D Server on with under
20 users and a “medium sized” data file.
This is how I currently categorized 4D data file sizes:
Small is
v13 docs do not specify a limit to the pairings, but other commands
(Query) have (or had) limits even without an acknowledgment from 4D.
the '*' in this instance does not negate the need for Execute Formula,
I considered that option.
Thanks
On Tue, 30 Jan 2018 20:32:56 +0100, Arnaud de Montard
> Le 29 janv. 2018 à 20:01, Douglas von Roeder via 4D_Tech
> <4d_tech@lists.4d.com> a écrit :
>
> Chip:
>
> Perhaps the optional asterisk has removed that limit?
Asterisk could also remove the need to use Execute Formula…
--
Arnaud de Montard
10 matches
Mail list logo
