Hi Marcus, all I've got the download buttons ready, but I will have to do some restructuring in the CSS to make this more future-proof (currently only one instance of each button is allowed because id's control everything). And IE is being a royal pain. At the same time, I'd like to make the CSS classes more semantic than #optionitem1 (e.g. something like .button-green)
You can see the buttons at: http://download.openoffice.org/cachedimages/option4-bg.png (for RCs) and http://download.openoffice.org/cachedimages/option5-bg.png (for dev builds) I've lightened the download arrow for the RC builds a little and used the darker orange arrow for the dev build image. Regards, Ivan. On Tue, Jan 20, 2009 at 2:32 AM, Marcus Lange <[email protected]> wrote: > Ivan M wrote: > > Hi Ivan, > >> On Fri, Jan 16, 2009 at 11:02 PM, Marcus Lange <[email protected]> >> wrote: >>> >>> [...] >>>> >>>> * The page does not seem to scale to 800x600 >>> >>> AFAIK the requirement for all websites is to support 1024x768 as minimum. >>> Do >>> you still work with 800x600? >> >> Thankfully, no :). But the Download home page displays reasonably well >> at 800x600 with no horizontal scrolling, so I was just wondering why >> your proposal does not seem to scale for widths below 1024px. It's not >> a major issue - there probably aren't very many people still using >> 800x600, but if can be scaled down, why not? I can help out with this >> if necessary - it should be reasonably easy to do. > > OK, we should keep an eye on 800x600 if possible but concentrate on > 1024x768. > >>>> * The blue and green download buttons should not be used for RCs/Dev >>>> builds - e.g. from the download homepage, their meanings are: blue >>>> download button is for extensions, green button is for stable major >>>> releases. I would advise against recontextualizing these buttons. >>> >>> I've made 4 rows just to see if this would still fit on the page. I think >>> we >>> will not see 4 rows in live but who knows. However, I've removed it now. >>> >>> Also the colors will change. Have you seen my color suggestion in the >>> previous posting? >> >> I'm not sure how fiery the buttons should be to alert users about >> these downloads - I would suggest: > > What about the little disclaimer text above the colored links? Do you think > it is sufficient? If so, then we can use some not that fiery colors maybe. > >> - Lime for RCs (more yellow than green) -or- the same as the bottom >> button on download.OOo > > I would like to see the same yellow as on download.ooo. > >> - Orange for Dev 310 >> - The same for Dev 300 if both have a similar status as dev builds - >> having two different colors would suggest (IMO) that one is less >> stable than the other (I'm not sure if this is the case or not - if it >> is, then something darker than the button for Dev 310 would be >> appropriate) > > I suggested different colors because of the different codelines. To make the > difference also clear from the colors, not only from the text. But in > general both are unstable builds. > > At this level OOO300 is more stable than DEV300. But this is changing > always. ;-) > > IMHO we should see both codelines as unstable as this will be true most of > the time. So, orange would be nice or light red. > >> I can make up some buttons based on whatever colors are chosen if >> you'd like, and I can add some extra styles to the main download >> stylesheet to fix the current CSS issues once the colors are decided >> upon. > > It would be great if you can help with CSS styling. :-) I've uploaded the > recent changes, so that my latest update is online now. > > Maybe you can create one orange (OOO310) and one light red (DEV300) colored > link? Then we can see directly what looks better and what we should use > finally. > >>>> Other page >>>> >>>> * Those gray tables look really unfriendly. Cells could really do with >>>> some padding. >>> >>> In order to use a known color I've used the same gray from the bigger >>> other.html page. Have you got a favorite color that you would like to >>> see? >> >> It was more of a first impression, but in this case, the >> 'unfriendliness' might even be functional (sending people who don't >> know what they're doing away) :) > > I would say let us stay with this gray. We can change it later on when other > people have the same feeling. Also here my latest update is online now. > > Thanks > > Marcus > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
