New To Vaadin

General
1

Hello…

I am new to web application developemt… Previously i was programming application programs with Swing and now want to move to Web Application… Vaadin code is similar to swing…

I am new so please guide me how to learn vaadin, what topics should i learn… MVC, EJB etc…

And any good video tutorial for vaadin…

I want to create a Property Management Software with vaadin

2

Hi!

The best place to start is probably the book of Vaadin https://vaadin.com/book. The page https://vaadin.com/framework also contains several links to demos and tutorials on how to get started with Vaadin.

Best regards,
Pontus

3

Hello there,

I’m new to vaadin and I’m reading the online version of the vaadin book, reading Chapter 4.1.
I examined the test application and started to think about how to develop a bit more complex webapp User Interface with this framework.

I’m thinking about 2 approaches, the first comes from the example application and looks like working as expected:
1;

  • I leave the built in layout on the MainUI class as it is. this MainUI and its layout will be the more static part of my project. Menu, footer, etc.
  • I create classes that are extending horizontal / vertical / etc layouts. These classes are my subpages, which are more interactive and changing time to time as the user interacts with the application.
  • For example when a user clicks on a menu item (registration), an event listener removes the homepage of the application from the MainUI’s content and attaches instantiates a registration page which is a class, extending vertical layout.

2; I create multiple UIs and switch in between them when the users interact with the application.

What are the benefits and limitations of these two approaches?

4

Hi,

You should definetly go with the first approach. The recommended way to switch between views is to use a Navigator https://vaadin.com/book/-/page/advanced.navigator.html. That ways the different views can be accessed directly by an URL (they are then bookmarkable also). Also access control and stuff can be easily implemented.

Alternative 2 is a bad idea in general. It becomes difficult to share information between views and switching between views is slow since a new application is reloaded every time.

Best regards,
Pontus