Re: info.plist

2017-10-29 Thread David Adams via 4D_Tech
I've been working with BUILD APPLICATION a lot lately, so a couple of notes:

* 4D _will_ record an error in the log if the path to the license files is
wrong or, for a built single-user app, the path to the engine is wrong.

* 4D will _not_ record an error if the path to your custom icons is wrong.

* It's not that hard to clear out extra resources after a build, like .xlf
files and so on.

* 4D has a tech tip about clearing out the SVG component help file which
has a helpful description of the file paths for compiled databases and
merged apps.

* Go ahead and clear out the /Cache folders from within Components,
Plugins, and Resources after the build. They can contain 100s of MB of
stuff and you don't need it.

Check the archives for some past tips and code from Tim Nevels on tweaking
the info/about details. There are several different build keys you can use:

Tip: I also like to onboard a small build_info.json file after the build.
It's got details that I might want to read out about the build itself for
error logs, about boxes, error reports, etc. This isn't part of the
standard build project file but it's easy to implement.


I'd be very interested to hear what other people clear out post-build.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: info.plist

2017-10-29 Thread Jeremy Roussak via 4D_Tech
Thanks, Spencer. I was right: I was indeed missing something obvious!

Jeremy


Jeremy Roussak
j...@mac.com

On 29 Oct 2017, 10:24 +, Spencer Hinsdale via 4D_Tech 
<4d_tech@lists.4d.com>, wrote:
> http://doc.4d.com/4Dv16/4D/16/4D-XML-Keys-BuildApplication.100-3130124.en.html
>
>
> > On Oct 29, 2017, at 1:31 AM, Jeremy Roussak via 4D_Tech 
> > <4d_tech@lists.4d.com> wrote:
> >
> > I’m sure I’m missing something obvious (and I think I’ve managed to solve 
> > the issue in the past), but…
> >
> > How do I tell 4D to put stuff into the info.plist file for a built 
> > application? I’m particularly interested in version strings.
> >
> > Mac, 4Dv14.
> >
> > Thanks.
> >
> > Jeremy
> >
> >
> > Jeremy Roussak
> > j...@mac.com
> >
> >
> >
> > **
> > 4D Internet Users Group (4D iNUG)
> > FAQ: http://lists.4d.com/faqnug.html
> > Archive: http://lists.4d.com/archives.html
> > Options: http://lists.4d.com/mailman/options/4d_tech
> > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> > **
> **
> 4D Internet Users Group (4D iNUG)
> FAQ: http://lists.4d.com/faqnug.html
> Archive: http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> **
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: info.plist

2017-10-29 Thread Spencer Hinsdale via 4D_Tech
http://doc.4d.com/4Dv16/4D/16/4D-XML-Keys-BuildApplication.100-3130124.en.html


> On Oct 29, 2017, at 1:31 AM, Jeremy Roussak via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> I’m sure I’m missing something obvious (and I think I’ve managed to solve the 
> issue in the past), but…
> 
> How do I tell 4D to put stuff into the info.plist file for a built 
> application? I’m particularly interested in version strings.
> 
> Mac, 4Dv14.
> 
> Thanks.
> 
> Jeremy
> 
> 
> Jeremy Roussak
> j...@mac.com
> 
> 
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

info.plist

2017-10-29 Thread Jeremy Roussak via 4D_Tech
I’m sure I’m missing something obvious (and I think I’ve managed to solve the 
issue in the past), but…

How do I tell 4D to put stuff into the info.plist file for a built application? 
I’m particularly interested in version strings.

Mac, 4Dv14.

Thanks.

Jeremy


Jeremy Roussak
j...@mac.com



**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**