From: Antony C. <an...@sm...> - 2006-06-22 09:05:47
|
How about a much simpler approach?!! Just add a method 'public static String trimText(String text, int maxLength)' to org.bodington.util.TextUtils and use that whenever there's a limited space for displaying text? Could always use title attribute in link to display full text. As I said we've also removed search and links from the navigation div so we have more space to play with. On 21 Jun 2006, at 16:56, Jon Maber wrote: > In summary, > o There is a good solution - using CSS 2.1, trouble is it requires > browsers to properly support CSS 2.1 > o Bad browsers mean we need to use bad HTML and/or bad CSS > o My conclusion is that we have to deal with the whackier browsers for > the time being and plan for most browsers properly supporting CSS in a > year or two's time. > > Therefore I propose an interim solution, i.e. the use of a very simple > table with a fixed height. One cell on the left would contain the > navigation icons and the title and within that the icons would float > left therefore allowing the title to wrap to two or more lines beside > it. A second cell on the right would have a fixed width and contain... > ...what? Just the quick search? The use of the table makes it possible > to vertically centre all the contents which would be neat and should > work on all browsers. > > The rest of the frame could be outside the table or in a second one row > table and could also vertically centre the contents. > > Jon > > > Owen Davies wrote: >> having spent a fair bit of time on this, i have come to the >> conclusion that >> the only justifiable solution is to have a vertical scroll bar on the >> top >> frame, because any other solution prevents users who enlarge their >> text from >> viewing some of the site content and/or functionality. that is, of >> course, >> until the dreaded frames are ditched! >> >> owen >> ----- Original Message ----- >> From: "Colin Tatham" <col...@ou...> >> To: "Bodington developers" >> <bod...@li...> >> Sent: Wednesday, June 21, 2006 3:50 PM >> Subject: Re: [Bodington-developers] Top frame styling improvement - >> commited >> to HEAD >> >> >> >>> Jon Maber wrote: >>> >>>> A not very pro CSS solution would be to go back to the use of a >>>> table. >>>> I.e. one row, two cells. The height of the row could be fixed and >>>> the >>>> width of the right hand cell fixed. This solution would not be too >>>> bad >>>> for accessibility because it could be navigated linearly and would >>>> work >>>> better with browsers that implement CSS to version 1 or dont handle >>>> it >>>> at all. What do you think about tables? >>>> >>> If it works I wouldn't mind. We need to find a better overall >>> solution at >>> some point, so this would >>> only be in the interim. >>> >>> I think we should also decide what the priorities are, as we no-one >>> seems >>> to have found the perfect >>> solution yet (we've also had Owen here looking at it for quite a >>> while). >>> Visual appearance? Text >>> re-sizing in browser? Displaying full title rather than abbreviating >>> it? >>> Limiting max number of >>> parent icons to display? >>> >>> Colin >>> >>> -- >>> ____________________________________ >>> Colin Tatham >>> VLE Team >>> Oxford University Computing Services >>> >>> http://www.oucs.ox.ac.uk/ltg/vle/ >>> http://bodington.org >>> >>> >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >>> >> >> >> >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> >> > > > > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |