You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

intro-goals.asciidoc 1.9KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. ---
  2. title: Goals and Philosophy
  3. order: 4
  4. layout: page
  5. ---
  6. [[intro.goals]]
  7. = Goals and Philosophy
  8. Simply put, Vaadin's ambition is to be the best possible tool when it comes to
  9. creating web user interfaces for business applications. It is easy to adopt, as
  10. it is designed to support both entry-level and advanced programmers, as well as
  11. usability experts and graphic designers.
  12. When designing Vaadin, we have followed the philosophy inscribed in the
  13. following rules.
  14. == Right tool for the right purpose
  15. Because our goals are high, the focus must be clear. Vaadin is designed for
  16. creating web applications. It is not designed for creating websites or
  17. advertisement demos. You may find, for example, JSP/JSF more suitable
  18. for such purposes.
  19. == Simplicity and maintainability
  20. We have chosen to emphasize robustness, simplicity, and maintainability. This
  21. involves following the well-established best practices in user interface
  22. frameworks and ensuring that our implementation represents an ideal solution for
  23. its purpose without clutter or bloat.
  24. == Choice between declarative and dynamic UIs
  25. The Web is inherently document-centered and very much bound to the declarative presentation of user interfaces.
  26. Vaadin allows for declarative designs of views, layouts, and even entire UIs.
  27. Vaadin Designer enables creating such designs visually.
  28. Nevertheless, the programmatic approach by building the UIs from Java components frees the programmer from its limitations.
  29. To create highly dynamic views, it is more natural to create them by programming.
  30. == Tools should not limit your work
  31. There should not be any limits on what you can do with the framework: if for
  32. some reason the user interface components do not support what you need to
  33. achieve, it must be easy to add new ones to your application. When you need to
  34. create new components, the role of the framework is critical: it makes it easy
  35. to create re-usable components that are easy to maintain.