Skip to content

Commit

Permalink
Add more explanation for WLeafletMap to release notes, added _blank t…
Browse files Browse the repository at this point in the history 
…o some <a>s
  • Loading branch information
@RockinRoel
RockinRoel committed Jul 17, 2019
1 parent 3c99bb3 commit 62b2e63
Showing 1 changed file with 19 additions and 16 deletions.
35 changes: 19 additions & 16 deletions ReleaseNotes.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ <h3>Notable backwards-incompatible changes</h3>
<a href="classWt_1_1WApplication_1_1UpdateLock.html#a09011389bb0b9319acbcd32800852918">WApplication::UpdateLock::operator bool()</a> and
<a href="classWt_1_1Core_1_1observing__ptr.html#a93ae9f0dd2a1553dc081faad7e1078ee">observing_ptr::operator bool()</a> were made <tt>explicit</tt>,
so they will no longer implicitly convert to <tt>bool</tt>, only
<a href="https://en.cppreference.com/w/cpp/language/implicit_conversion#Contextual_conversions">contextually</a>.
<a href="https://en.cppreference.com/w/cpp/language/implicit_conversion#Contextual_conversions" target="_blank">contextually</a>.
This may cause some valid code to no longer compile, but it is more likely that it will actually uncover bugs.
</li>
<li>
Expand All @@ -67,13 +67,16 @@ <h3>Notable backwards-incompatible changes</h3>
</ul>
<h3>New widgets</h3>
<ul>
<li><b><a href="classWt_1_1WLeafletMap.html">WLeafletMap</a></b>: this is a wrapper around the <a href="https://leafletjs.com/">Leaflet</a>
JavaScript library.</li>
<li>
<a href="classWt_1_1WLeafletMap.html">WLeafletMap</a>: this is a wrapper around the <a href="https://leafletjs.com/" target="_blank">Leaflet</a>
JavaScript library. It has support for some basic features of Leaflet, and one special feature: the ability to add arbitrary
widgets (within reason) as markers to the map using <a href="classWt_1_1WLeafletMap_1_1WidgetMarker.html">WidgetMarker</a>.
</li>
</ul>
<h3>New examples</h3>
<ul>
<li>
Added a <a href="classWt_1_1WLeafletMap.html">WLeafletMap</a> example to the <a href="https://www.webtoolkit.eu/widgets/graphics-charts/leaflet-maps">widget gallery</a>
Added a <a href="classWt_1_1WLeafletMap.html">WLeafletMap</a> example to the <a href="https://www.webtoolkit.eu/widgets/graphics-charts/leaflet-maps" target="_blank">widget gallery</a>
and in <tt>examples/leaflet</tt>.
</li>
<li>
Expand Down Expand Up @@ -134,10 +137,10 @@ <h3>Dbo</h3>
no reasonable "null" value. Use <tt>std::optional</tt> or <tt>boost::optional</tt> to make them nullable instead.
</li>
<li>
Fixed a query corruption bug when using <tt>UNION</tt>, <tt>INTERSECT</tt>, or <tt>EXCEPT</tt> (<a href="https://redmine.webtoolkit.eu/issues/7028">issue #7028</a>).
Fixed a query corruption bug when using <tt>UNION</tt>, <tt>INTERSECT</tt>, or <tt>EXCEPT</tt> (<a href="https://redmine.webtoolkit.eu/issues/7028" target="_blank">issue #7028</a>).
</li>
<li>
Fixed a crash when using <tt>Session::dropTables()</tt> while there is an active transaction, <a href="https://redmine.webtoolkit.eu/boards/2/topics/16123">as reported on the forum</a>.
Fixed a crash when using <tt>Session::dropTables()</tt> while there is an active transaction, <a href="https://redmine.webtoolkit.eu/boards/2/topics/16123" target="_blank">as reported on the forum</a>.
</li>
<li>
PostgreSQL uses <tt>?</tt> for some operators, but that is also the character we use for placeholders in prepared statements. If the literal <tt>?</tt> is meant instead of a placeholder, you can now use <tt>??</tt>. This is similar to how PostgreSQL's JDBC driver handles it.
Expand Down Expand Up @@ -169,7 +172,7 @@ <h3>Miscellaneous features</h3>
<a href="classWt_1_1WWidget.html#a1f5151154770b4956b4870cb4ecc38d3">removeWidget()</a> and <a href="classWt_1_1WObject.html#a00f32a263b742f42b73a9353eaa3c7ca">removeChild()</a> now return a more concrete <tt>std::unique_ptr</tt>, for convenience. Also added a similar <a href="classWt_1_1WFitLayout.html#a071ea55ea16e71213b3bbd2f5f497932">WFitLayout::addWidget()</a>.
</li>
<li>
Wt's widget coordinate calculation code now uses <a href="https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect">getBoundingClientRect()</a>, which means that coordinate calculations are still accurate even when CSS transforms are used to position widgets. This was necessary for <a href="classWt_1_1WLeafletMap_1_1WidgetMarker.html">WidgetMarker</a> support.
Wt's widget coordinate calculation code now uses <a href="https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect" target="_blank">getBoundingClientRect()</a>, which means that coordinate calculations are still accurate even when CSS transforms are used to position widgets. This was necessary for <a href="classWt_1_1WLeafletMap_1_1WidgetMarker.html">WidgetMarker</a> support.
</li>
<li>
<a href="classWt_1_1WTemplate.html">WTemplate</a>'s <a href="structWt_1_1WTemplate_1_1Functions.html#ab070ae026639fb7edc0c70db6510abc7">while_f</a> function now takes extra arguments, similar to the <a href="structWt_1_1WTemplate_1_1Functions.html#a734f46b7a8155cbc6cf0407dd3dbe85d">block</a> function.
Expand All @@ -186,15 +189,15 @@ <h3>Miscellaneous features</h3>
<h3>Miscellaneous bug fixes</h3>
<ul>
<li>Fixed an issue where JavaScript could be sent to the browser in the wrong order when doing background updates of hidden widgets
(<a href="https://redmine.webtoolkit.eu/issues/7023">issue #7023</a>)</li>
<li>Fixed a client side memory leak caused by misuse of jQuery's data feature (<a href="https://redmine.webtoolkit.eu/boards/2/topics/15941">reported on the forums</a>)</li>
(<a href="https://redmine.webtoolkit.eu/issues/7023" target="_blank">issue #7023</a>)</li>
<li>Fixed a client side memory leak caused by misuse of jQuery's data feature (<a href="https://redmine.webtoolkit.eu/boards/2/topics/15941" target="_blank">reported on the forums</a>)</li>
<li><a href="classWt_1_1WTableView.html">WTableView</a>: fixed row deletion behavior</li>
<li>Fixed icons not showing up on tabs and menu items when using <a href="classWt_1_1WBootstrapTheme.html">WBootstrapTheme</a>, as <a href="https://redmine.webtoolkit.eu/boards/1/topics/15664">reported on the forums</a>.</li>
<li>Fixed wrong <a href="classWt_1_1WStackedWidget.html">WStackedWidget</a> height when animating transitions (<a href="https://redmine.webtoolkit.eu/issues/6788">issue #6788</a>)</li>
<li>Fixed not able to hide widgets with a flexbox-based layout (<a href="https://redmine.webtoolkit.eu/issues/6884">issue #6884</a>)</li>
<li>Fixed out of bounds array access when using a widget with a custom HTML tag name (<a href="https://redmine.webtoolkit.eu/issues/7059">issue #7059</a>). Widgets will now derive whether they are default inline based on the widget's default DOM element type.</li>
<li>Fixed icons not showing up on tabs and menu items when using <a href="classWt_1_1WBootstrapTheme.html">WBootstrapTheme</a>, as <a href="https://redmine.webtoolkit.eu/boards/1/topics/15664" target="_blank">reported on the forums</a>.</li>
<li>Fixed wrong <a href="classWt_1_1WStackedWidget.html">WStackedWidget</a> height when animating transitions (<a href="https://redmine.webtoolkit.eu/issues/6788" target="_blank">issue #6788</a>)</li>
<li>Fixed not able to hide widgets with a flexbox-based layout (<a href="https://redmine.webtoolkit.eu/issues/6884" target="_blank">issue #6884</a>)</li>
<li>Fixed out of bounds array access when using a widget with a custom HTML tag name (<a href="https://redmine.webtoolkit.eu/issues/7059" target="_blank">issue #7059</a>). Widgets will now derive whether they are default inline based on the widget's default DOM element type.</li>
<li>Fixed a regression in <a href="classWt_1_1WDate.html#a6d604c9c4409729abbe4a334c4d69368">WDate::addMonths()</a> and <a href="classWt_1_1WDate.html#ab03f57a16749501343b8368047199002">addYears()</a>, introduced in Wt 4.0.0. When a day would not exist in the resulting month, this would yield an invalid month. Instead, it will now (as it did in Wt 3) set the date to the last day of that month, e.g. May 31, 2019 + 6 months becomes November 30, 2019.</li>
<li>Fixed an issue where mouse signals of a <a href="classWt_1_1WTreeView.html">WTreeView</a> would fire multiple times (<a href="https://redmine.webtoolkit.eu/issues/6260">issue #6260</a>)</li>
<li>Fixed an issue where mouse signals of a <a href="classWt_1_1WTreeView.html">WTreeView</a> would fire multiple times (<a href="https://redmine.webtoolkit.eu/issues/6260" target="_blank">issue #6260</a>)</li>
<li>
wthttp WebSocket fixes:
<ul>
Expand All @@ -203,8 +206,8 @@ <h3>Miscellaneous bug fixes</h3>
</li>
<li>
WebSocket messages with continuation frames (as sent by Google Chrome when the messages become very large) could become corrupted,
especially when per-message-deflate is used (<a href="https://redmine.webtoolkit.eu/issues/7039">issue #7039</a>,
<a href="https://redmine.webtoolkit.eu/issues/7034">#7034</a>).
especially when per-message-deflate is used (<a href="https://redmine.webtoolkit.eu/issues/7039" target="_blank">issue #7039</a>,
<a href="https://redmine.webtoolkit.eu/issues/7034" target="_blank">#7034</a>).
</li>
<li>
WebSocket message size is now properly limited by <tt>--max-memory-request-size</tt>. Previously, this would only limit the size
Expand Down

0 comments on commit 62b2e63

Please sign in to comment.