Built-in subsites: Static,   Auth  Form processing and layout generation[ edit ] See ref. It can also be used to generate a new form with blanks or default values. The form type takes the shape of a function of an html snippet to be embedded in the view, that will hold security purpose hidden fields. There are three types of forms: Applicative with tabular layout , Monadic with free layout style , both in the Yesod. Functions module, Input for parsing only, no view generated in the Yesod.
|Published (Last):||3 February 2015|
|PDF File Size:||15.67 Mb|
|ePub File Size:||20.77 Mb|
|Price:||Free* [*Free Regsitration Required]|
Why Yesod? Turn runtime bugs into compile-time errors Yesod believes in the philosophy of making the compiler your ally, not your enemy. We use the type system to enforce as much as possible, from generating proper links, to avoiding XSS attacks, to dealing with character encoding issues. In general, if your code compiles, it works. And instead of declaring types everywhere you let the compiler figure them out for you with type inference. Asynchronous made easy The Haskell runtime is asynchronous automatically.
Instead of dealing with callbacks, you get to write normal code. By utilizing light-weight green threads and event-based system calls, your code automatically becomes non-blocking, without the pain. Scalable and Performant Yesod lets you write simple, high-level code, and gives you good performance. But when you need more, you can tune your compiled code for something even faster. The GHC compiler ensures we get fast machine code at the end of the day. Light-weight syntax A lot of web development is boilerplate.
Setting up routing tables, creating database schemas, and dealing with forms can all be long, repetitive code. But more importantly the DSLs are correct: they are all compile-time checked to get rid of the runtime bugs.
Subscribe to RSS
Web/Comparison of Happstack, Snap and Yesod