Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

Vaadin evolution and freedom for designers

Marco Falsitta
1 decade ago Jul 15, 2011 9:09am

Vaadin provides a very comfortable production environment.
The advantage of creating components in Java and see the results on the generated HTML is speeding up a lot of work.
This works well for prototyping and internal utilities for companies, and in fact I have the impression that most of what companies do with Vaadin is that. For products that need to be made for the vast public the things is different because the difficulties of customize Vaadin created interfaces to create fluid layouts or interactive interfaces is really time consuming.
All the benefits of speeding up the initial prototype might get lost once the team employ HMTL/CSS designers that needs to customize the final look and behavior.

My tantrum here is about having the OPTION given from Vaadin to provide the most skimmed and cleaned output in term of HTML.
A Label that could be just a DIV with a class when attached to a VerticalLayout or a SPAN if attached to an HorizontalLayout with nothing else around it and not widh or hight forcefully calculated.

Some sort simple method called freeDesign(true); which let HTML/CSS (and why not, even jQuery developers) to regain controls over the final result.

Ergonomic deign, interactivity and tailored-thought behiviours are becoming more and more a requirements. Give designer the option to take control from a most clean and simple output generated from your great tools.

Can I hope for it?

Last updated on Jul, 19th 2011
Marlon Richert
1 decade ago Jul 21, 2011 3:36pm
Marco Falsitta
1 decade ago Jul 22, 2011 8:28am
Marlon Richert
1 decade ago Jul 22, 2011 8:35am
Marco Falsitta
1 decade ago Jul 22, 2011 8:42am
Marlon Richert
1 decade ago Jul 25, 2011 10:32am
Henri Sara
1 decade ago Jul 25, 2011 11:48am
Jouni Koivuviita
1 decade ago Jul 25, 2011 12:13pm

...and here's another attempt at ignoring those constraints: SimpleLayout

Simply put (no pun intended), this layout could possibly fix the issues you were having with CSSLayout, like the nested DIV hell. You're also free to specify margins, borders and paddings to the layout, which is possible with CSSLayout as well, but with more complex CSS and some small limitations in inheritance.

But do dead all about the SimpleLayout in the Directory page!

And feedback is more than welcome, once again!

Marco Falsitta
1 decade ago Jul 27, 2011 3:40pm
André Schild
1 decade ago Jul 27, 2011 4:25pm

Marco G Falsitta: The browser compatibility might always be an issue but it has a tendency to fade out over time. The latest compatibility test with IExplorer 10 where pretty promising.

Yes and no....

At a major client site we are now just phasing out the latest Windows 2000 systems, which means we are no longer bound to IE6.
BUT: Currently we can't jump to Windows 7 because the client has some other software which does not work with Vista or newer systems,
so currently we are replacing windows 2000 by windows xp, which then ends up in IE8, nothing more.
We hope to be able to upgrade to Windows 7 in 1-2 years at this client site and I doubt that many other companies will have phased out all Windows XP or older systems in two years....

One thing we see with vaadin is that the layouts are very well designed and work very well crossbrowser, BUT, they are slow on browsers with slow JS engines (Like IE6..8), because the sizes/margings etc. are calculated in JS and not natively by the browser.
Moving out <div> level of the dom structure helps improve js performance, but then cross browser compatibility catches you again... :(

Marco Falsitta
1 decade ago Aug 19, 2011 3:50pm
Marco Falsitta
1 decade ago Sep 05, 2011 2:42pm