Release 5.0.2: appcast

This commit is contained in:
Athanasius committed 2021-05-21 15:32:36 +01:00
1 parent 1e79e59ba9
commit 993d6a8c14
1 file changed
+68 -4
+68 -4
View File
@@ -36,11 +36,75 @@
<!-- Windows -->
<item>
<title>Release 5.0.1</title>
<title>Release 5.0.2</title>
<description>
<![CDATA[
<style>body { font-family:"Segoe UI","Tahoma"; font-size: 75%; } h2 { font-family:"Segoe UI","Tahoma"; font-size: 105%; }</style>
<h2>Release 5.0.2</h2>
<p>This release is primarily aimed at getting the UI "<code>Suit: ...</code>" line working
properly.</p>
<ul>
<li>
<p>The "<code>Suit: ...</code>" UI line should now function as best it can given the
available data from the game. It should not appear if you have launched
the Horizons version of the game, even if your account has Odyssey
enabled. You might see "<code>&lt;Unknown&gt;</code>" as the text when this application
does not yet have the required data.</p>
</li>
<li>
<p>Changed the less than obvious "<code>unable to get endpoint: /profile</code>" error
message to "<code>Frontier CAPI query failure: /profile</code>", and similarly for the
other CAPI endpoints we attempt to access. This new form is potentially
translated, but translators need time to do that.</p>
<p>In addition the old message "<code>Received error {r.status_code} from server</code>"
has been changed to "<code>Frontier CAPI server error: {r.status_code}</code>" and is
potentially translated.</p>
</li>
<li>
<p>The filenames used for 'Market data in CSV format file' will now be sane,
and as they were before 5.0.0.</p>
</li>
<li>
<p>Linux: 'Shipyard provider' will no longer default to showing 'False' if
no specific provider has been selected.</p>
</li>
</ul>
<h2>
<a id="user-content-plugin-developers" class="anchor" href="#plugin-developers" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Plugin Developers</h2>
<ul>
<li>
<p>Extra <code>Flagse</code> values added in the live release of Odyssey have been added to
<code>edmc_data.py</code>.</p>
</li>
<li>
<p>Odyssey 'BackPack' values should now track better, but might still not be
perfect due to Journal bugs/shortcomings.</p>
</li>
<li>
<p><code>state</code> passed to <code>journal_entry()</code> now has a <code>BackpackJSON</code> (note the case)
member which is a copy of the data from the <code>Backpack.json</code> (yes, that's
currently the correct case) file that is written when there's a <code>BackPack</code>
(guess what, yes, that is currently the correct case) event written to
the Journal.</p>
</li>
<li>
<p><code>state['Credits']</code> tracking is almost certainly not perfect. We're
accounting for the credits component of <code>SuitUpgrade</code> now, but there
might be other such we've yet accounted for.</p>
</li>
<li>
<p><code>state['Suits']</code> and associated other keys should now be tracking from
Journal events, where possible, as well as CAPI data.</p>
</li>
<li>
<p>There is a section in PLUGINS.md about how to package an extra Python
module with your plugin. Note the new caveat in
<a href="./PLUGINS.md#avoiding-potential-pitfalls">PLUGINS.md:Avoiding-pitfalls</a>
about the name of your plugin's directory.</p>
</li>
</ul>
<h2>Release 5.0.1</h2>
<p>The main reason for this release is to add an 'odyssey' boolean flag to all
EDDN messages for the benefit of listeners, e.g. eddb.io, inara.cz,
@@ -525,11 +589,11 @@ about this:
]]>
</description>
<enclosure
url="https://github.com/EDCD/EDMarketConnector/releases/download/Release/5.0.1/EDMarketConnector_win_5.0.1.msi"
url="https://github.com/EDCD/EDMarketConnector/releases/download/Release/5.0.2/EDMarketConnector_win_5.0.2.msi"
sparkle:os="windows"
sparkle:installerArguments="/passive LAUNCH=yes"
sparkle:version="5.0.1"
length="10194944"
sparkle:version="5.0.2"
length="10190848"
type="application/octet-stream"
/>
</item>