But if you are already using Play!, Scalatra, Spring MVC or any other Scala/Java web framework, why would you add Supler to the mix? All web frameworks already provide support for writing, validating and submitting web forms – why not use the built-in tools?
But then comes the form where you need to conditionally enable/disable fields basing on complex business rules, or dynamically change possible choices in a dropdown, or embed a list of subforms in a form etc., and as most of the fields behave in a standard way, you could use some help from a library. That’s where using Supler will help the most.
subform field. Refactoring your entity? The form will be refactored as well, as everything is type-safe. Adding a new field? Just add it to the backend form definition, no changes on the frontend needed.
While Supler imposes some constraints on how your form works, as every library, it is highly customisable, both on the backend and frontend (presentation) side. Take a look at our quick-start guide and extensive documentation.
To sum up:
- for simple, static forms use what your framework provides
- for dynamic, complex, nested forms use Supler
Finally, during spring we’ve given a number of talks on Supler of JUGs and a couple of conferences. If you’d like, you can view the shorter one (30 minutes) from Scalar (below) or the long one (60 minutes) from LJC.