Hi Alexandro, Goran, Many thanks for your constructive feedback. On Tue, Nov 25, 2008 at 10:34 AM, Alexandro Colorado <[EMAIL PROTECTED]> wrote: > I brought this point a few months back and told me that it was soooo > dificult. Since I am not a JSP developer I thought the template was embedded > in the code like PHP usually handle things. Which btw is NOT dificult at > all to read html from php.
This is the problem: I don't see what's so difficult about doing this, and I hope someone can explain it to me - test.OOo seems to be coping without tables - IssueZilla seems fine as well (e.g., http://test.openoffice.org/issues/show_bug.cgi?id=200) > Java developers don't care about W3C. You can also see this on the Save your > OOo document as HTML 4 with all their tags in uppercaps which is also not > recomended. OOo's HTML rendering is a different issue (which should definitely be addressed). But with the website, we have complete control over CollabNet's HTML skeleton - the template covers everything from the DOCTYPE tag to the closing of the HTML tag. Plus there are some basic functions (e.g. if, else) that allow us to customize this structure in certain cases. > I actually encourage to go tableless and maybe adding more span tags around > so that the content becomes more manageable. Could you please give me an example of where more span tags would help? I'm not against it, but I don't know where they could/should go. > I would like to propose some CSS toolkit so the projects can have a better > way to homoneagize their classes. Buttons and roundcorner elements should be > written in CSS and be documented on the Wiki so that project can re-utilize > this across the board. The problem with this is that rounded corners are a CSS3 feature, supported only by a few browsers Even then, we can't use border-radius (invalid CSS2 property). We have to have -moz-border-radius: 3px; -khtml-border-radius: 3px; -webkit-border-radius: 3px; So I'm afraid this will be something to look at in the more distant future. The other problem is that the Wiki CSS is quite different to the OOo homepage, and we can't easily change class names because they are generated by MediaWiki. The tabs were just one example; on the website we can have those span tags inside, but on the wiki we cannot do this without editing core MediaWiki files. > I would also want to have infoboxes like the ones at yahoo.com portal where > you have boxes with tabs that show different content. Some would argue that this would be information overload, which goes against the original motives for the new design. Even if we had these tabs, the content would have to be manually updated. What I would like to see is a RSS feed link on the homepage, and a link tag in the HTML to a RSS feed for OOo updates (e.g. important news, new version updates), etc. > Also i would like to propose building some wiki documentation about how to > position projects pages. Like best practices, adding a significant impact > image. Define the look & feel and colors that we recomend to use (preffered > hex). Could you please elaborate a little on this? I'm interested in this kind of idea, but that is what I'm trying to do with the Website Style Guide - is there anything you would like to see there, or do you have any ideas on how it could be improved? (except, of course, with more information about CSS which I still have to add :) ) Goran, lots of good points from you (and bugs :) ). On Tue, Nov 25, 2008 at 11:02 AM, Goran Rakic <[EMAIL PROTECTED]> wrote: > [...] > I don't know if we need min-width property (together with IE hack) for > content page. If screen is not wide enough, #campaign div is floated > under #actionstatements but this can also be a feature, not a bug. This is definitely a bug, and a nasty one too. I have added a min-width property to #content so it should not be moving below #navcolumn any more. I have also set #navcolumn to display: none for the homepage, so it looks as it should. The header bug should only be on test.OOo now. That's on my needs-to-be-fixed list, along with the IE6 search box bug. Thanks again for your feedback! - Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
