Page 1 of 1


PostPosted: 07 May 2019, 21:03
by Ursego
You can build a successful career as a Vaadin developer using such classes as VericalLayout, TextField, Label, Button etc. without knowing the complicated hierarchies of classes and interfaces behind them. In fact, that's how programmers work with PowerBuilder and classical Visual Basic: they simply place an object in a container, input & output work, events occur, and everybody are happy. In these environments, it's even impossible to see the bricks, from which the objects are built, and nobody complains about that. Another example: to practice sex, people don't need to be specialists in anatomy, physiology and psychology. They simply place an object in a container, input & output work, events occur, and everybody are happy. But, for me, it was very interesting to dig a bit deeper in the world of classes and interfaces of Vaadin. The provided file contains a lot of such internal information, but read it as a detective story, not as a boring technical book! It's not a study book: your goal is TO GET AN IDEA how Vaadin works, not to LEARN that! The file is based on the official Vaadin documentation plus some stuff from a couple of books. I tried to cut off as much information as possible, and keep only the most interesting stuff - probably, not very successfully, since the file is still large... Anyway, enjoy!

Save the file on your hard disk.

To enjoy keywords coloring, open this file in Eclipse. After that, enable word-wrap by pressing Alt + Shift + Y (otherwise you will need to scroll right to read long comments). Set the code editor width so the very first line of the file (with asterisks) fits one line (i.e. is not broken into 2 lines).

You can also open this file in Notepad++. It will understand by the file extension (.java), that it's Java code, and paint keywords. After that, enable word-wrap by marking the menu option View > Word wrap.

In any editor, use the Fixedsys font (as I did) to see straight vertical alignment.

To find (Ctrl+F) a class or an interface, add a colon (:) to its end. For example, search by the string "Sizeable:", not "Sizeable" ("Sizeable" will be
found as well, but it can appear many times in description of other classes; "Sizeable:" will take you to the description of the Sizeable type itself). If not found (like "Field:"), then try "Field<" (some types contain generics).