forked from emweb/wt
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathReleaseNotes.html
3621 lines (3145 loc) · 130 KB
/
ReleaseNotes.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1" />
<style type="text/css">
dt { font-weight: bold; }
h3 { text-decoration: underline; }
dd { margin-top: 10px; margin-bottom: 10px; }
dd p { margin-top: 0px; }
dd div { margin: 10px 0px; }
</style>
<title>Wt Release notes</title>
</head>
<body>
<h1>Wt Release notes</h1>
This file lists important notes on migrating existing applications to
newer version of Wt. It lists changes in the library that may break
the way you build Wt, the way you configure Wt or the Wt API and
behaviour.
<h2>Release 3.3.0 (March, ? 2013)</h2>
<p>
This release focusses on a reorganization of Wt's theme
infrastructure, with the objective of
supporting <a href="http://twitter.github.com/bootstrap/">Twitter's
Bootstrap CSS framework</a> as a new theme. At the same time we've
added a number of widgets for which Twitter Bootstrap provides
styling.
</p>
<p>It is our intention to support the Bootstrap theme (or more
specifically, the Bootstrap class names) alongside the themes we
already supported (which are based on our own class names). Ignoring
what Bootstrap brings, you should be able to upgrade to this release
without too much trouble, although you may need to adapt some CSS
stylesheets as we did reorganize a number of things which were
required for Bootstrap and were a good idea for our own CSS
stlesheets too.</p>
<h3>A) New classes:</h3>
<dl>
<dt>
<a href="classWt_1_1WTheme.html">WTheme</a>,
<a href="classWt_1_1WCssTheme.html">WCssTheme</a>,
<a href="classWt_1_1WBootstrapTheme.html">WBootstrapTheme</a>,
</dt>
<dd>
Theme support classes for Wt. The role of a theme is to:
<ul>
<li>Load the CSS stylesheets for a new session</li>
<li>Annotate newly created widgets with appropriate style
classes</li>
</ul>
</dd>
<dt>
<a href="classWt_1_1WDateEdit.html">WDateEdit</a>
</dt>
<dd>
Functionally almost the same as a WDatePicker, this class
specializes WLineEdit and is thus a WFormWidget, making it much
easier to use in WTemplateFormView.
</dd>
<dt>
<a href="classWt_1_1WLocale.html">WLocale</a>
</dt>
<dd>
This class supports localization for number formatting and
extends the simple localization support we had in the previous
versions of Wt (which as only effect had the selection of
a different language for the resource bundles). It's main
added value of native C++ support for localization is that it
also affects client-side handling and parsing of number values,
i.e. in <a href="classWt_1_1WIntValidator.html">WIntValidator</a> and
<a href="classWt_1_1WDoubleValidato.htmlr">WDoubleValidator</a>.
</dd>
<dt>
<a href="classWt_1_1WNavigationBar.html">WNavigationBar</a>
</dt>
<dd>
A navigation bar styles a menu as a typical top-level bar
(currently only styled in the Bootstrap Theme).
</dd>
<dt>
<a href="classWt_1_1WPopupWidget.html">WPopupWidget</a>
</dt>
<dd>
A base class to simplify the creation of popup widgets that
typically assist in editing or provide circumstancial information
for another widget.
</dd>
<dt>
<a href="classWt_1_1WSplitButton.html">WSplitButton</a>
</dt>
<dd>
A split button, which combines a button and a popup menu
(currently only styled in the Bootstrap Theme).
</dd>
<dt>
<a href="classWt_1_1WToolBar.html">WToolBar</a>
</dt>
<dd>
A button tool bar (currently only styled in the Bootstrap Theme)
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1backend_1_1MySQL.html">Dbo::MySQL</a>
</dt>
<dd>
A MariaDB/MySQL backend for Wt::Dbo. This is based on the work
from Paul Harrisson who maintained this backend so far outside the
Wt distribution. The backend has been designed for MariaDB, but
should work fine for MySQL as well.
</dd>
</dl>
<h3>B) Main improvements:</h3>
<dl>
<dt>
<a href="classWt_1_1Mail_1_1Message.html">Mail::Message</a>
</dt>
<dd>
Added API support for additional SMTP headers.
</dd>
<dt>
<a href="classWt_1_1WDatePicker.html">WDatePicker</a>,
<a href="classWt_1_1WSuggestionPopup.html">WSuggestionPopup</a>
</dt>
<dd>
The setGlobalPopup() functionality has been deprecated and does no
longer have any effect, since a new improved algorithm is being
used to anchor the popup to the DOM which no longer requires this
workaround.
</dd>
<dt>
<a href="classWt_1_1WDialog.html">WDialog</a>
</dt>
<dd>
Addition of a footer() method that returns a container for dialog
footer elements, typically buttons.
</dd>
<dt>
<a href="classWt_1_1WFormModel.html">WFormModel</a>
</dt>
<dd>
Addition of a validator() function that returns the validator for
a field set using setValidator(),
</dd>
<dt>
<a href="classWt_1_1WGLWidget.html">WGLWidget</a>
</dt>
<dd>
Support for binary transfers which avoids serialization and
deserialization of floats to text.
</dd>
<dt>
<a href="classWt_1_1WPushButton.html">WPushButton</a>
</dt>
<dd>
A push button can now act as a toggle button, using setCheckable()
and related API (currently only styled in the Bootstrap Theme) and
can be linked to a popup menu using setMenu().
</dd>
<dt>
<a href="classWt_1_1WStackedWidget.html">WStackedWidget</a>
</dt>
<dd>
When switching between current widgets, the stacked widget will
now record and restore the current scroll position, providing a
much improved user experience when using the stacked widget for
the 'main' contents of an application.
</dd>
<dt>
<a href="classWt_1_1WStringListModel.html">WStringListModel</a>
</dt>
<dd>
Full support was added for storing data of all roles, lifting the
requirement to use another model such as WStandardItemModel for
simple MVC widgets like WComboBox or WSuggestionPopup simply to be
able to store UserRole data.
</dd>
<dt>
<a href="classWt_1_1WTemplate.html">WTemplate</a>
</dt>
<dd>
Added a new standard function (Functions::block) which allows the
definition and use of a macro block inside a placeholder, which is
in particular useful for forms which have repetitive formatting
for each field.
</dd>
<dt>
<a href="classWt_1_1WTemplateFormView.html">WTemplateFormView</a>
</dt>
<dd>
Several API improvements: A new setFormWidget() allows the
definition of the form widget for editing a field which
is a more useful alternative compared to reimplement
createFormWidget(). It also allows the optional
definition of functions to update the view/model values, which
avoids the need for specializing updateViewField() and
updateModelField() these latter two functions have been deprecated
in favour of two new functions updateViewValue() and
updateModelValue() which only update the value but not other
aspects such as visibility, validation state, or messages.
</dd>
<dt>
Built-in httpd improvements
</dt>
<dd>
A redundant copy operation of the response generated and sent by
Wt has been removed, using scatter-gather I/O implemented by
boost::asio instead.
</dd>
</dl>
<h3>C) Non-backwards compatible changes</h3>
<dl>
<dt>
<a href="classWt_1_1WMenuItem.html">WMenuItem</a>
</dt>
<dd>
While in previous version of Wt, this class was only a data class
that held the information related to an item, in 3.3.0 we modified
this so that this class represents the widget itself. If you were
redefining protected methods to customize the widget
(i.e. createItemWidget() and updateItemWidget()), then this will no
longer work as expected. The new system should be easier to
customize (since you can simply specialize WMenuItem itself).
In addition, we've simplified the rendering of a menu item so that
a redundant layer of spans (or div's) has been removed. It makes
the menu more consistent with the way CSS designers expect a menu
to rendered, and this was done (you can guess the theme of this
release by now ?) to be compatible with bootstrap's CSS styles.
</dd>
<dt>
<a href="classWt_1_1WApplication.html">WApplication::locale()</a>
</dt>
<dd>
This now returns a WLocale object instead of the string
designation of the locale (which you can query by calling name())
on the locale object.
</dd>
<dt>
<a href="classWt_1_1WCalendar.html">WCalendar</a>
</dt>
<dd>
The markup for this class has changed, and thus customized CSS
will need to be updated.
</dd>
<dt>
<a href="classWt_1_1WMenuItem.html">WPopupMenuItem</a>
</dt>
<dd>
The popup menu item class has been merged with WMenuItem (and
WPopupMenu is now a specialized WMenu). This should not have
noticable API changes, except for the changes in markup and CSS
documented above.
</dd>
<dt>
<a href="classWt_1_1WTreeNode.html">WTreeNode</a>,
<a href="classWt_1_1WTreeTable.html">WTreeTable</a>
<a href="classWt_1_1WTreeView.html">WTreeView</a>
</dt>
<dd>
The markup for tree rendering has been changed (to using nested
unordered list instead of nested tables), and thus customized CSS
will need to be updated. The only API consequence is that
WTreeNode::labelArea() is no longer returning a WTableCell but
instead a WContainerWidget.
</dd>
<dt>
<a href="classWt_1_1WTreeView.html">WTreeView</a>,
<a href="classWt_1_1WTableView.html">WTableView</a>
</dt>
<dd>
Event handling (clicked(), doubleClicked(), ... ) has been
generalized: events that are not generated on an item (but for
example in empty space below the items) will now also
generate these events, but then with an invalid model index.
You may thus need to adapt current code to check whether the model
index that is returned is valid.
</dd>
</dl>
<hr>
<h2>Release 3.2.3 (November, 1 2012)</h2>
<p>
This release contains mostly bug fixes and one new feature: a payment
processing API.
</p>
<h3>A) New namespaces:</h3>
<dl>
<dt>
<a href="group__payment.html">Wt::Payment (payment handling)</a>
</dt>
<dd>
This namespace contains services and back-end classes for dealing
with online payment brokers. At the moment there is support for
PayPal's Express Checkout service.
</dd>
</dl>
<h3>B) Main improvements:</h3>
<dl>
<dt>
Layout improvements.
</dt>
<dd>
<p>
If you had massive trouble migrating to 3.2.2 because of the
layout rewrite, then you'll appreciate the efforts we've made to
make the layout algorithms in 3.2.3 much more robust and
consistent.
</p>
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1QueryModel.html">Dbo::QueryModel</a>:
added a mechanism for stable row data.
</dt>
<dd>
<p>
A common nuisance when working with the QueryModel (which
retrieves data from the database as needed), is that concurrent
database modifications such as insertions of new data, may
interfere with the model's mapping of rows to objects (this is
in fact a common problem with most ORM's indeed). This mapping
may be important, especially when you want to process the user's
selection of one or more rows selected by the user, in e.g. a
table view. We've added a mechanism to assure that one can
request the model for data at a given row, which is guaranteed
to be the same row that has been previously retrieved, using the
stableResultRow() method. It works by default for simple queries
(returning data from one table), but can be easily customized
for more complex queries.
</p>
</dd>
<dt>
<a href="namespaceWt_1_1Render.html">Render library:</a>
improved support for %-based block sizes and table rendering
</dt>
<dd>
<p>
Support was added for %-based sizes for block widths and table
cell widths. In addition, table rendering in Wt::Render has been
improved to support repeating headers (<thead> sections)
for multi-page tables, and explicit page breaks (using the css
page-break-after/before properties).
</p>
</dd>
</dl>
<h3>C) Non-backwards compatible changes</h3>
<dl>
<dt>
<a href="classWt_1_1Dbo_1_1backend_1_1Sqlite3.html">Dbo::backend::Sqlite3</a>
</dt>
<dd>
<p>We've changed the implementation of the storage ISO8601AsText
format for time stamps (datetime). In the new, corrected,
implementation, we generate dates using 'T' as the separator
between date and time (as mandated by ISO8601), while the old
behaviour used a space (' ') instead as the
separator. Sqlite3 supports either format equally. This may
however break some applications which use queries for an exact
date (or a date comparison), as the results may be affected.
</p>
<p> The old behaviour is still available as PseudoISO8601AsText,
which can be configured using
<tt>connection.setDateTimeStorage(Wt::Dbo::SqlDateTime,
Wt::Dbo::backend::Sqlite3::PseudoISO8601AsText)</tt>
</p>
</dd>
<hr>
<h2>Release 3.2.2 (July, 23 2012)</h2>
<p>
This release contains mostly bug and feature improvements, but
also a rewrite of the layout managers in Wt (WBoxLayout and
WGridLayout), and this comes with some changes in (in most cases
previously undefined) behaviour.
</p>
<h3>A) New classes:</h3>
<dl>
<dt>
<a href="classWt_1_1WSslInfo.html">WSslInfo</a>
</dt>
<dd>
Class containing information on a client-side certificate that may
have been configured for a SSL connection, and which can be used
for authentication (accessible from
<a href="classWt_1_1WEnvironment.html">WEnvironment</a>).
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1weak__ptr.html">Wt::Dbo::weak_ptr</a>
</dt>
<dd>
A weak variant of Wt::Dbo::ptr which is used to implement
One-to-One relations (see also
<a
href="group__dbo.html#ga00a060d5f4764f673948989f21837548">Wt::Dbo::hasOne()
</a>).
</dd>
</dl>
<h3>B) Main improvements:</h3>
<dl>
<dt>
Rewrite of <a href="classWt_1_1WLayout.html">WBoxLayout, WGridLayout</a>
</dt>
<dd>
<p>
The layout managers have been reimplement, to address various
issues with the old implementation, including API (in particular the wonked
side-effects of AlignTop | AlignJustify) inconsistencies and bugs.
</p>
<p>The new implementation no longer uses tables when JavaScript
is available, but instead using JavaScript-based layout with
absolute positioning. The table-based implementation is still kept
for plain HTML sessions (and progressive bootstrap). The code now
uses exactly the same layout logic for both horizontal and
vertical layout (but giving precedence to horizontal layout) and
should be much more consistent (and perhaps also more
performant). However, because of the many complexities and
problems with the old code (inconsistent behaviour), you may see
issues while upgrading. Please see the "Non-backwards compatible
changes" below for hints on how to deal with this.</p>
</dd>
<dt>
<a href="classWt_1_1WAbstractItemView.html">WAbstractItemView</a>
</dt>
<dd>
<p>
A drag & drop mime-type can now be specified on a per-item
basis using a new <a
href="group__modelview.html#ga0ae864e12320f9f89172735e075ed068">ItemDataRole</a>,
and the mime-type for the entire selection is computed
from these individual mime-types.
</p>
</dd>
<dt>
<a href="classWt_1_1WInteractWidget.html">WInteractWidget</a>
</dt>
<dd>
A new method <a href="classWt_1_1WInteractWidget.html#a60423e777cffa89e6d1373fd25754099">setMouseOverDelay()</a> allows to specify a delay for
generating the mouseWentOver() event.
</dd>
<dt>
<a href="classWt_1_1Auth_1_1AbstractUserDatabase.html">Auth::AbstractUserDatabase</a>
</dt>
<dd>
A new method <a href="classWt_1_1Auth_1_1AbstractUserDatabase.html#a5067e569748cfad8c3356735a33aa10f">deleteUser()</a> was added, which deletes a user and all
related authentication information.
</dd>
<dt>
<a href="classWt_1_1Chart_1_1WCartesianChart.html">Chart::WCartesianChart</a>
</dt>
<dd>
A new method <a href="classWt_1_1Chart_1_1WCartesianChart.html#aa6c394c4d9a801d088b7b02c3fd66b28">setAxisPadding()</a> was added, which configures the
amount of adding between the chart area and the axes.
</dd>
<dt>
<a href="classWt_1_1Chart_1_1WDataSeries.html">Chart::WDataSeries</a>
</dt>
<dd>
A new method <a href="classWt_1_1Chart_1_1WDataSeries.html#ab0dbcd9bcbc0f39a042eb36aa930def4">setCustomMarker()</a> was added which allows the use of a
user-defined path for the markers. A new role
MarkserScaleFactorRole was added which allows overriding the
marker size based on item model data.
</dd>
</dl>
<h3>C) Non-backwards compatible changes</h3>
<dl>
<dt>
<a href="classWt_1_1WLayout.html">WBoxLayout, WGridLayout</a>
</dt>
<dd>
While migrating old code to this version, here are some tips:
<ol>
<li><p>Alignment flags</p>
<p>Previously, specifying an alignment for a widget in a
layout, or for the layout when set to a container, had a double
meaning. Not only would it implement the given alignment but also
revert to passively letting HTML layout decide the layout of the
contents, and adjust the parent (layout respectively container)
accordingly. This had all kinds of side effects such as not
propagating the size of layout-size-aware widgets and quirks in
the vertical alignment.</p>
<p><a href="classWt_1_1WContainerWidget.html#aff9884c8efdf90974077e96bcb1701db">WContainerWidget::setLayout(layout, alignment)</a> has been
deprecated and will be removed from a future release. This call
was almost always used to let the parent container resize to fit
the size of the contained children, instead of fitting children
in the parent container. This behaviour is now
automatically deduced based on an (empty) size of the parent
container. In case this heuristic does not work, then setting a
non-0 maximum size on the container using <a href="classWt_1_1WWebWidget.html#a9b83805a5b8090d296ae4b5939fc9d11">setMaximumSize()</a> will
act as a trigger, with the added benefit that the parent will only
be allowed to resize up to a specified maximum size.</p>
<p>An alignment specified in
<a href="classWt_1_1WBoxLayout.html#a7c1ec58e25d0b7add93f5f4342844db6">W(Box/Grid)Layout::addWidget(widget, stretch, alignment)</a> now
purely affects the alignment but has no other side effects. The
perferred and minimum sizes of a child widget or layout is now
always taken into account.</p>
</li>
<li><p>Child item sizes</p>
<p>The layout algorithm is now implemented entirely in
JavaScript, and is more gentle when dealing with a combination
of cells (or columns/rows) that have a stretch factor and others
that don't. Previously, a minimum (or fixed) size would be used
to layout items that do not have a stretch factor. This had for
example as a consequence that a WText would be narrowed down to its
minimum width by using word wrapping throughout. Now, the
preferred size is used for a child item, and shrinking to a minimum
size only if necessary.</p>
<li><p>Progressive bootstrap</p>
A layout in the first page of an application rendered using
progressive bootstrap will no longer fully upgrade to a full
JavaScript version, but will result in a hybrid (between
table-based and JavaScript-based). If it doesn't work out as you'ld
expect, then you should reconsider the use of progressive bootstrap,
or the use of a layout manager in your first page.
</li>
</ol>
</dd>
</dl>
<hr>
<h2>Release 3.2.1 (March 16, 2012)</h2>
<p>
This release contains mostly bug and feature improvements.
</p>
<h3>A) New classes:</h3>
<dl>
<dt>
<a href="classWt_1_1WFormModel.html">WFormModel</a>
</dt>
<dd>
A model class for forms. These models are used in Wt::Auth as the
basis for RegistrationModel and AuthModel, and allow a more
straight-forward customization of the underlying behavior of these
forms.
</dd>
<dt>
<a href="classWt_1_1WReadOnlyProxyModel.html">WReadOnlyProxyModel</a>
</dt>
<dd>
A proxy model class which allows to share a source model
read-only between multiple sessions.
</dd>
<dt>
<a href="classWt_1_1WTemplateFormView.html">WTemplateFormView</a>
</dt>
<dd>
A WTemplate-based standard view implementation that works in conjunction
with WFormModel.
</dd>
<dt>
<a href="classWt_1_1Auth_1_1AuthModel.html">Auth::AuthModel</a>
</dt>
<dd>
A model that implements authentication logic.
</dd>
<dt>
<a href="classWt_1_1Auth_1_1FacebookService.html">Auth::FacebookService</a>
</dt>
<dd>
An OAuth-2.0 based authentication service implementation for
Facebook.
</dd>
<dt>
<a href="namespaceWt_1_1Utils.html">Wt::Utils</a>
</dt>
<dd>
This namespace contains a number of utility functions that we
found useful in projects using Wt. They relate mostly to
lower-level encoding and decoding functions: base64-, hex-, html-,
and url-encoding/decoding.
</dd>
</dl>
<h3>B) Main improvements:</h3>
<dl>
<dt>
<a href="classWt_1_1WApplication.html">WApplication</a>
</dt>
<dd>
A new method, WApplication::bind(), is useful in combination with
WServer::post() to avoid posting to a method of a deleted object,
leveraging the same life-time tracking as with signal connections.
</dd>
<dt>
<a href="namespaceWt_1_1Render.html">Render library</a>
</dt>
<dd>
A large number of performance improvements, especially for table
layout and rendering.
</dd>
<dt>
<a href="classWt_1_1Chart_1_1WAxis.html">Chart::WAxis</a>
</dt>
<dd>
DateScale and DateTimeScale axes have improved auto-configuration of
limits and timesteps, now taking into account the resolution.
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1Transaction.html">Dbo::Transaction</a>
</dt>
<dd>
We've modified the default transaction outcome: a transaction will
now automatically commit(), unless the transaction is being
destroyed (goes out of scope) because an exception is being
thrown, in which case the transaction will rollback(). Previously,
an uncomitted transaction would always rollback() on destruction.
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1ptr.html">Dbo::ptr</a>
</dt>
<dd>
Added a session() method, returning the session with which the
session has been associated.
</dd>
<dt>
Shipped SHA-1 implementation.
</dt>
<dd>
We now ship a SHA-1 implementation with Wt and this thus relaxes
the need for OpenSSL to implement WebSockets and
Auth::SHA1HashFunction.
</dd>
</dl>
<h3>C) Non-backwards compatible changes</h3>
<dl>
<dt>
<a href="classWt_1_1WTextEdit.html">WTextEdit</a>
</dt>
<dd>
Due to backwards incompatiblity of IE9, we now require the latest
version of TinyMCE (3.5b1 or later).
</dd>
<dt>
<a href="classWt_1_1Auth_1_1AuthWidget.html">Auth::AuthWidget</a>
</dt>
<dd>
A number of API methods that configure and access the configuration
were moved to the new Auth::AuthModel class which can be accessed from
the widget using model().
</dd>
<dt>
<a href="classWt_1_1Auth_1_1AbstractPasswordService_1_1AbstractStrengthValidator.html">Auth::AbstractPasswordService::AbstractStrengthValidator</a>
</dt>
<dd>
The API was simplified to be less unorthodox: validate() now
returns a Result that contains all the information for it.
</dd>
<dt>
<a href="classWt_1_1Http_1_1Client.html">Http::Client</a>
</dt>
<dd>
We've changed the signature of the parseUrl() utility function to
parse the URL into a URL structure instead of a collection of
string parameters.
</dd>
</dl>
<hr>
<h2>Release 3.2.0 (November 29, 2011)</h2>
<p>
This release contains a number of new modules, as well as the usual
batch of <a href="http://redmine.emweb.be/versions/show/13">bug
fixes</a> and small feature improvements.
</p>
<p>
In this release we also change the WValidator API in a way that it
is likely to break existing applications.
</p>
<h3>A) New namespaces:</h3>
<dl>
<dt>
<a href="group__json.html">Wt::Json (JSON handling)</a>
</dt>
<dd>
This namespace contains classes (Object, Value, Array) which map
the JSON types in C++. It also contains a parser to deserialize
JSON. A writer to serialize to JSON hasn't been added yet.
</dd>
<dt>
<a href="group__mail.html">Wt::Mail (SMTP protocol)</a>
</dt>
<dd>
This namespace contains a Client to send mail messages. It is
currently offering only limited functionality w.r.t. SMTP protocol
handling, but contains enough functionality to send standards
compliant plain-text/HTML mails, with full support for unicode.
</dd>
<dt>
<a href="group__auth.html">Wt::Auth (Authentication)</a>
</dt>
<dd>
<div>This namespace contains model and view classes for
authentication. It implements password authentication using best
practices, email verifiation, remember-me tokens, and provisions
support for federated login with an implementation of OAuth 2.0
for authentication using third party identity providers.</div>
<div>We expect that the API may still evolve, especially with
respect to OAuth 2.0 (which is a draft protocol), and its use
for OpenID Connect, which is the main use case for OAuth within
the authentication module.</div>
</dd>
</dl>
<h3>B) New classes:</h3>
<dl>
<dt>
<a href="classWt_1_1WException.html">WException</a>
</dt>
<dd>
We have cleaned up the use of exceptions within Wt. We have
converted numerous cases where an exception used to be thrown to
error logging, if the exception was thrown to indicate an API
problem. When the API problem is not resulting in a corrupt state,
we now log the error instead of terminating the session. All other
cases now use an exception that implements WException. This does
not affect situations where a std::exception was advertised in the
API.
</dd>
<dt>
<a href="classWt_1_1WIOService.html">WIOService</a>
</dt>
<dd>
<div>
Previously, boost::asio was used only in the built-in httpd as a
portable asynchronous I/O reactor implementation. We have now
moved this into the Wt library itself, where it is now used
instead of a dedicated thread pool for dispatching requests (and
other server events), and where it is also used for asynchronous
I/O by e.g. the Http::Client.
</div>
<div>
The WIOService specializes a boost::asio::service, and integrates
the thread pool that runs the service.
</div>
</dd>
<dt>
<a href="classWt_1_1WStringStream.html">WStringStream</a>
</dt>
<dd>
This is a utility class that we have used since long in Wt. It is
a more efficient replacement for std::stringstream, with mostly a
compatible API (at least for our purposes). For our purposes it is
typically a factor of two or more faster.
</dd>
<dt>
<a href="classWt_1_1Http_1_1Client.html">Http::Client</a>,
<a href="classWt_1_1Http_1_1Message.html">Http::Message</a>
</dt>
<dd>
<div>We have added an implementation of a Http(s) client. The client
is intended for consuming web services in Wt, and handles GET or
POST requests. It is not suitable (yet) for large responses, since
it buffers the entire response internally.</div>
<div>The client uses asynchronous I/O, using the WIOService that is
found in the current WServer instance.</div>
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1backend_1_1Firebird.html">Dbo::Firebird</a>
</dt>
<dd>
<div>Lukasz Matuszewski contributed a Firebird backend
implementation, thanks !</div>
</dd>
</dl>
<h3>C) Main improvements:</h3>
<dl>
<dt>
<a href="classWt_1_1WAbstractItemView.html">WAbstractItemView</a>
</dt>
<dd>
Added a setHeaderWordWrap() method which configures header text
word wrapping, and changed setHeaderAlignemnt() so that it now
allows to change both the horizontal and vertical alignment. This
replaces the previously interwoven API for both features using the
multiLine parameter in setHeaderHeight(), which has been
deprecated. The rendering of the header items has been
reimplemented, simplified, and cleaned up in the process, avoiding
rendering problems on IE browsers.
</dd>
<dt>
<a href="classWt_1_1WApplication.html">WApplication</a>
</dt>
<dd>
Two new methods, deferRendering() and resumeRendering() can be
used to defer the rendering phase in response to the current
event-loop request. This is useful for situations where you are
waiting for an asynchronous operation to complete, but want to
handle this synchronously in the user-interface (i.e. blocking the
interface until the operation completes). While this is not a good
idea in general, it may be useful if you can guarantee that the
event will arrive within an acceptible time (e.g. 1 second). This
effectively stalls the response to the current request, but avoids
blocking threads in the process.
</dd>
<dt>
<a href="classWt_1_1WDialog.html">WDialog</a>
</dt>
<dd>
Added setClosable(), which adds a close icon into the title bar.
</dd>
<dt>
<a href="classWt_1_1WFormWidget.html">WFormWidget</a>
</dt>
<dd>
We have cleaned up the use of exceptions within Wt. We have
converted numerous cases where an exception used to be thrown to
error logging, if the exception was thrown to indicate an API
problem. When the API problem is not resulting in a corrupt state,
we now log the error instead of terminating the session. All other
cases now use an exception that implements WException. This does
not affect situations where a std::exception was advertised in the
API.
</dd>
<dt>
<a href="classWt_1_1WLogger.html">WLogger</a>
</dt>
<dd>
<div>
We have reorganized the logging within Wt. Internally, a number
of macros are now used for logging, with as default
implementation our own (simple) logger, but which can be
redefined to use instead another logging framework of your
choice, as some have rightfully requested.
</div>
<div>
But we've also improved our logger so that it now can be
configured to filter only certain information, based on type and
scope. This is mostly useful for debuggin and development of Wt
itself, since it allows us to switch on debugging output, in a
fine-grained way, in a debug build.
</div>
<div>Finally, a new global function has been added (Wt::log()) which
selects an appropriate logger for logging and is more convenient
than WApplication::log() which required an application instance.
</div>
</dd>
<dt>
<a href="classWt_1_1WTemplate.html">WTemplate</a>
</dt>
<dd>
<div>Arguments to bound functions are now parsed and passed to
the resolveString() methods.</div>
<div>Two new constructs have been added: conditions and
functions. Conditions allow certain parts of a template to be
skipped or included based on a bound condition. Functions are
useful to automatically resolve certain variables, two built-in
functions are implemented: one to resolve strings in a message
resource bundle ("tr"), and another to resolve the id of a bound
widget ("id").
</div>
</dd>
<dt>
<a href="classWt_1_1Dbo_1_1collection.html">Dbo::collection<T></a>
</dt>
<dd>
We've added front() methods that return the first element.
</dd>
<dt>
Built-in httpd connector
</dt>
<dd>
We have expanded the WebSockets implementation to cover newer
versions of the WebSockets protocol (draft): next to 00, we now
also support 07, 08 and 13 protocols (with draft-17 semantics).
</dd>
<dt>
Configuration
</dt>
<dd>
On UNIX-like platforms, and using the built-in httpd connector,
SIGHUP is caught in the WServer::waitForShutdown() utility function,
and the configuration file (wt_config.xml) is reread.
</dd>
<dt>
Several security improvements
</dt>
<dd>
<dl>
<dt>DoS mitigation</dt>
<dd>We have added two measures to prevent DoS attacks that try
to exhaust the server by spawning sessions. This is in
particular a risk when deploying using the progressive bootstrap
method, since then a plain HTML session can be spawned with a
single request.
<ul>
<li>Plain sessions may be limited to constitute only a
fraction of the total number of sessions. This is configured
using the <plain-ajax-sessions-ratio-limit>
configuration option.</li>
<li>Ajax sessions need to confirm their "intelligence" by
solving a puzzle which requires them to properly parse the
(ever-changing) JavaScript and HTML.</li>
</ul>
</dd>
<dt>Compromised session ID risk reduction</dt>
<dd>