Mercurial > urweb
comparison demo/prose @ 896:0ae8894d5c97
New command-line options; describe simple SQLite build in demo intro
| author | Adam Chlipala <adamc@hcoop.net> |
|---|---|
| date | Sat, 18 Jul 2009 13:46:22 -0400 |
| parents | 305bc0a431de |
| children | 4359e185d3af |
comparison
equal
deleted
inserted
replaced
| 895:ae9e22822ec5 | 896:0ae8894d5c97 |
|---|---|
| 1 <p><b>Ur/Web</b> is a domain-specific language for programming web applications backed by SQL databases. It is (strongly) statically-typed (like ML and Haskell) and purely functional (like Haskell). <b>Ur</b> is the base language, and the web-specific features of Ur/Web (mostly) come only in the form of special rules for parsing and optimization. The Ur core looks a lot like <a href="http://sml.sourceforge.net/">Standard ML</a>, with a few <a href="http://www.haskell.org/">Haskell</a>-isms added, and kinder, gentler versions added of many features from dependently-typed languages like the logic behind <a href="http://coq.inria.fr/">Coq</a>. The type system is much more expressive than in ML and Haskell, such that well-typed web applications cannot "go wrong," not just in handling single HTTP requests, but across their entire lifetimes of interacting with HTTP clients. Beyond that, Ur is unusual in using ideas from dependent typing to enable very effective metaprogramming, or programming with explicit analysis of type structure. Many common web application components can be built by Ur/Web functions that operate on types, where it seems impossible to achieve similar code re-use in more established statically-typed languages.</p> | 1 <p><b>Ur/Web</b> is a domain-specific language for programming web applications backed by SQL databases. It is (strongly) statically-typed (like ML and Haskell) and purely functional (like Haskell). <b>Ur</b> is the base language, and the web-specific features of Ur/Web (mostly) come only in the form of special rules for parsing and optimization. The Ur core looks a lot like <a href="http://sml.sourceforge.net/">Standard ML</a>, with a few <a href="http://www.haskell.org/">Haskell</a>-isms added, and kinder, gentler versions added of many features from dependently-typed languages like the logic behind <a href="http://coq.inria.fr/">Coq</a>. The type system is much more expressive than in ML and Haskell, such that well-typed web applications cannot "go wrong," not just in handling single HTTP requests, but across their entire lifetimes of interacting with HTTP clients. Beyond that, Ur is unusual in using ideas from dependent typing to enable very effective metaprogramming, or programming with explicit analysis of type structure. Many common web application components can be built by Ur/Web functions that operate on types, where it seems impossible to achieve similar code re-use in more established statically-typed languages.</p> |
| 2 | 2 |
| 3 <p>This demo is built automatically from Ur/Web sources and supporting files. If you unpack the Ur/Web source distribution, then the following steps will build you a local version of this demo: | 3 <p>This demo is built automatically from Ur/Web sources and supporting files. If you unpack the Ur/Web source distribution, then the following steps will (if you're lucky) build you a local version of this demo. If you're not lucky, you can consult the beginning of <a href="http://www.impredicative.com/ur/manual.pdf">the manual</a> for more detailed instructions. |
| 4 | 4 |
| 5 <blockquote><pre>./configure | 5 <blockquote><pre>./configure |
| 6 make | 6 make |
| 7 sudo make install | 7 sudo make install |
| 8 urweb -demo /Demo demo</pre></blockquote></p> | 8 urweb -demo /Demo demo</pre></blockquote></p> |
| 21 | 21 |
| 22 ProxyPass /Demo/ http://localhost:8080/Demo/ | 22 ProxyPass /Demo/ http://localhost:8080/Demo/ |
| 23 ProxyPassReverse /Demo/ http://localhost:8080/Demo/</pre></blockquote></p> | 23 ProxyPassReverse /Demo/ http://localhost:8080/Demo/</pre></blockquote></p> |
| 24 | 24 |
| 25 <p>Building the demo also generates a <tt>demo.sql</tt> file, giving the SQL commands to run to define all of the tables and sequences that the applications expect to see. The file <tt>demo.urp</tt> contains a <tt>database</tt> line with the PostgreSQL database that the demo web server will try to connect to.</p> | 25 <p>Building the demo also generates a <tt>demo.sql</tt> file, giving the SQL commands to run to define all of the tables and sequences that the applications expect to see. The file <tt>demo.urp</tt> contains a <tt>database</tt> line with the PostgreSQL database that the demo web server will try to connect to.</p> |
| 26 | |
| 27 <p>The easiest way to get a demo running locally is probably with this alternate command sequence: | |
| 28 | |
| 29 <blockquote><pre>urweb -dbms sqlite -db /path/to/database/file -demo /Demo demo | |
| 30 sqlite3 /path/to/database/file <demo/demo.sql | |
| 31 demo/demo.exe</pre></blockquote></p> | |
| 32 | |
| 33 <p>Then you can skip the static content and connect directly to the demo server at <tt>http://localhost:8080/Demo/Demo/main</tt>, which contains links to the individual demos.</p> | |
| 26 | 34 |
| 27 <p>The rest of the demo focuses on the individual applications. Follow the links in the lefthand frame to visit the applications, commentary, and syntax-highlighted source code. (An Emacs mode is behind the syntax highlighting.) I recommend visiting the applications in the order listed, since that is the order in which new concepts are introduced.</p> | 35 <p>The rest of the demo focuses on the individual applications. Follow the links in the lefthand frame to visit the applications, commentary, and syntax-highlighted source code. (An Emacs mode is behind the syntax highlighting.) I recommend visiting the applications in the order listed, since that is the order in which new concepts are introduced.</p> |
| 28 | 36 |
| 29 hello.urp | 37 hello.urp |
| 30 | 38 |