Menu
▾
▴
bodington-developers — Mailing list for Bodington developers
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(41) |
May
(353) |
Jun
(133) |
Jul
(534) |
Aug
(401) |
Sep
(219) |
Oct
(86) |
Nov
(144) |
Dec
(61) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(200) |
Feb
(130) |
Mar
(345) |
Apr
(153) |
May
(247) |
Jun
(338) |
Jul
(222) |
Aug
(70) |
Sep
(39) |
Oct
(27) |
Nov
(76) |
Dec
(30) |
| 2007 |
Jan
(81) |
Feb
(44) |
Mar
(9) |
Apr
|
May
(3) |
Jun
(2) |
Jul
(34) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(6) |
| 2008 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Colin T. <col...@ou...> - 2006-06-21 08:51:58
|
Jon Maber wrote: > I have commit access to the CVS repository with my new user name so Ive > stuck these updates in. > > Ive only tested on Firefox and IE6. Could someone try it out on Safari? I've tried on Linux/Firefox, Win/Firefox and Win/IE 6 (with user settings set to defaults) and found the following in all cases. Is anyone else seeing them, are they intended? - text size of links has changed (bigger) - size of 'Search' text and button is smaller - search box positioning has moved up to top of frame - all text and toggle icons have moved up to top of logged in div - (IE6 only) title of current resource moved up to top of frame Colin -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
|
From: Matthew B. <mat...@ou...> - 2006-06-21 08:07:28
|
Jon Maber wrote: > I have commit access to the CVS repository with my new user name so Ive > stuck these updates in. > > Ive only tested on Firefox and IE6. Could someone try it out on Safari? Can I suggest that we also have Bodington work reasonable well on IE 5.5 as it has a reasonable marketshare still. http://www.w3schools.com/browsers/browsers_stats.asp For WebLearn we had a bit of discussion about supported browsers and came up with: Full Supported - Everything works as expected. Testing should mainly be done against these browsers. Firefox (1.0+) - All Platforms Internet Explorer (5.5, 6.0+) - Windows Well Supported - The whole site display correctly and is useable although some advanced features may not work correctly, although there should be work arounds. Safari (?) - Mac Opera (7.5+) - all Platforms Working - These browsers allow you to use WebLearn but we do not guarantee how it will display. All the information should still be readable though and you should be able to use most of the functionality. Internet Explorer - Mac Opera Mini - Mobile Phones/PDAs? Notes: All of WebLearn should work without any plugins and with JavaScript turned of although it is perfectly acceptable to use these technologies to enhance the experience (eg RTWEdit). Of course all we can do is affect the tool, nothing at the moment stops users uploading material isn't accessable. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
|
From: Sean M. <se...@sm...> - 2006-06-20 17:19:08
|
I would suggest concentrating on testing the release package. The added benefit is to start creating a testing plan, but if we get a reliable build out on time, that is the biggest win, IMHO. s <quote who=3D"Andrew Booth"> > Sounds good, as long as the option to opt out of the 'advice' to the > student > remains. > > Aggie > > -----Original Message----- > From: bod...@li... > [mailto:bod...@li...] On Behalf O= f > Jon > Maber > Sent: 20 June 2006 17:00 > To: Bodington developers > Subject: [Bodington-developers] Testing - Your opinion required. > > I'm running out of time for the testing work on 2.8 and I would like to > hear from you about the following proposal; > > Adding exemplar testing instructions into the templates of a single > Bodington tool. > * Work on MCQ tool only. > * Add command to left page visible only to sysadmin. > * Opens new browser window with a full set of instructions on testing > the tool. > * Will include printable forms with tick boxes etc. > * When a developer adds functionality s/he edits the test instructions > to match. > > I picked out the MCQ tool because it also has on-line help files (which > is another kind of exemplar). > > What do you all think about this? > > Jon > > > > _______________________________________________ > 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 > --=20 Sean Mehan Head of e-Frameworks Learning and Information Services UHI |
|
From: Jon M. <jo...@te...> - 2006-06-20 16:58:35
|
Paul Davis wrote: > I agree with Colin > > plus anything in one > tool just makes all the others look bad! > ...which adds a little extra incentive to developers to do a thorough job. But fair enough, there isnt enough time to match that in all the other tools in 2.8 - perhaps something for 2.10. O.K. 1-2 against. Jon |
|
From: Paul D. <pau...@co...> - 2006-06-20 16:48:41
|
I agree with Colin Major push has to be getting this build out and reliable, plus anything in one tool just makes all the others look bad! Paul In message <449...@ou...> Bodington developers <bod...@li...> writes: > Jon Maber wrote: > > I'm running out of time for the testing work on 2.8 and I would like to > > hear from you about the following proposal; > ... > > > What do you all think about this? > > My view is that the most useful use of your time would be to continue testing -- it's already proven > useful. (I realise that that would mean you don't fulfil half of the brief, which was to start > devising a test plan for future, but I think that's less important.) > > I also think that if you developed the test plan for a single tool, we would run the risk of never > having the rest of Bod added, and so it wouldn't be useful :-( > > 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 > |
|
From: Jon M. <jo...@te...> - 2006-06-20 16:46:26
|
Colin Tatham wrote: > > I also think that if you developed the test plan for a single tool, we would run the risk of never > having the rest of Bod added, and so it wouldn't be useful :-( > I thought there might be some differences of opinion which is why I didn't just dive in and do it. So that's a 1-1 draw so far. Anyone else want to take a shot? Jon |
|
From: Colin T. <col...@ou...> - 2006-06-20 16:35:29
|
Jon Maber wrote: > I'm running out of time for the testing work on 2.8 and I would like to > hear from you about the following proposal; ... > What do you all think about this? My view is that the most useful use of your time would be to continue testing -- it's already proven useful. (I realise that that would mean you don't fulfil half of the brief, which was to start devising a test plan for future, but I think that's less important.) I also think that if you developed the test plan for a single tool, we would run the risk of never having the rest of Bod added, and so it wouldn't be useful :-( Colin -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
|
From: Andrew B. <a.g...@le...> - 2006-06-20 16:12:43
|
Sounds good, as long as the option to opt out of the 'advice' to the = student remains. Aggie -----Original Message----- From: bod...@li... [mailto:bod...@li...] On Behalf Of = Jon Maber Sent: 20 June 2006 17:00 To: Bodington developers Subject: [Bodington-developers] Testing - Your opinion required. I'm running out of time for the testing work on 2.8 and I would like to=20 hear from you about the following proposal; Adding exemplar testing instructions into the templates of a single=20 Bodington tool. * Work on MCQ tool only. * Add command to left page visible only to sysadmin. * Opens new browser window with a full set of instructions on testing=20 the tool. * Will include printable forms with tick boxes etc. * When a developer adds functionality s/he edits the test instructions=20 to match. I picked out the MCQ tool because it also has on-line help files (which=20 is another kind of exemplar). What do you all think about this? Jon _______________________________________________ Bodington-developers mailing list Bod...@li... https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Jon M. <jo...@te...> - 2006-06-20 15:59:52
|
I'm running out of time for the testing work on 2.8 and I would like to hear from you about the following proposal; Adding exemplar testing instructions into the templates of a single Bodington tool. * Work on MCQ tool only. * Add command to left page visible only to sysadmin. * Opens new browser window with a full set of instructions on testing the tool. * Will include printable forms with tick boxes etc. * When a developer adds functionality s/he edits the test instructions to match. I picked out the MCQ tool because it also has on-line help files (which is another kind of exemplar). What do you all think about this? Jon |
|
From: Antony C. <an...@sm...> - 2006-06-20 15:54:41
|
yep On 20 Jun 2006, at 16:51, Jon Maber wrote: > I have commit access to the CVS repository with my new user name so Ive > stuck these updates in. > > Ive only tested on Firefox and IE6. Could someone try it out on Safari? > > Jon > > > > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Jon M. <jo...@te...> - 2006-06-20 15:51:13
|
I have commit access to the CVS repository with my new user name so Ive stuck these updates in. Ive only tested on Firefox and IE6. Could someone try it out on Safari? Jon |
|
From: Jon M. <jo...@te...> - 2006-06-20 12:58:25
|
Colin Tatham wrote: > Jon Maber wrote: > >> My user ID doesn't have access to the CVS so I can't commit. >> > > I can sort that if you need me to... > Yes please. |
|
From: Jon M. <jo...@te...> - 2006-06-20 12:57:24
|
Antony Corfield wrote: > is this a move to css files! > No, its a case of making the best of a bad job. ;-) Jon |
|
From: Antony C. <an...@sm...> - 2006-06-20 12:30:49
|
On 20 Jun 2006, at 13:23, Jon Maber wrote:
> Antony Corfield wrote:
>> Thanks John we were about to crop title text in top frame.
> Do you mean output less text from the template?
Yes I did but will test your updates... is this a move to css files!
> The styling should make that unnecessary - the full space will be used
> and any extra text will be cropped at the bottom of the div.
>> Have also moved search to LHS frame and other links from top div to
>> 'login' div. Have you committed these files?
>>
> My user ID doesn't have access to the CVS so I can't commit.
>
> I've attached another set of versions to this Email because I got I.E.
> 6 working in a Windows emulator and there were problems. At the same
> time I changed the way styling adapts to the thinner top frame used
> with PDAs. Now the normal css file is always included and a very small
> css file is added to the HTML if the slim line top frame has been
> selected. This makes it much easier to maintain the CSS.
>
> Jon
>
>
>
>
> #NavigationContainer {
> /* frame is fixed height so this must be fixed height */
> height:24px;
> }
>
> #Search{
> height:0px;
> }
>
> #SearchKeywords{
> height:0px;
> }
> #SearchSubmit{
> height:0px;
> }
>
> #LoggedOnContainer{
> /* Fixed height to make sure border is visible */
> height: 15px;
> }
>
> .Title {
> /* Title is put in a fixed height box so the layout manager
> knows where the middle is.
> */
> height:22px;
> }
> preference.navigation.illustrations stylesheet small
> preference.navigation.nav_bar_height small big
> linkout
>
> Options notifyswitch Options Advanced Search
> title
> hidden preference.navigation.illustrations <image.tiff>
> <image.tiff> EEEE, d MMM yyyy You are logged in as:
> nameofuser
> body {
> /* ensure sub blocks touch edges of frame */
> margin: 0px;
> }
>
>
> #NavigationContainer {
> /* frame is fixed height so this must be fixed height */
> height:46px;
> /* prevents colour preferences from working - bad thing */
> background-color: #EEEEEE;
> /* at least it makes sure that there is always a high contrast */
> color: black;
> /* thin rule across bottom of box separates it from lower box */
> border-bottom:1px solid #aaaaaa;
> /* if the user increases text size it will be cropped within the
> 46px height */
> overflow: hidden;
> }
>
> #NavigationContainer :link {
> color: blue;
> }
>
> #NavigationContainer :visited {
> color: purple;
> }
>
> #Icon{
> /* does this really need properties? */
> }
>
>
> #Link{
> /* This box has the search and command sub boxes and floats on the
> right */
> /* It has to float to allow the title text to flow in the middle
> */
> float:right;
> text-align: right;
> padding: 0px 15px 0px 0px;
> margin: 0px 0px 0px 0px;
> }
>
> #Search{
> /* makes sure anything that creeps out of box is clipped */
> overflow: hidden;
> /* container box has fixed height so this must too */
> height: 18px;
> width: 250px;
> padding: 0px 0px 0px 0px;
> margin: 0px 0px 0px 0px;
> }
>
>
> #Search form{
> /* This is a bit of a bodge to make sure that the form element
> doesnt add extra space and push the input elements downwards
> */
> font-size: 0px;
> margin: 0px 0px 0px 0px;
> padding: 0px 0px 0px 0px;
> }
>
>
> #SearchKeywords{
> /* The text input has fixed dimensions and fixed font size because
> it has to fit in a fixed height box. However, in Firefox there
> is
> no such thing as a fixed font size so it goes out of whack on
> big
> text sizes.
> */
> font-size: 9px;
> height:18px;
> width:150px;
> margin: 0px 0px 0px 0px;
> padding: 0px 0px 0px 0px;
> }
> #SearchSubmit{
> /* Same considerations for button input */
> font-size: 9px;
> height:18px;
> margin: 0px 0px 0px 0px;
> padding: 0px 0px 0px 0px;
> }
>
> #Commands{
> /* There is space for the text to enlarge so a relative font size
> is specified.
> */
> font-size: 75%;
> text-align: right;
> padding: 0px 0px 0px 0px;
> margin: 0px 0px 0px 0px;
> }
>
> #LoggedOnContainer{
> /* This is the other main box. It doesnt matter if contents spill
> out of the bottom edge because that will be clipped by the frame
> */
> background-color: #ffffff;
> color: black;
> margin: 0px 0px 0px 0px;
> padding: 0px 0px 0px 0px;
> /* Fixed height to make sure border is visible */
> height: 19px;
> width:100%;
> border-bottom: 1px solid #aaaaaa;
> }
>
> #LoggedOnContainer :link {
> color: blue;
> }
>
> #LoggedOnContainer :visited {
> color: purple;
> }
>
> #toggleLeftFrame img{
> margin: 2px 0 0 2px;
> }
>
> .Text {
> font-family: Verdana, Arial Unicode MS, Helvetica, sans-serif;
> font-size:0.70em;
> }
>
> .Title {
> /* Title is put in a fixed height box so the layout manager
> knows where the middle is.
> */
> height:44px;
> /* A table cell treats the vertical align differently */
> display: table-cell;
> /* A single line of text goes in the middle of the space but if
> the title
> wraps to two lines the top line shifts up. When the box is
> filled it
> aligns at the top.
> */
> vertical-align: middle;
> font-size: 100%;
> font-weight:bold;
> padding: 0px 0px 0px 8px;
> margin: 0px 0px 0px 0px;
> line-height: 100%;
> }
>
>
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
|
|
From: Colin T. <col...@ou...> - 2006-06-20 12:29:25
|
Jon Maber wrote: > My user ID doesn't have access to the CVS so I can't commit. I can sort that if you need me to... -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
|
From: Jon M. <jo...@te...> - 2006-06-20 12:24:00
|
Antony Corfield wrote: > Thanks John we were about to crop title text in top frame. Do you mean output less text from the template? The styling should make that unnecessary - the full space will be used and any extra text will be cropped at the bottom of the div. > Have also > moved search to LHS frame and other links from top div to 'login' div. > Have you committed these files? > My user ID doesn't have access to the CVS so I can't commit. I've attached another set of versions to this Email because I got I.E. 6 working in a Windows emulator and there were problems. At the same time I changed the way styling adapts to the thinner top frame used with PDAs. Now the normal css file is always included and a very small css file is added to the HTML if the slim line top frame has been selected. This makes it much easier to maintain the CSS. Jon |
|
From: Antony C. <an...@sm...> - 2006-06-20 12:10:47
|
Thanks John we were about to crop title text in top frame. Have also moved search to LHS frame and other links from top div to 'login' div. Have you committed these files? On 19 Jun 2006, at 17:00, Jon Maber wrote: > Matthew Buckett wrote: >> Jon Maber wrote: >> >>> Over the last week or so Ive got increasingly irritated by >>> Bodington's >>> top frame and so I took a couple of hours out from the testing >>> programme >>> to fix it. The best results will need CSS 2.1 compliant browsers >>> but it >>> shouldn't be too bad on CSS 1 browsers. >>> >> >> Nice one. >> Could you outline the bugs that this fixes? >> > Yep... > o For long titles and large font sizes the title reaches across to the > search and commands box on the right and that box pops out of view and > the title texts goes to the right of the page before wrapping. > o As the font is enlarged the margin above the text elements increases > too so the text drifts out of view. > o As the font is enlarged it spills out of its designated div and goes > over the box below. > These are all fixed although there is no way to stop the text > eventually > becoming illegible when it is very big because it gets cropped. The fix > to the second bug only works on CSS 2.1 compliant browsers. > > Another bug which I've not fixed: > o The background colours in the top frame are hardwired in a static CSS > file but the foreground colours are taken from the dynamic CSS - a > recipe for disaster. > Temp fix - add foreground colours to the static CSS. Proper fix - > process all the colours. (Which I could do given a little funding....) > > Jon > > > > > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Jon M. <jo...@te...> - 2006-06-20 11:40:17
|
I've finished the job off. Now all the colours are fixed, rather than just the background colours. Fixed background colours break the accessibility options but having fixed background and foreground colours breaks it less. For example, if the user selected white text on black background the top frame became totally illegible because it produced white text on an off-white background. There are many other templates which are still very dodgy. I found there were three different stylesheets for the top frame but this is not necessary - Ive reduced it to two, which has also involved chopping some code out of the template. Jon P.S. Sean, can I have access to check in to the CVS? In the meantime I've attached the files to this Email. |
|
From: Andrew B. <a.g...@le...> - 2006-06-20 10:08:51
|
They are used in generating usernames automatically. Aggie -----Original Message----- From: bod...@li... [mailto:bod...@li...] On Behalf Of Matthew Buckett Sent: 20 June 2006 09:29 To: Bodington Developers Subject: [Bodington-developers] Users Initials Although we store the initials for a user (along with the surname and display name) it seems they aren't really ever used by the interface (apart from the user directory tool). Was the original reason for storing them a Leeds requirement? -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ _______________________________________________ Bodington-developers mailing list Bod...@li... https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Jon M. <jo...@te...> - 2006-06-20 09:26:41
|
Matthew Buckett wrote:
> Although we store the initials for a user (along with the surname and
> display name) it seems they aren't really ever used by the interface
> (apart from the user directory tool). Was the original reason for
> storing them a Leeds requirement?
>
>
If you use the standard user creation tool and don't specify the user
name the initials are used to form the user name.
The formula is {admin zone prefix}{a number}{users initials}
The number is the lowest number that can be used while making the user
name unique.
Jon
|
|
From: Matthew B. <mat...@ou...> - 2006-06-20 08:29:28
|
Although we store the initials for a user (along with the surname and display name) it seems they aren't really ever used by the interface (apart from the user directory tool). Was the original reason for storing them a Leeds requirement? -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
|
From: Jon M. <jo...@te...> - 2006-06-19 16:09:12
|
Jon Maber wrote: > The fix > to the second bug only works on CSS 2.1 compliant browsers. > Meant to say third bug. |
|
From: Jon M. <jo...@te...> - 2006-06-19 16:00:34
|
Matthew Buckett wrote: > Jon Maber wrote: > >> Over the last week or so Ive got increasingly irritated by Bodington's >> top frame and so I took a couple of hours out from the testing programme >> to fix it. The best results will need CSS 2.1 compliant browsers but it >> shouldn't be too bad on CSS 1 browsers. >> > > Nice one. > Could you outline the bugs that this fixes? > Yep... o For long titles and large font sizes the title reaches across to the search and commands box on the right and that box pops out of view and the title texts goes to the right of the page before wrapping. o As the font is enlarged the margin above the text elements increases too so the text drifts out of view. o As the font is enlarged it spills out of its designated div and goes over the box below. These are all fixed although there is no way to stop the text eventually becoming illegible when it is very big because it gets cropped. The fix to the second bug only works on CSS 2.1 compliant browsers. Another bug which I've not fixed: o The background colours in the top frame are hardwired in a static CSS file but the foreground colours are taken from the dynamic CSS - a recipe for disaster. Temp fix - add foreground colours to the static CSS. Proper fix - process all the colours. (Which I could do given a little funding....) Jon |
|
From: Matthew B. <mat...@ou...> - 2006-06-19 15:51:16
|
Jon Maber wrote: > Over the last week or so Ive got increasingly irritated by Bodington's > top frame and so I took a couple of hours out from the testing programme > to fix it. The best results will need CSS 2.1 compliant browsers but it > shouldn't be too bad on CSS 1 browsers. Nice one. Could you outline the bugs that this fixes? -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
|
From: Jon M. <jo...@te...> - 2006-06-19 15:45:11
|
Over the last week or so Ive got increasingly irritated by Bodington's top frame and so I took a couple of hours out from the testing programme to fix it. The best results will need CSS 2.1 compliant browsers but it shouldn't be too bad on CSS 1 browsers. This is still a bit of a compromise because it still works around the frame set and the fact that the top frame height is fixed but the font size is variable. The boxes in the frames now have fixed heights and are set to crop any text that overflows the border. The padding and margins is fixed in units of pixels to prevent the text drifting south as it is enlarged. A key change is to put the title text last in the top box so that it flows between the right and left floating sub-boxes. At present I dont have access to commit source to the CVS with my new user name so Ive attached the two files that Ive edited so you can test what Ive done with various browsers. (I've only tested with Firefox). Jon |
19 messages has been excluded from this view by a project administrator.
