On Sat, Jun 16, 2012 at 2:44 PM, James Cammarata jimi@sngx.net wrote:
On Fri, Jun 15, 2012 at 6:13 PM, Greg Swift gregswift@gmail.com wrote:
So I just updated to epel-testing, then noticed that i lost round edges (the .button, .action {} css section needs border-radius added). So I grabbed the latest releast of style.css and put it on my box so I could do a quick patch file on the issue, and wow... umm ya. So I went and looked at the changes and I see that james had to do quite a bit (20 adds, 25 deletions) for the new tabbed interface.
The only problem with that is that it affected more than jsut the tabbed interfaces.
The main issue is that to accomidate the smaller width on the tabbed interface the content div was adjusted to be a static width of 850px. Since the tables and the forms share the same parent div, I can see where you were going, my concern is just the overall effect. most of the tables are fine with this change, but not all of them.
I wanted a more static layout, I did not want expanding/contracting to cause weird float issues. If other objects inside the content div need to be sized correctly, we should just create more CSS for them rather than relying on the outer div to size them correctly.
Okay. Thats fine. My goal was to make it work for varying size of monitors as best as possible. I use anywhere from 1280x768 to 1900x1200 and had it sizing well on each. That being said, I know the tab interface adjusts that view and am fine with the change.
Can you be more specific about what's having issues? I didn't really notice any major artifacts from my changes.
So the main page that had a immediate wrap issue was the systems page. the buttons wrapped to two lines. I have a screenshot at work, but couldn't attach it, and can't upload to my personal website from there...
We should probably look at the user+logout button on the new style sheet as well. On my 1900x1200 monitor theat section is stranded way on the top left of the page, far away from any of the content.
-greg