| Re: XHTML & CSS [designing without tables] |
| by Anonymous on 2006/4/15 7:32:37 'Guest', you've misunderstood the meaning of 'Open Source'. If you feel the default theme needs improving, go ahead and improve it! Don't come here demanding others start working for you, because you think the existing work 'sucks'. Geez, some people... 
|
| Re: XHTML & CSS [designing without tables] |
| by Guest on 2006/4/15 7:27:30 Ah yes, the popups with the scrolling information for the modules is annoying too. It's lagging in Firefox. |
| Re: XHTML & CSS [designing without tables] |
| by Guest on 2006/4/15 7:25:38 I just installed XOOPS to have a look at it. As a webdesigner-hobbyist, I wanted to change the theme, so I started fiddling around with the default one. I was surprised seeing such a bad code for HTML and CSS. The pages really could (and should!) do without tables and the CSS is faulty could be optimized a lot. Please fix that. As long as you don't, XOOPS sucks. |
| Re: XHTML & CSS [designing without tables] |
| by russtik on 2006/1/19 15:00:12 Quote:
Aren't you missing the point? It doesn't matter how good the house looks if it's built on s**t foundations. Eventually it will fall down. The visually impaired man doesn't care how good the house looks, he just wants to be able to get around with ease. This is not to say that visual styling and layout are not important. But to ignore how pages are built or attempt to devalue well established "best working practices" is just... foolish IMHO. |
| Re: XHTML & CSS [designing without tables] |
| by skenow on 2006/1/15 3:07:04 (second attempt at posting this - I took too long the first time...) Basically, I think the real challenge is getting programmers out of the design, which is why XOOPS uses templates, themes, and smarty. And, I think the designers need some guidelines for proper theme development. Here's some things I have discovered - 1. Elements, Classes and IDs are not always used correctly in XOOPS (Core and Modules). You can often find the same ID tag on more than one element in a page, which is not valid - this should be a class, instead. 2. Module styles have set attributes for html elements that affect the entire site, not just the module's appearance. If you are going to style an element in your module, at least give it a class or ID so you don't break someone else's theme. 3. Inline styles make it necessary to edit the templates to get control of the style - not a good thing. 4. New selectors that need to be added to your theme's stylesheet so the module/block displays correctly are also not a good thing. 5. Having stylesheets all over the site is also not a good thing (how many places do I have to go to change the appearance of my site and the modules I have selected?) 6. Lots of nested elements makes it difficult to track down just what is affecting an element's appearance. Using WebDeveloper in Firefox (Outline Selected Element) sometimes doesn't get to the element before it goes out of the window.... 7. Different browsers display styles differently. Trying to create a stylesheet that works in all browsers can be maddening. A method for having multiple stylesheets to handle browser differences would be good. Here's some example code: le="color: #000000"><?php if (stristr($_SERVER["HTTP_USER_AGENT"], "Opera")) print "<link rel="stylesheet" href="".$sheet."opera.css" type="text/css" media="screen"></link>nt"; else if (stristr($_SERVER["HTTP_USER_AGENT"], "Netscape")) print "<link rel="stylesheet" href="".$sheet."netscape.css" type="text/css" media="screen"></link>nt"; else if (stristr($_SERVER["HTTP_USER_AGENT"], "Gecko")) print "<link rel="stylesheet" href="".$sheet."mozilla.css" type="text/css" media="screen"></link>nt"; else if (stristr($_SERVER["HTTP_USER_AGENT"], "MSIE")) print "<link rel="stylesheet" href="".$sheet."msie.css" type="text/css" media="screen"></link>nt"; } With, or without tables, all of these things need to be addressed in a XOOPS module/theme design document. </my 2 cents> |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|