Clean CSS

[GoogleCodeExporter]

Currently Hablar.css is a mess. Only skinnable attributes should be there...

Original issue reported on code.google.com by danigb on 19 Apr 2010 at 4:17

[GoogleCodeExporter]

What about leveraging the GWT themes as much as possible? Currently Hablar and 
Hablar.css overwrites almost every default CSS theme class.
I think that we should start from a clean situation using the standard theme 
(for 
example).
After that, the Hablar.css file will have all the classes that will make the 
interface 
be nice.
I will play with it a bit locally.

Original comment by antonio....@gmail.com on 20 Apr 2010 at 1:37

[GoogleCodeExporter]

I committed a version where all the background color information is stored in 
few 
central points.
I moved some layout information inside the widgets themselves (e.g. headers 
that have 
all the components floating to left, padding a little somewhere, etc.)
I tried to leverage the GWT themes as much as possible.

Original comment by antonio....@gmail.com on 21 Apr 2010 at 3:48

[GoogleCodeExporter]

Thats great!

Original comment by danigb on 23 Apr 2010 at 11:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I reopen it, wrong commit comment sorry!

Original comment by antonio....@gmail.com on 26 Apr 2010 at 3:38

[GoogleCodeExporter]

Original comment by antonio....@gmail.com on 26 Apr 2010 at 3:39

• Changed state: New

[GoogleCodeExporter]

Original comment by antonio....@gmail.com on 26 Apr 2010 at 3:39

• Changed state: Accepted

[GoogleCodeExporter]

Hello Antonio:

You did a good work cleaning Hablar.css but maybe its time to go further and 
move all except color definitions 
into de gwt.xml files... what do you think?  

Original comment by danigb on 13 May 2010 at 4:10

[GoogleCodeExporter]

I agree, but currently I cannot do it, I prefer resolving the IE6 issues and 
preparing 
for our client graphics.
If you want, you (or someone else) can step in and finish the work, or simply 
wait 
until I've finished.

Original comment by antonio....@gmail.com on 13 May 2010 at 5:45

[GoogleCodeExporter]

Guys, we are looking to use emite in our application (www.spiraluniverse.com). 
I would 
strongly recommend that you drop support for IE6. Two reasons:

1. Don't waste your time. Do something useful instead.
2. Fixes for IE6 increase the code base without helping most of the customers.

Most major companies (including Google) already dropped it. Our system is used 
in 87 
countries, and we dropped IE6 many months ago.

Original comment by volgin%s...@gtempaccount.com on 23 May 2010 at 7:18

[GoogleCodeExporter]

volgin
this is not the place to talk about Emite, this is an issue.
Please write to the Emite users mailing list:
emite@googlegroups.com

Original comment by antonio....@gmail.com on 23 May 2010 at 7:34