/usr/lib/Wt/examples/wt-homepage/wt-home.xml is in witty-examples 3.3.0-1build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 | <?xml version="1.0" encoding="UTF-8" ?>
<messages>
<message id="template">
<div id="top_wrapper">
<div id="top_content">
${languages}
<div id="top_wt">
<a href="http://www.emweb.be/">
<img src="/css/wt/emweb_powered.jpg" alt="Emweb" height="22" />
</a>
</div>
</div>
</div>
<div id="banner_wrapper">
<div id="banner_content">
<div id="banner_end">
<div id="banner">
<!-- <a href="#">Wt</a> -->
</div>
</div>
</div>
</div>
<div id="main_wrapper" class="home">
<div id="main_content">
<div id="main_menu">
${menu}
${sidebar}
</div>
${contents}
<div class="clearall"></div>
</div>
</div>
<div id="footer_wrapper">
<div id="footer_content">
<div id="footer_copyright">
<a href="http://www.emweb.be/">
<img src="/css/wt/emweb_large.jpg" height="25" width="101"
alt="Emweb.be" title="emweb.be"/></a>
Solutions for web-based systems<br/>
<a href="http://www.emweb.be/">www.emweb.be</a>
</div>
<div id="footer_menu">
<a href="http://www.webtoolkit.eu/wt">Home</a>
| <a href="http://www.emweb.be/contact">Contact</a>
</div>
<div id="chat"></div>
<script src="http://www.webtoolkit.eu/wt/examples/simplechat/chat.js?div=chat" type="text/javascript"></script>
<div class="clearall"></div>
</div>
<script type="text/javascript">
/*<![CDATA[*/
window.pageTracker = null;
loadScript("http://www.google-analytics.com/ga.js", function() {
window.pageTracker = _gat._getTracker('UA-4345578-1');
window.pageTracker._initData();
window.pageTracker._trackPageview();
});
/* ]]> */
</script>
</div>
</message>
<message id="wt">Wt, C++ Web Toolkit</message>
<message id="introduction">Introduction</message>
<message id="blog">Blog</message>
<message id="features">Features</message>
<message id="documentation">Documentation</message>
<message id="examples">Examples</message>
<message id="download">Download</message>
<message id="community">Support</message>
<message id="other-language">!C++</message>
<message id="hello-world">Hello world</message>
<message id="charts">Charts</message>
<message id="wt-homepage">Wt homepage</message>
<message id="treeview">Treeview</message>
<message id="git">Git explorer</message>
<message id="chat">Chat</message>
<message id="mail-composer">Mail composer</message>
<message id="hangman">Hangman</message>
<message id="widget-gallery">Widget gallery</message>
<message id="home.news">
<h3><span>News</span></h3>
</message>
<message id="home.latest-news">
<h4><span>Latest News</span></h4>
</message>
<message id="home.historical-news">
<h4><span>Historical News</span></h4>
</message>
<message id="source-browser-link">
<a href="{1}">Browse the source code</a>
</message>
<message id="src-title">
<div>
</div>
</message>
<message id="home.intro">
<h3><span>Wt: an introduction</span></h3>
<p>Wt (pronounced as <i>witty</i>) is a C++ library for developing
web applications.</p>
<p>The API is <b>widget-centric</b> and uses well-tested patterns of
desktop GUI development tailored to the web. To the developer, it
offers abstraction of web-specific implementation details, including
client-server protocols, event handling, graphics support, graceful
degradation (or progressive enhancement), and URL handling.</p>
<p>Unlike many page-based frameworks, Wt was designed for creating
stateful applications that are at the same time highly interactive
(leveraging techinques such as WebSockets and Ajax to their fullest)
and accessible (supporting plain HTML browsers), using automatic
<b>graceful degradation or progressive enhancement</b>. Things that
are natural and simple with Wt would require an impractical amount of
effort otherwise: switching widgets using animations, while being
perfectly indexed by search robots with clean URLs, or having a
persistent chat widget open throughout, that even works in legacy
browsers like Microsoft Internet Explorer 6.</p>
<p>The library comes with an application server that acts as a
stand-alone Http(s)/WebSocket server or integrates through FastCGI
with other web servers.</p>
<h4>Interactive, secure and accessible</h4>
<p>Page-based web frameworks (Django, Ruby on Rails, PHP, etc...) do
not attempt to abstract underlying technologies (HTML/XHTML,
JavaScript, CSS, Ajax, WebSockets, Comet, Forms, DHTML,
SVG/VML/Canvas). As a consequence, a web developer needs to be
familiar with all of these evolving technologies and is also
responsible for graceful degradation when browser support is
lacking. The structure of many web applications still follows mostly
the page-centric paradigm of early day HTML. This means that not only
will you need to implement a controller to indicate how a user moves
from page to page, but when using advanced Ajax or WebSockets, you
will need to design and maintain your client-server communication.</p>
<p>Pure Ajax frameworks on the other hand require tedious JavaScript
programming to deal with browser quirks, and client-server programming
to interact securely with server resources. These applications usually
are not compliant with accessibility guidelines and cannot be indexed
by a search robot.</p>
<p>Generating HTML code or filling HTML templates is prone to security
problems such as <a
href="http://en.wikipedia.org/wiki/Cross-site_scripting">XSS
(Cross-Site-Scripting)</a> by unwillingly allowing JavaScript to be
inserted in the page, and <a
href="http://en.wikipedia.org/wiki/Cross-site_request_forgery">CSRF
(Cross-Site Request Forgery)</a> by trusting cookies for
authentication. These security problems are hard to avoid in
traditional frameworks when as a developer you need to implement
JavaScript functionality and thus the framework cannot filter it
out.</p>
<p>In contrast, a web application developed with Wt is developed
against a C++ API, and the library provides the necessary HTML, CSS,
Javascript, CGI, SVG/VML/Canvas and Ajax code. The responsibility of
writing secure and browser-portable web applications is carried by
Wt. For example, if available, Wt will maximally use JavaScript, Ajax
and even WebSockets, but applications developed using Wt will also
function correctly when JavaScript is not available. Wt will start
with a plain HTML/CGI application and progressively enhance to a rich
Ajax application if possible. With Wt, security is built-in and by
default.</p>
<h4>Typical use scenarios:</h4>
<ul>
<li><b>High performance, complex</b> web applications which are
fully personalized (and thus cannot benefit from caching), fully
Ajax enabled and at the same time entirely accessible and Search
Engine Optimized.</li>
<li>Web-based GUIs for <b>embedded systems</b> benefit from the low
footprint of a C++ web application server.</li>
<li>Web-based GUIs that require <b>integration with (existing) C++
libraries</b>, for example for scientific or engineering
applications, or <b>existing C++ desktop applications</b>.</li>
</ul>
<h4>Other benefits of using Wt</h4>
<ul>
<li>Develop web applications using familiar desktop GUI
patterns.</li>
<li>Provides an extensive set of widgets, which work regardless of
JavaScript availability (but benefit from JavaScript
availability).</li>
<li>A single specification for both client- and server-side
validation and event handling.</li>
<li>Optionally, use XHTML and CSS for layout and decoration.</li>
<li>Generates standards compliant HTML or XHTML code.</li>
<li>Portable, anti-aliased graphics optimized for web usage (using
inline VML, inline SVG, HTML5 canvas or PNG images), which can also
be used to render to PDF.</li>
<li>Avoid common security problems since Wt has complete control
over the presentation layer and proactively filters out
<i>active</i> tags and attributes, does not expose business logic,
and simplifies authentication using a stateful design.</li>
<li>Ultra-fast load time and low bandwidth usage, which are affected
only by screen complexity, not application size. Wt implements all
the common tips and tricks for optimizing application
responsiveness and even optimizes per browser.</li>
<li>A simple API with a robust cross-browser implementation for
server-initiated events aka <i>server push</i> (using <i>comet</i>
or WebSockets).</li>
<li>Use the built-in httpd for easy development and deployment, or
use the FastCGI/ISAPI connectors to deploy in existing web
servers.</li>
</ul>
</message>
<message id="home.features">
<h3><span>Features</span></h3>
<h4>Core library</h4>
<ul>
<li>Supports major browsers (Firefox/Gecko, Internet Explorer,
Safari, Chrome, Konqueror, and Opera) but also plain HTML browsers
(Links, Lynx).</li>
<li>Develop and deploy on Unix/GNU Linux or Microsoft Windows
(Visual Studio) environments.</li>
<li>Equal behavior with or without support for JavaScript or Ajax,
as far as possible, by using graceful degradation or progressive
enhancement.</li>
<li>Integrated Unicode support and pervasive localization.</li>
<li>Efficient rendering and (very) low latency.</li>
<li>Support for browser history navigation (back/forward buttons and
bookmarks), pretty URLs with HTML5 History if available, and
search engine optimization with a unified behavior for plain HTML
or Ajax sessions.</li>
<li>Configurable session tracking options that include URL rewriting
and cookies.</li>
<li>High performance, allowing deployment on low-end embedded
devices, or energy-, space- and budget-friendly deployment of
Internet or extranet web sites.</li>
<li>Completely based on event-driven async I/O: sessions are not
tied to threads, and neither do open connections block threads.
Instead, threads are needed only to improve concurrent request
handling or for reentrant event loops.</li>
</ul>
<h4>Event handling</h4>
<ul>
<li>Uses a modern typesafe signal/slot API for responding to events.</li>
<li>Listen for keyboard, mouse and focus events, and get event
details (such as mouse position, modifier buttons, or keyboard
key).</li>
<li>Automatic synchronization of form field data between browser and
server.</li>
<li>Dynamic C++-to-JavaScript translation, by specifying
<i>stateless slot</i> implementations. A single C++ slot implementation
provides both client-side and server-side event handling: visual changes
at client-side and application state at server side.</li>
<li>Possibility to hook in custom JavaScript (e.g. for client-side only event
handling), and <i>emit</i> C++ signals from this custom JavaScript.</li>
<li>Drag&Drop API.</li>
<li>Timed events and server-initiated updates ("server push")</li>
<li>Uses plain HTML CGI, Ajax or WebSockets</li>
</ul>
<h4>Native painting system</h4>
<ul>
<li>Unified painting API which uses the browsers native (vector)
graphics support (inline VML, inline SVG, or HTML5 canvas), or
renders to common image formats (PNG, GIF, ...) or vector formats
(SVG, PDF).</li>
<li>Supports arbitrary painter paths, clipping, text, images,
transformations, drop shadow.</li>
</ul>
<h4>GUI components</h4>
See the <a href="http://www.webtoolkit.eu/widgets">Widget
gallery</a> for an interactive overview of built-in functionality.
<h4>Built-in security</h4>
<ul>
<li>Kernel-level memory protection protects against privacy issues
arising from programming bugs, since sessions can be completely
isolated from each other (in dedicated-process mode).</li>
<li>Supports encryption and server authentication using Secure Sockets
Layer (SSL) or Transport Layer Security (TLS) through HTTPS.</li>
<li>Enables continuous use of HTTPS through low bandwidth
requirements (fine-grained Ajax).</li>
<li>Built-in Cross-Site Scripting (XSS) prevention. Rendered text is
always filtered against potentially malicious code, making XSS
attacks against Wt applications (close to) impossible.</li>
<li>Not vulnerable to Cross-site Request Forgery (CSRF) because
cookies for session tracking are optional, and even when used, they
are never solely relied on for requests that trigger event handling
code.</li>
<li>Not vulnerable to breaking the application logic by skipping to
a particular URL, since only those events exposed in the interface
can be triggered.</li>
<li>Session hijacking mitigation and risk prevention</li>
<li>DoS mitigation</li>
<li>A built-in authentication module implements best practices for
authentication, and supports third party identity providers using
OAuth 2.0, and (later) OpenID Connect</li>
</ul>
<h4>Object Relational Mapping library</h4>
Wt comes with Wt::Dbo, a self-contained library which implements
Object-Relational mapping, and thus a convenient way to interact with
SQL databases from C++. Although features like optimistic concurrency
control make this an ideal technology for a database driven web
application (and it provides good integration with Wt's MVC classes),
the library can also be used for other applications, and does not
depend on Wt.
The ORM library (see also <a
href="http://www.webtoolkit.eu/wt/doc/tutorial/dbo/tutorial.html">this
tutorial</a>) has the following features:
<ul>
<li>No code generation, no macro hacks, no XML configuration, just
modern C++!</li>
<li>Uses a templated visitor pattern which requires a single
template method to provide the mapping: DRY and as efficient as
conceivable!</li>
<li>You can indicate surrogate auto-incremental keys or map natural
keys of any C++ type, which may also be composite (i.e. require more
than one database field).</li>
<li>Supports <a
href="http://en.wikipedia.org/wiki/Optimistic_concurrency_control">
optimistic concurrency control</a> using a version field.</li>
<li>Maps Many-to-One and Many-to-Many relations to STL-compatible
collections.</li>
<li>Provides schema generation (aka DDL: data definition language)
and CRUD operations (aka DML: data manipulation language).</li>
<li>Prepared statements throughout.</li>
<li>Each session tracks dirty objects and provides a first-level cache.</li>
<li>Flexible querying which can query individual fields, objects, or
tuples of any these (using Boost.Tuple).</li>
<li>Use a single connection or share connection pools between
multiple sessions from which connections are used only during an
active transaction.</li>
<li>Comes with Sqlite3, Firebird, MariaDB/MySQL and PostgreSQL
backends, and an Oracle backend is also available on request.</li>
</ul>
<h4>Testing</h4>
With Wt, event handling code constructs and manipulates a widget tree,
which can easily be inspected by test code. Therefore, a <a href="
http://webtoolkit.eu/wt/doc/reference/html/classWt_1_1Test_1_1WTestEnvironment.html">test
environment</a> allows your application to be instantiated and events
to be simulated in absence of a browser, short-cutting the underlying
request/response cycle that would otherwise require a simulated browser.
<h4>Deployment</h4>
<p>
The library abstracts different deployment options as connectors
libraries, which connect Wt with the outer world. Switching deployment
option is a matter of (re)linking to one of these connector libraries!
</p>
<h5>a) Built-in httpd</h5>
<ul>
<li>Simple, high-performance web application server (multi-threaded,
asynchronous I/O) based on the C++ asio library.</li>
<li>Supports the HTTP(S) and WebSocket(S) protocols.</li>
<li>Supports response chunking and compression.</li>
<li>Single process (convenient for development and debugging), and
embeddable in an existing application.</li>
<li>Supports deployment behind a ProxyPass'ing (and if needed,
load-balancing) web server.</li>
<li>Available for both UNIX and Win32 platforms.</li>
</ul>
<h5>b) FastCGI</h5>
<ul>
<li>Integrates with most common web servers (apache, lighttpd).</li>
<li>Different session-to-process mapping strategies.</li>
<li>Hot deployment: new sessions use the new application version while
older sessions may continue with their application version.</li>
<li>Available only for UNIX platforms.</li>
</ul>
<h5>c) ISAPI</h5>
<ul>
<li>Integrates with Microsoft IIS server.</li>
<li>Uses the ISAPI asynchronous API for maximum performance.</li>
<li>Available for the Win32 platform.</li>
</ul>
</message>
<message id="home.examples">
<h3><span>Examples</span></h3>
<p>Explore some live examples of Wt below.</p>
<p>
The source code of these (and many more) examples is included in the
Wt source distribution. You may also browse through the source code
of each example using the <a href="#/src">source code viewer</a>,
following the link below each example.
</p>
<p>
Cross-linked source code for these examples is also in
<a href="http://www.webtoolkit.eu/wt/doc/examples/html/modules.html" target="_blank">
doxygen documentation (in a new window)</a>.
</p>
</message>
<message id="home.examples.hello">
<div>
<h4 class="example">Hello world!</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/hello/hello.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a>
</p>
<p>This simple example illustrates most of the basic Wt concepts:</p>
<ul>
<li>
How to make a minimal Wt application, using <b>WRun()</b> to start
the web server, and a function to create a new <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WApplication.html"
target="_blank">WApplication</a>, corresponding to a new session.
</li>
<li>
<b>Creating widgets</b>, and adding them to <b>the widget tree</b>.
</li>
<li>
Reacting to events using the <b>signal/slot</b> mechanism.
</li>
<li>
Reading user input and updating widgets.
</li>
</ul>
<p>For a thorough (although slightly out-dated) explanation of the
hello world example, see also the <a
href="http://www.codeguru.com/cpp/i-n/internet/browsercontrol/article.php/c15275/"
target="_blank">nice introduction to Wt</a> written by Victor Venkman.</p>
</div>
</message>
<message id="home.examples.wt">
<div>
<h4 class="example">Wt homepage</h4>
<p>We eat our own dog food: this website itself is a Wt example. </p>
<p>
Not really the interactive application Wt was designed for, the
homepage illustrates how Wt also makes excellent content-driven
websites. To that extent, Wt supports pretty URLs all the same for
both Ajax and plain HTML sessions (leveraging HTML5 History support
if possible), useful for browser history navigation,
bookmarks, and search engine optimization.
</p>
<p>
Navigation is provided by a <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WMenu.html"
target="_blank">WMenu</a> and <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WTabWidget.html"
target="_blank">WTabWidget</a>. These widgets share the same feature
set. For Ajax sessions, they support <b>pre-loading</b> and <b>lazy
loading</b> of the contents associated with each item. Pre-loaded
contents does not increase the load time because the Wt rendering
engine always optimizes the response time by only transmitting
visual widgets or changes first. Everything invisible (such as the
contents for other pre-loaded menu items) is transmitted in the
background, after rendering the visible contents.
</p>
<p>
Menu navigation is implemented using C++ stateless slots, and
therefore results in <b>client-side</b> event handling
code. Optionally, CSS3 animations can be used to animate the
transition of contents managed by a <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WStackedWidget.html"
target="_blank">WStackedWidget</a>.
</p>
<p>
URLs are associated with each menu/tab entry, and in this way
participate in browser navigation history and bookmarking. When the
user browses through the history, the menu reacts
to <a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WApplication.html#a674fd6a2522d66d07908e8f3d82424a9"
target="_blank">navigation events</a>. Similarly, when a user
bookmarks a URL to revisit it later, or follows an external link to
your application, the menu reacts to the initial internal
path. All-together this generates a decentralized "routing
framework" for pretty URLs that works equally well for Ajax as plain
HTML sessions.
</p>
<p>
The chat widget sitting at the bottom is actually part of the <a
href="#/examples/chat">chat example</a>.
</p>
</div>
</message>
<message id="home.examples.treeview">
<div>
<h4 class="example">Treeview</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/treeview-dragdrop/treeview-dragdrop.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a>
</p>
This example illustrates some MVC functionality provided by builtin
Views (WTreeView, WTableView and PieChart) and models.
<ul>
<li>
The example uses <a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WTreeView.html"
target="_blank">WTreeView</a>
and <a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WTableView.html"
target="_blank">WTableView</a> widgets for rendering a Model's
data in a tree or a table.
</li>
<li>
A <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WSortFilterProxyModel.html"
target="_blank">WSortFilterProxyModel</a>
implement sorting and filtering for another model.
</li>
<li>
These item views have support for drag and drop of a selection of items.
</li>
<li>
You can use nested layout managers (horizontal and
vertical
<a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WBoxLayout.html" target="_blank">
WBoxLayout</a>)
for an automatic window-filling layout, with optional resize handles.
</li>
<li>
Modal (and non-modal) <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WDialog.html"
target="_blank">dialogs</a> can be used to prompt for input.
</li>
<li>
You may show a context-sensitive
<a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WPopupMenu.html" target="_blank">
WPopupMenu</a>.
</li>
</ul>
</div>
</message>
<message id="home.examples.chart">
<div>
<h4 class="example">Charts example</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/charts/charts.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a>
</p>
<p>This example demonstrates the <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/group__charts.html" target="_blank">Wt
charting widgets</a> that are implemented on top of Wt's cross-browser
painting API. This painting API uses built-in browser support for
generating high quality graphics. Depending on the browser,
inline VML, inline SVG, HTML5 canvas, or a PNG image is used to
render painted contents in a <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WPaintedWidget.html"
target="_blank">WPaintedWidget</a>.
</p>
<p>This example also demonstrates how a Model can be shared by several
Views, and pass modification events to each connected View. The <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WTableView.html"
target="_blank">table view</a> and the chart implement a <i>View</i>
on the same <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WAbstractItemModel.html"
target="_blank">item model</a>.</p>
</div>
</message>
<message id="home.examples.git">
<div>
<h4 class="example">Git explorer</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/gitmodel/gitview.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a>
</p>
<p>
This example serves as a demo for a custom model implementation which can
be used by Wt's item View classes, such as
<a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WTreeView.html" target="_blank">
WTreeView</a>.
</p>
<p>
A <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WStandardItemModel"
target="_blank">WStandardItemModel</a> can be populated with data
retrieved from for example a database. A draw-back is however that
all data must be retrieved in advance and is kept in session
memory. By reimplementing <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WAbstractItemModel"
target="_blank">WAbstractItemModel</a>, you can however implement a
model that reads (or computes) the data only when needed, and
provides a trade-off between keeping data in memory or fetching it
from the source.</p>
<p>In this example, we implement a tree model that navigates a <a
href="http://git-scm.com/">git repository</a>. The model lazy-stores
folder nodes in memory, but reads all other data directly from
git. Initially we thought the SHA-1 id's could be used, but folders
with the same content in different places of the git repository have
the same SHA-1 ID's while representing different <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WModelIndex.html"
target="_blank">model indexes</a>.
</p>
</div>
</message>
<message id="home.examples.composer">
<div>
<h4 class="example">Mail composer</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/composer/composer.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a>
</p>
<p>
This example implements a GMail-like mail composer and shows among
other things how to upload files asynchronously, showing a
cross-browser upload progress bar and with support for multiple
files.
</p>
<ul>
<li>
The <i>ContactSuggestions</i> class provides auto-completion of
the addressees in the To: Cc: and Bcc: fields. The widget
derives from <a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WSuggestionPopup.html"
target="_blank">WSuggestionPopup</a>.
</li>
<li>
The <i>AttachmentEdit</i> widget uses a <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WFileUpload.html"
target="_blank">WFileUpload</a> to asynchronously
upload files. The upload <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WProgressBar.html"
target="_blank">progress bar</a> will work even in IE6.
</li>
<li>
The <i>Option</i> and <i>OptionList</i> classes show how
stateless slots, a trick to handle events client-side but
implement them still in C++, may be used even when the behaviour
is not entirely stateless. In this case, the hiding of an Option
affects neighboring visible options: an option needs a separator
only if there is a neighbouring option. By <b>invalidating the
stateless slot implementations</b> when state has changed, we
can still use a stateless slot implementation and enjoy
client-side event handling performance!
</li>
</ul>
</div>
</message>
<message id="home.examples.chat">
<div>
<h4 class="example">Simple Chat</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/simplechat/simplechat.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a> (or ventilate your thoughts down here)
</p>
<p>
This example implements a simple chat client and server. Using
<b>server-initiated updates</b>, you can easily push events from one
user to other users. Server-initiated updates are implemented using
Ajax long polling or HTML5 WebSockets.
</p>
<p>
It also illustrates nice benefits of a class-based approach to web
application development: you can easily instantiate the same widget
class multiple times. The SimpleChatClient widget may be reused just
as you reuse basic Wt widgets such as a push button.
</p>
<p>
The chat application is also available as a <i>Widget</i> which can
be embedded in another page (very much like how you integrate a
google maps widget inside another application). In this case, we've
embedded the chat also in this very homepage as follows:
</p>
<pre> <div id="chat"></div>
<script src="http://www.webtoolkit.eu/wt/examples/simplechat/chat.js?div=chat"></script></pre>
<p>
This uses Cross-Origin Ajax/WebSocket requests (if the browser
supports this, falling back to old tricks if not) to communicate
from a HTML origin page to a server hosting the Widget possibly from
a different domain.
</p>
<p>
Interactive applications like these, which allow users to post HTML
text to other users, are notorious for <b>cross-site-scripting (XSS)
attacks</b>: a user enters malicious (javascript) code as part of
his message. When another user renders this message, it may transmit
unwanted private information retrieved from, for example, browser
cookies. Wt prevents such attacks completely, and without any
responsibility to the developer, since widgets such as WText ensure
that what is displayed is only passive text, discarding anything
that is not strictly text.
</p>
</div>
</message>
<message id="home.examples.hangman">
<div>
<h4 class="example">Hangman</h4>
<p>
<a href="http://www.webtoolkit.eu/wt/examples/hangman-game/hangman.wt" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Run example
</a>
</p>
<p>
This example implements a simple well-known game, including a user
ranking system, which is persisted to a database using Wt::Dbo.
</p>
<p>
Some of the things illustrated in this example:
</p>
<ul>
<li>
Different approaches to layout: using an <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WTemplate.html"
target="_blank">HTML template</a>, a <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WBoxLayout.html"
target="_blank">layout manager</a>, or by compositing basic
widgets and CSS.
</li>
<li>
Using hidden content to optimize the user experience by preloading
contents, used in this game to preload the various images used to
show the hanging man.
</li>
<li>
Navigation is implemented using <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WAnchor.html"
target="_blank">WAnchor</a> which reference an internal path.
Action is taken by reacting to internal path changes.
</li>
<li>
The example uses <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/group__auth.html">the
authentication module (Wt::Auth)</a> to authenticate users using a
username/password, or using Google's beta OAuth 2.0 service.
</li>
<li>
A database which contains user information is accessed and updated
using <a href="http://www.webtoolkit.eu/wt/doc/tutorial/dbo/tutorial.html">Wt::Dbo</a>.
</li>
</ul>
<!--<p>For a thorough explanation of the hangman example, see also the ARTICLE</p>-->
</div>
</message>
<message id="home.examples.widgetgallery">
<div>
<h4 class="example">Widget gallery</h4>
<p>
<a href="http://www.webtoolkit.eu/widgets" class="run" target="_blank">
<img src="/icons/green-play.png" style="vertical-align: top"/> Go to widget gallery
</a>
</p>
<p>
This example demonstrates most widgets provided by Wt, in addition to
other aspects such as event handling and layout classes. Useful as an
executable reference to widgets and features provided by the library.
</p>
</div>
</message>
<message id="home.download">
<h3><span>Download</span></h3>
</message>
<message id="home.download.license">
<h4>License and Pricing</h4>
<p>Wt may be used using either an Open Source or a Commercial License.</p>
<p>If you wish to use the library using the <b>GNU General Public
License (GPL)</b>, you may build a web application with Wt and deploy
it, but per the terms of the GPL, you are obliged to make the source
code available to anyone who you give the application to install the
application on its own server. This also applies to redistribution of
the Wt library, in original or modified form.</p>
<p><b>The Commercial License</b> has no such limitations: you may
redistribute applications developed with Wt without needing to
redistribute the source code. The license is a royalty-free, perpetual
license for one developer to use the API of Wt (respectively Wt::Dbo)
for application development, using the latest version of Wt or any
version released during one year.
</p>
<table class="versions">
<tr class="trh">
<th></th>
<th class="product">Dbo</th>
<th class="product">Wt + Dbo</th>
</tr>
<tr class="r0">
<th>Widget library</th>
<td></td>
<td>+</td>
</tr>
<tr class="r1">
<th>Application server</th>
<td></td>
<td>+</td>
</tr>
<tr class="r0">
<th>HTTP + WebSockets server</th>
<td></td>
<td>+</td>
</tr>
<tr class="r1">
<th>Charting Module</th>
<td></td>
<td>+</td>
</tr>
<tr class="r0">
<th>XHTML Rendering Module</th>
<td></td>
<td>+</td>
</tr>
<tr class="r1">
<th>C++ ORM</th>
<td>+</td>
<td>+</td>
</tr>
<tr class="r0">
<th class="indent">Sqlite3 driver</th>
<td>+</td>
<td>+</td>
</tr>
<tr class="r1">
<th class="indent">PostgreSQL driver</th>
<td>+</td>
<td>+</td>
</tr>
<tr class="r0">
<th class="indent">Firebird driver</th>
<td>+</td>
<td>+</td>
</tr>
<tr class="r1">
<th class="indent">MariaDB/MySQL driver</th>
<td>+</td>
<td>+</td>
</tr>
<tr class="r0">
<th class="indent">Oracle driver</th>
<td colspan="2"><a href="mailto:sales@emweb.be">Contact us</a></td>
</tr>
<tr class="separate r1">
<th>License</th>
<td></td>
<td></td>
</tr>
<tr class="r0">
<th class="indent">
GNU General Public License
</th>
<td>free</td>
<td>free</td>
</tr>
<tr class="r1">
<th class="indent multiline">
Commercial License
</th>
<td class="multiline">
<div><span class="price">€175</span> <span class="cart" /></div>
<div><a href="http://www.webtoolkit.eu/wt/license/WtDbo%20License%20Agreement.pdf" class="smallprint">(license text)</a></div>
</td>
<td class="multiline">
<div><span class="price">€599</span> <span class="cart" /></div>
<div><a href="http://www.webtoolkit.eu/wt/license/Wt%20License%20Agreement.pdf" class="smallprint">(license text)</a></div>
</td>
</tr>
</table>
There is also an Oracle driver for Wt::Dbo, which is sold separately and
can be used only in conjunction with a Commercial License for Wt::Dbo.
</message>
<message id="home.download.packages">
<h4><span>Available packages</span></h4>
</message>
<message id="home.download.version"><b>Version</b></message>
<message id="home.download.date"><b>Date</b></message>
<message id="home.download.description"><b>Description</b></message>
<message id="home.download.other">
<p>
If you are on Ubuntu, you can install a reasonably recent version of
Wt from official packages.
</p>
<div class="fragment">
<pre class="fragment">
$ sudo apt-get install libwt libwt-dev libwthttp-dev witty-examples</pre>
</div>
<p>
The last package (<tt>witty-examples</tt>) installs the examples
in <tt>/usr/lib/Wt/examples</tt>. You can run each of them like this:
</p>
<div class="fragment">
<pre class="fragment">$ /usr/lib/Wt/examples/hello/hello</pre>
</div>
<p>Older releases are still available at
<a href="http://sourceforge.net/project/showfiles.php?group_id=153710#files">sourceforge.net</a>.
</p>
<h4>The Wt installer: winst</h4>
If you are curious about Wt and would like to try it out but your OS
or distribution does not provide an up-to-date package, then this may
be just what you need. This package will download and build Wt and its
dependencies in a <b>UNIX(-like) environment</b>, and provides also
a script to run the examples.
<p>
This requires <tt>CMake</tt> and <tt>GNU make</tt> and will try to
download software using <tt>wget</tt>.
</p>
<p>
Download the package
(<a href="http://www.webtoolkit.eu/packages/winst-0.4.tar.gz">winst-0.4.tar.gz</a>)
or get the latest git version:
<div class="fragment">
<pre class="fragment">$ git clone git://github.com/kdeforche/winst.git</pre>
</div>
</p>
<h4>System requirements</h4>
For building and installing the latest version of Wt, you need at
least the following two packages:
<ul>
<li><a href="http://www.cmake.org/">CMake</a> cross-platform make configure
utility.<br />
CMake >= 2.6 is preferred (although by the act of a miracle,
2.4 still works).
</li>
<li>
The indispensable <a href="http://www.boost.org/"> boost C++
library</a>: boost-1.41 or later. Older boost versions (as old as 1.36)
may also be used, but some functionality will be missing
(JSON parsing and a better SQL query parsing for Wt::Dbo). <br />
The following boost libraries (which are not headers only) are
needed: <tt>boost_date_time</tt>, <tt>boost_regex</tt>,
<tt>boost_program_options</tt>, <tt>boost_signals</tt>,
<tt>boost_random</tt>, <tt>boost_system</tt>, and optionally (but
highly recommended) <tt>boost_thread</tt>.
</li>
</ul>
The following packages are optional, and availability enables additional
features in Wt:
<ul>
<li><a href="http://www.openssl.org/">OpenSSL</a>: if available,
then the HTTPS protocol will be supported by the web client
(<a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1Http_1_1Client.html">Http::Client</a>) and web server (wthttp connector)
</li>
<li><a href="http://libharu.org/wiki/Main_Page">libharu</a>: if
available, a
<a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WPdfImage.html">WPdfImage</a>
paint device will be included, which provides rendering support for PDF
documents. For more complete support for TrueType fonts and Unicode, you'll
want <a href="https://github.com/libharu/libharu">the latest git version</a>
and probably also libpango (see further) for accurate font/glyph
selection.
</li>
<li><a href="http://www.graphicsmagick.org/">GraphicsMagick</a>: if
available,
a <a href="http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WRasterImage.html">WRasterImage</a>
paint device will be included, which outputs to raster images like PNG
or GIF.</li>
<li><a href="http://www.pango.org/">pango</a> (LGPL): if available,
text rendering for WPdfImage and WRasterImage will be assisted by
this library for TrueType font selection, taking into
consideration both the font face and unicode coverage.</li>
<li>
<a href="http://www.postgresql.org/">PostgreSQL</a>, <a
href="http://www.mysql.com/">MySQL</a>/<a
href="http://mariadb.org/">MariaDB</a>, and <a
href="http://firebirdsql.org">Firebird</a>: if available,
connectors for these databases for the ORM library (<a
href="http://www.webtoolkit.eu/wt/doc/tutorial/dbo/tutorial.html">
Wt::Dbo</a>) will be built (alongside the Sqlite3 connector which
is distributed with Wt).
</li>
</ul>
<p>The other requirements depend on the connector support you would
like. The connector is what makes your Wt application communicate with
the browser:</p>
<h5>For FastCGI (Unix only):</h5>
<ul>
<li>Apache 1 or 2, or another web server which supports the FastCGI
protocol.</li>
<li>
<a href="http://www.fastcgi.com/#TheDevKit">FastCGI development kit</a>
: fcgi-2.4.0
</li>
<li>
When using apache:
Apache <a href="http://www.fastcgi.com/dist/mod_fastcgi-2.4.6.tar.gz">mod_fastcgi</a>:
mod_fastcgi-2.4.x.<br />Alternatively you may
use <a href="http://httpd.apache.org/download.cgi#mod_fcgid">mod_fcgid</a>:
mod_fcgid-2.3.5.
</li>
</ul>
<h5>For the built-in http deamon, wthttpd:</h5>
<ul>
<li>Optionally, libz (for compression-over-HTTP) and openssl (for
HTTPS support).
</li>
</ul>
<h5>For ISAPI (Win32 only):</h5>
<ul>
<li>The ISAPI connector only works for deploying Wt applications withing a
Microsoft IIS server.</li>
</ul>
Follow the <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/InstallationUnix.html">Installation
instructions</a> to build Wt and run the examples, or see if your
platform is listed in the <a
href="http://redmine.webtoolkit.eu/projects/wt/wiki/Wt_Installation">platform specific
installation instructions</a>.
<h4>Git repository</h4>
<a href="https://github.com/kdeforche/wt"><img style="display: block; width: 80px; float: right" src="https://github.com/github/media/blob/master/octocats/octocat.png?raw=true"></img></a>
<p>If you want to keep track of the latest changes, or participate in
Wt development, you may want to work from
the <a href="https://github.com/kdeforche/wt">github
repository</a>.</p>
<p>
Alternatively checkout the repository using:
<div class="fragment">
<pre class="fragment">$ git clone git://github.com/kdeforche/wt.git</pre>
</div>
</p>
</message>
<message id="home.community">
<h3><span>Support</span></h3>
<h4>Support and Training</h4>
<p>
You can get <a href="http://www.emweb.be/services">support and
training</a> directly from the library authors, with a
guaranteed three-day response time.
</p>
<p>
Community help is available in the <a
href="http://redmine.webtoolkit.eu/projects/wt/boards">public
forums</a>. Until September 2009, there was only a <a
href="mailto:witty-interest@lists.sourceforge.net">mailing list</a>
(<a
href="http://lists.sourceforge.net/lists/listinfo/witty-interest">how
to join</a>), and the old dogs haven't left yet. You may search or
browse the mailing list archives using the <a
href="http://gmane.org/info.php?group=gmane.comp.web.witty.general">Gmane
gateway</a> (kudos to Pau Garcia i Quiles for setting this up).
</p>
<p>
To get up to speed with Wt and/or Wt::Dbo, you may also obtain <a
href="http://www.emweb.be/services">training</a> directly from
the library authors.
</p>
<h4>Authors</h4>
<p>
The software was originally developed by <a
href="mailto:koen@emweb.be">Koen Deforche</a>, and is currently
maintained by <a href="http://www.emweb.be/">Emweb bvba</a>.</p>
<p>We are greateful to these projects from which we borrowed code:</p>
<ul>
<li>The built-in httpd is based on an example of the <a
href="http://asio.sourceforge.net/">asio C++
library</a>, developed by Christopher M. Kohlhoff. <a
href="http://www.boost.org/LICENSE_1_0.txt">Boost Software License</a></li>
<li>The <a href="http://rapidxml.sourceforge.net/">RapidXML</a>
library by Marcin Kalicinski. <a
href="http://www.boost.org/LICENSE_1_0.txt">Boost Software License</a></li>
<li>The authentication module
contains <a href="http://www.openwall.com/crypt/">bcrypt</a>
and <a href="http://www.openwall.com/passwdqc/">passwdqc</a> by Solar
Designer. <a href="http://www.openwall.com/crypt/">Public
domain.</a></li>
</ul>
<p>
Other independent contributors include: Richard Ulrich, Gaetano
Mendola, Thomas Suckow, Hilary Cheng, Dmitriy Igrishin, Daniel Derr,
Omer Katz, and Lukasz Matuszewski, and many others (see the Changelog).
</p>
<h4>Wiki</h4>
<p>
There is a community-run <a
href="http://redmine.webtoolkit.eu/projects/wt/wiki">Wt Wiki</a> with useful
information, including installation notes for several Linux
distributions.
</p>
<h4>Contributions</h4>
<p>Development of Wt is sponsored by the following companies and
organisations:</p>
<p>
<table>
<tr>
<td class="sponsor-logo"><a href="http://www.emweb.be/">
Emweb bvba</a>
</td>
<td class="sponsor-role">
Creators, official maintainers, and support
</td>
</tr>
<tr>
<td class="sponsor-logo">
<a href="http://www.eurofer.be/">
Eurofer</a>
</td>
<td class="sponsor-role">
Sponsored the development of the charting library, WTreeView and
hierachical item models.
</td>
</tr>
</table>
</p>
<p>User contributions are welcomed, ranging from simple patches to
widgets, widget sets, and core improvements.</p>
<p>However, because Wt is dual-licensed under an Open Source and
commercial license, and to legally protect the code base of Wt as a
whole by one entity without having to worry about the copyrights for
different pieces, we require a copyright assignment from contributors
to <a href="http://www.emweb.be/">Emweb</a> before
accepting the contribution.</p>
<h4>Translations</h4>
The Chinese translation of the homepage was provided by Zhimin Song.
<h4>Sourceforge</h4>
<a href="http://sourceforge.net"><img src="http://sflogo.sourceforge.net/sflogo.php?group_id=153710&type=1" style="vertical-align:middle" width="88" height="31" border="0" alt="SourceForge.net Logo" /></a>
The Wt project is hosted at sourceforge <a href="http://sourceforge.net/projects/witty/">here</a>.
</message>
<message id="home.other-language">
<h3><span>!C++ ?</span></h3>
<p>You like the library functionality, but do not grock C++ for your
project?</p>
<p>Do not despair. Wt exists in a native variant or through bindings
in other languages:
<ul class="languages">
<li>
<div>
<img class="java-language-icon" src="/icons/java-logo.png" alt="Java"></img>
You can use <a href="http://www.webtoolkit.eu/jwt">JWt</a>, a native <b>Java</b> version of Wt
developed and maintained together with the C++ version. It has, with
few exceptions, the same features as Wt, but runs natively in the JVM
and can be deployed into any Servlet container.
</div>
<br style="clear: both" />
</li>
<li>
<div>
<img class="language-icon" src="/icons/ruby-logo-R.png" alt="Ruby"></img>
Richard Dale is
maintaining <a href="http://github.com/rdale/wtruby/tree/master">WtRuby</a>,
<b>Ruby</b> bindings to Wt, using the same framework used for generating Ruby
bindings to Qt and KDE.
</div>
<br style="clear: both" />
</li>
<li>
<div>
<img class="language-icon" src="/icons/clojure-logo.png" alt="Clojure"></img>
Leveraging the JVM's support for other languages, such
as <b>Clojure</b>, a LISP variant, Ralph Moritz is experimenting
with <a href="http://lispetc.posterous.com/hello-jwt-from-clojure">using
JWt from within Clojure</a>, documenting his experience in his blog
and eventually developing a small support library.
</div>
<br style="clear: both" />
</li>
<li>
<div>
<img class="language-icon" src="/icons/jython-logo.png" alt="Jython"></img>
Albert Cervera i Areny is experimenting to use JWt from <b>Jython</b>,
another language running on the JVM. He documents how to create and run
the "Hello World!" program in Jython in <a href="http://www.nan-tic.com/en/from-pyqt-to-jythonjwt-setting-up-the-environment">this blog post</a>.
</div>
<br style="clear: both" />
</li>
</ul>
</p>
</message>
<message id="home.documentation">
<h3><span>Documentation</span></h3>
<h4>Build and install</h4>
<p>
Generic installation instructions (UNIX)
are <a href="http://www.webtoolkit.eu/wt/doc/reference/html/InstallationUnix.html">here</a>, which
is also included in the source package (INSTALL or INSTALL.html).</p>
<p>
In addition, the <a href="http://redmine.webtoolkit.eu/projects/wt/wiki">Wt
Wiki</a> has a section dedicated
to <a href="http://redmine.webtoolkit.eu/projects/wt/wiki/Wt_Installation">platform
specific installation notes</a>.
</p>
<h4>Introduction and tutorials</h4>
<ul>
<li>Learn about the benefits of Wt compared to traditional web
application frameworks using our <a
href="http://www.webtoolkit.eu/doc/Wt-WhitePaper.pdf">white
paper</a>.</li>
<li>The <a
href="http://www.webtoolkit.eu/wt/doc/tutorial/wt.html">online
tutorial</a> (<a
href="http://www.webtoolkit.eu/wt/doc/tutorial/wt.pdf">download
PDF</a>) brings you up to speed on developing web applications using
Wt (revised December 2011).</li>
<li>The ORM framework (Wt::Dbo) is covered in a separate <a
href="http://www.webtoolkit.eu/wt/doc/tutorial/dbo.html">online
tutorial</a> (<a
href="http://www.webtoolkit.eu/wt/doc/tutorial/dbo.pdf">download
PDF</a>) (revised July 2011).</li>
<li>Dr Dobbs Journal has a good <a href="http://www.ddj.com/cpp/206401952">
introductary article on Wt</a> (February 2008).</li>
<li>The reference manual contains a <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/overview.html">library
overview</a> which is recommended reading with information on
configuration and deployment options.</li>
<li>Victor Venkman wrote a
<a href="http://www.codeguru.com/cpp/i-n/internet/browsercontrol/article.php/c15275/">nice introduction to Wt</a>, with a closer examination of
the <a href="#/examples/">hello world example</a>.</li>
</ul>
<h4>Reference manual</h4>
<p>The <a
href="http://www.webtoolkit.eu/wt/doc/reference/html/index.html"
target="_blank"> reference manual</a> has been generated from the
source code using doxygen.</p>
<h4>Annotated examples</h4>
<p>Source-level documentation has also been generated for the examples
and can be viewed <a href="http://www.webtoolkit.eu/wt/doc/examples/html/modules.html"
target="_blank">here (in a new window)</a>.</p>
<h4>Wiki</h4>
<p>
There is a community-run <a href="http://redmine.webtoolkit.eu/projects/wt/wiki">Wt Wiki</a> with useful information such as a FAQ and
tips and tricks.
</p>
</message>
<message id="srcview.title.CPP.">
<div class="srcviewtitle">
<h2>Source code for Wt examples</h2>
<p>
Browse below the source code for all examples included in
<a href="#/">Wt</a>.
</p>
</div>
</message>
<message id="srcview.title.">Wt examples</message>
<message id="srcview.title.CPP.hello">
<div class="srcviewtitle">
<h2>Source code of the <i>Hello world</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/">Hello world</a> example.
</p>
</div>
</message>
<message id="srcview.title.hello">Example: Hello world</message>
<message id="srcview.title.CPP.hangman">
<div class="srcviewtitle">
<h2>Source code of the <i>Hangman</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/">Hangman</a> example.
</p>
</div>
</message>
<message id="srcview.title.hangman">Example: Hangman</message>
<message id="srcview.title.CPP.charts">
<div class="srcviewtitle">
<h2>Source code of the <i>Charts</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/charts">Charts</a> example.
</p>
</div>
</message>
<message id="srcview.title.charts">Example: Charts</message>
<message id="srcview.title.CPP.treeview-dragdrop">
<div class="srcviewtitle">
<h2>Source code of the <i>Treeview</i> example</h2>
<p>
Browse below the source code for Wt's <a href="#/examples/treeview">
Treeview</a> example.
</p>
</div>
</message>
<message id="srcview.title.treeview-dragdrop">Example: Treeview</message>
<message id="srcview.title.CPP.composer">
<div class="srcviewtitle">
<h2>Source code of the <i>Mail composer</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/composer">Mail composer</a> example.
</p>
</div>
</message>
<message id="srcview.title.composer">Example: Mail composer</message>
<message id="srcview.title.CPP.wt-homepage">
<div class="srcviewtitle">
<h2>Source code of the <i>Wt homepage</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/wt-homepage">Homepage</a> example.
</p>
</div>
</message>
<message id="srcview.title.wt-homepage">Example: Wt Homepage</message>
<message id="srcview.title.CPP.gitmodel">
<div class="srcviewtitle">
<h2>Source code of the <i>Git explorer</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/gitmodel">Git explorer</a> example.
</p>
</div>
</message>
<message id="srcview.title.gitmodel">Example: Git explorer</message>
<message id="srcview.title.CPP.simplechat">
<div class="srcviewtitle">
<h2>Source code of the <i>Chat</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/simplechat">Chat</a> example.
</p>
</div>
</message>
<message id="srcview.title.simplechat">Example: Chat</message>
<message id="srcview.title.CPP.widgetgallery">
<div class="srcviewtitle">
<h2>Source code of the <i>Widget gallery</i> example</h2>
<p>
Browse below the source code for Wt's
<a href="#/examples/widgetgallery">Widget gallery</a> example.
</p>
</div>
</message>
<message id="srcview.title.widgetgallery">Example: Widget gallery</message>
</messages>
|