<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 20, 2022, at 6:04 PM, Michael Hall <<a href="mailto:mik3hall@gmail.com" class="">mik3hall@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Sep 20, 2022, at 5:50 PM, Michael Hall <<a href="mailto:mik3hall@gmail.com" class="">mik3hall@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Given that this does break that, one possibility might be to include parameter changes in the Info.plist file. Some time back Apple java applications used to include a java dictionary in the plist that was more or less equivalent to the jpackage .cfg file. Maybe a override mechanism could be added to that which would be up to the developer to add in post processing. </span></div></blockquote></div><br class=""><div class="">Never mind on this. That is no different really from the .cfg file and doesn’t help with changing settings on the installed machine, user or system. </div></div></div></blockquote></div><br class=""><div class="">Alexander,</div><div class=""><br class=""></div><div class="">If you don’t mind a little more opinion on this. When I started trying to figure out what to do with application external files on OS/X I began with the “Application Support” directories. But it occurred to me that most users rarely look at or often possibly aren’t even aware of the “Application Support” directory. So if I thought if I want the user to look at or actively manage a file I'd put it in their Documents directory. </div><div class=""><br class=""></div><div class="">I also thought it might be nice going for different file types possibly on different platforms if you didn’t have to think about what would be the best place to put things. So I tried to come up with an API that would determine the locations for me and all I would indicate would be the data type. Like…</div><div class=""><br class=""></div><div class="">public enum DataTypes {<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * temporary<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>TEMP,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * log file type<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>LOG,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * cache file type<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>CACHE,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * preferences file type<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>PREFERENCES,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * permanent, critical, not user accessible<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>PERMANENT,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * permanent, non-critical, user accessible<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>USER,<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/**<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * <br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> * Documents folder<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span> */<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>DOCUMENTS;<br class="">}</div><div class=""><br class=""></div><div class="">Example usages:</div><div class="">// default path<br class="">path = Application.getApplication().getFolder(DOCUMENTS).resolve("userprefs.xml”);</div><div class="">Although that pretty obviously resolves to the Documents directory.</div><div class=""><br class=""></div><div class="">Or </div><div class="">Path logDir = Application.getApplication().getFolder(LOG);</div><div class=""><br class=""></div><div class="">Where the API determines the best location for log files and you don’t have to be concerned.</div><div class="">Not so clear exactly where that might be, but you don’t really have to worry about it.</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>