I switched back to folders for development. It's easier to manipulate the
app's supporting folders and files. Users get a package, but like Chip said,
you have to guard against the unintentional use of the datafile within the
package.
Keith - CDI
> On Oct 19, 2017, at 5:41 PM, Robert ListMai
Other issue with package systems:
- data file can be unintentionally replaced/lost during an update to the
structure/package.
ex: client copies new structure/package to old location overwriting existing
structure/package -- datafile (other items(?)) LOST!
I understand the idea - but I always mov
I think the difference is largely cosmetic,
but spotlight might fail to locate files inside a package.
(resources, for example)
> 2017/10/20 7:41、Robert ListMail via 4D_Tech <4d_tech@lists.4d.com> のメール：
> Regarding best practices, what approach do you favor? Do we like packages? :)
**
It seems like most of my Mac-based 4D databases are in a folder with the
structure and datafile on the same level and where there might be a test data
file in folder elsewhere. Yet, I have a few newly inherited Mac-based databases
that are in packages. Regarding best practices, what approach do
4 matches
Mail list logo
