<p>GResources sounds like a very good idea, but I also proposed in the other post, that the paths, instead of being constants generated by prefix during ./configure, are completely replaced in all of the source code, with GetDataPath() function, and then you just add that function in some central place, and it uses $PATH-like loginc to test few paths according to priority:</p>
<ol>
<li>path specified by the prefix (current), if not found then</li>
<li>path relative to user's home folder ($HOME), if still not then</li>
<li>path relative to the folder of the executable (argv[0])</li>
</ol>
<p>Also, optionally, an environmental variable could also be tested in that function and give, for example highest priority.</p>
<p>Conceptually it feels sound to me, and if Geany source code is fairly well structured, or if someone knows it well, should be an easy task as well.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1702#issuecomment-348679823">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ7bbGuQq_MRFbqqeKoZQlVu0UyJTks5s8Rc7gaJpZM4Qy55n">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJz6oN_2sb22qOWjhR2zhXCV3ZQlaks5s8Rc7gaJpZM4Qy55n.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1702#issuecomment-348679823"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@krisjace in #1702: GResources sounds like a very good idea, but I also proposed in the other post, that the paths, instead of being constants generated by prefix during ./configure, are completely replaced in all of the source code, with GetDataPath() function, and then you just add that function in some central place, and it uses $PATH-like loginc to test few paths according to priority:\r\n1. path specified by the prefix (current), if not found then\r\n2. path relative to user's home folder ($HOME), if still not then\r\n3. path relative to the folder of the executable (argv[0])\r\n\r\nAlso, optionally, an environmental variable could also be tested in that function and give, for example highest priority.\r\n\r\nConceptually it feels sound to me, and if Geany source code is fairly well structured, or if someone knows it well, should be an easy task as well."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1702#issuecomment-348679823"}}}</script>