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...@co...> - 2005-07-25 12:05:18
|
Yes, you're right. I misread your email. Thought you said stable2 -> 2.4... The tables are dropped and recreated, but I think the columns change. The details are all in org/bodington/installation/upgrade_2_1_to_2_1_1.sql Colin Alistair Young wrote: > surely they would have shown up between stable1 and 2.4.0? Does that > mean that deleted tables in stable2 ended up back in 2.4.0? > > Alistair > > On 25 Jul 2005, at 12:42, Colin Tatham wrote: > >> >> I was referring to schema changes between stable1 and stable2... >> >> >> Alistair Young wrote: >> >>> My eye breaking research so far: >>> 2.1.1 stable1 -> 2.4.0 >>> log_book_entries - columns added >>> log_book_pages tables - columns added >>> xml_tokens - columns added >>> xml_words - columns added >>> user_x509s created >>> Colin - no sign of any tables that were deleted. That's worrying! >>> Why do you need to delete tables in 2.4.0? >>> From a fresh install, no tables have been removed. >>> Alistair >>> On 25 Jul 2005, at 12:15, Colin Tatham wrote: >>> >>>> I think Alistair's starting point is what's deployed at UHI (stable2)? >>>> >>>> There were some database schema changes between stable1 and >>>> stable2 (from memory, although I have some notes: Logbook, XML >>>> repository) >>>> >>>> We had trouble upgrading from stable1 to 2_4, because the code >>>> that was supposed to run some SQL on the database to drop XML >>>> repository related tables didn't run, so we've ended up with a >>>> broken search tool (only finds resources created after the >>>> upgrade). It was looking for bod.properties identifying the >>>> current Bod version, which weren't present (and as far as I could >>>> tell don't ever get created unless you add them manually..) >>>> >>>> Colin >>>> >>>> Matthew Buckett wrote: >>>> >>>> >>>>> Alistair Young wrote: >>>>> >>>>> >>>>>>> still accepting more stuff into HEAD >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> so I'll work the other way as it's an upgrade path, so it seems >>>>>> logical to do: >>>>>> 2_1_1_stable2 -> 2_4 >>>>>> 2_4 -> 2_6 >>>>>> >>>>>> I'll ignore the rc "releases". >>>>>> >>>>>> >>>>> Looking at the release notes on sourceforge the 2.1.0 series was >>>>> the stable one and the 2.1.1 was aimed at being shapshots for >>>>> experiments/developers, but I may be wrong as I wasn't around in >>>>> the Bodington community when these versions were released. >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >>>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>>> informative Webcasts and more! Get everything you need to get up to >>>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>>> _______________________________________________ >>>> Bodington-developers mailing list >>>> Bod...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>> >>>> >>> ------------------------------------------------------- >>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>> informative Webcasts and more! Get everything you need to get up to >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@co...> - 2005-07-25 11:59:57
|
I'm working on keyword searching for WebLearn, will be finished by end of tomorrow. I'd prefer to finish that before adding EasyBuilder (and TextBlocks) but if anyone wants to look at them sooner, I can commit them to Bod head. I'm going to have to drop Edit Discussion Room Posts, unless someone else wants to look at that? Sean Mehan wrote: > We are here (Friday) (methinks): > > 1. HSQLDB - estimated 3 days - MB > 1. Quicklinks - 1 day AOC > 1. Textblocks - 1days - CT - Announcements goes to 2.8 > 1. Edit Discussion Room Posts - CT - done, throw it in! > 2. RSS - 1.5 days - MB > 2. EasyBuilder - 2days - CT not including keyword searching, html widget. > 2. Schema update - 3 days with tests - AY et al. > 3. Resource Search, Keyword only - 1 day - CT > > > anything coming off the list?-) > > I have taken 3. ACL - 2days - MB (this is without timed access support) > off the list. > > s > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Alistair Y. <ali...@sm...> - 2005-07-25 11:59:37
|
> the web application context > name = bodington is hardwired into the code I don't think so. I run it under all sorts of context names other than bodington, some of which I can't repeat before the 9pm watershed ;) Alistair On 25 Jul 2005, at 12:50, Brian Peter Clark wrote: > On a not-unrelated point, but more distantly related, perhaps. I > think that I am correct in saying that the web application context > name = bodington is hardwired into the code. > > I suggest that this might cause problems in the app server world > where you can set up the context at the press of a button at war > deployment time. > > Also, people might not like seing bodington in all their urls. > > Regards, > > Brian > > > > >> Peter Crowther wrote: >> >>>> From: [...] Alistair Young >>>> res.generic: >>>> strings_en.properties: >>>> system=CLAN >>>> >>>> templates: >>>> <localise id="system" /> >>>> >>>> change res.generic.strings_en.properties system=Weblearn for Ox >>>> etc. >>>> >>>> Alistair >>>> >>> >>> >>> Thanks - that's a much more specific answer than I could give. >>> Thought >>> there'd be something in place. >>> >>> - Peter >>> >>> >> >> I have to confess that I took my cue from Alistair and put strings of >> the form 'foo.bar=<!-- Bodington-->Bodington' into i18n resource >> property files, which I realized was retarded at the time because it >> makes sense in an un-i18n-ed template for finding rendering of the >> system name, but not in a resource property file ;-). >> >> To my mind it would probably make sense to: >> >> * standardize 'system' on something more meaningful like >> 'institutional.system.name'. >> * ensure that all templates that require this import the same generic >> resource file. >> * ensure that this 1 name-value pair is of the form: >> institutional.system.name=CLAN (i.e. *no* HTML comment that can >> end up >> in the title of non-compliant browsers!). >> >> I'm just flagging this up for now. Hey, I might even do this >> myself, but >> I'm working on QuickLinks right now. >> >> >> Alexis >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration >> Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> >> > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Brian P. C. <bm...@bm...> - 2005-07-25 11:54:06
|
On a not-unrelated point, but more distantly related, perhaps. I think that I am correct in saying that the web application context name = bodington is hardwired into the code. I suggest that this might cause problems in the app server world where you can set up the context at the press of a button at war deployment time. Also, people might not like seing bodington in all their urls. Regards, Brian > Peter Crowther wrote: > >>From: [...] Alistair Young > >>res.generic: > >>strings_en.properties: > >>system=CLAN > >> > >>templates: > >><localise id="system" /> > >> > >>change res.generic.strings_en.properties system=Weblearn for Ox etc. > >> > >>Alistair > > > > > > Thanks - that's a much more specific answer than I could give. Thought > > there'd be something in place. > > > > - Peter > > > > I have to confess that I took my cue from Alistair and put strings of > the form 'foo.bar=<!-- Bodington-->Bodington' into i18n resource > property files, which I realized was retarded at the time because it > makes sense in an un-i18n-ed template for finding rendering of the > system name, but not in a resource property file ;-). > > To my mind it would probably make sense to: > > * standardize 'system' on something more meaningful like > 'institutional.system.name'. > * ensure that all templates that require this import the same generic > resource file. > * ensure that this 1 name-value pair is of the form: > institutional.system.name=CLAN (i.e. *no* HTML comment that can end up > in the title of non-compliant browsers!). > > I'm just flagging this up for now. Hey, I might even do this myself, but > I'm working on QuickLinks right now. > > > Alexis > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@co...> - 2005-07-25 11:48:44
|
> Keep your > eyes peeled for: > > src/org/bodington/server/resources/Quicklink.sql There'll be more, for NewsFeeds, TextBlocks, ImageBlocks... Alexis O'Connor wrote: > Alistair Young wrote: > >> here's a daft question - is is only the sql files that are required >> or does SetupServlet do hard coded sql? >> >> Alistair >> > > I'm almost certain that SetupServlet only invokes SQL that is contained > within .sql files. > > I believe we're working on Wednesday as the cut-off point, so I'm just > warning you that there is another .sql to come for Quicklinks. Keep your > eyes peeled for: > > src/org/bodington/server/resources/Quicklink.sql > > It should be in by this afternoon. > > Alexis > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Alistair Y. <ali...@sm...> - 2005-07-25 11:48:26
|
surely they would have shown up between stable1 and 2.4.0? Does that mean that deleted tables in stable2 ended up back in 2.4.0? Alistair On 25 Jul 2005, at 12:42, Colin Tatham wrote: > > I was referring to schema changes between stable1 and stable2... > > > Alistair Young wrote: > >> My eye breaking research so far: >> 2.1.1 stable1 -> 2.4.0 >> log_book_entries - columns added >> log_book_pages tables - columns added >> xml_tokens - columns added >> xml_words - columns added >> user_x509s created >> Colin - no sign of any tables that were deleted. That's worrying! >> Why do you need to delete tables in 2.4.0? >> From a fresh install, no tables have been removed. >> Alistair >> On 25 Jul 2005, at 12:15, Colin Tatham wrote: >> >>> I think Alistair's starting point is what's deployed at UHI >>> (stable2)? >>> >>> There were some database schema changes between stable1 and >>> stable2 (from memory, although I have some notes: Logbook, XML >>> repository) >>> >>> We had trouble upgrading from stable1 to 2_4, because the code >>> that was supposed to run some SQL on the database to drop XML >>> repository related tables didn't run, so we've ended up with a >>> broken search tool (only finds resources created after the >>> upgrade). It was looking for bod.properties identifying the >>> current Bod version, which weren't present (and as far as I >>> could tell don't ever get created unless you add them manually..) >>> >>> Colin >>> >>> Matthew Buckett wrote: >>> >>> >>>> Alistair Young wrote: >>>> >>>> >>>>>> still accepting more stuff into HEAD >>>>>> >>>>>> >>>>> >>>>> >>>>> so I'll work the other way as it's an upgrade path, so it >>>>> seems logical to do: >>>>> 2_1_1_stable2 -> 2_4 >>>>> 2_4 -> 2_6 >>>>> >>>>> I'll ignore the rc "releases". >>>>> >>>>> >>>> Looking at the release notes on sourceforge the 2.1.0 series >>>> was the stable one and the 2.1.1 was aimed at being shapshots >>>> for experiments/developers, but I may be wrong as I wasn't >>>> around in the Bodington community when these versions were >>>> released. >>>> >>>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is sponsored by: Discover Easy Linux Migration >>> Strategies >>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>> informative Webcasts and more! Get everything you need to get up to >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >>> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration >> Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@co...> - 2005-07-25 11:46:40
|
> I'll do that. As long as we all agree to write a simple but meaningful comment if you ever close a bug instead of 'bug fixed'! (So that when someone else looks at the closed bugs, they can see *what* you fixed, in case it wasn't a complete fix, even tho you thought it was.) Colin Colin Tatham wrote: > Yes, sorry. I was being a bit 'dof' (South African for dim). I thought > there were issues, rather than just needing to assign access rights... > > I'll do that. > > Colin > > ____________________________________ > Colin Tatham > VLE Team > Oxford University Computing Services > > http://www.oucs.ox.ac.uk/ltg/vle/ > http://bodington.org > > > Peter Crowther wrote: > >>> From: [...] Colin Tatham >>> Bug trackers would get my vote. It will increase SF traffic. There's >>> a handy mail list to subscribe to if you want to be notified of any >>> bug reports, changes. We could assign developers to specific bugs. >>> >>> What do we need to sort out wrt access rights, Peter? >> >> >> >> <consults a project where I'm an admin> >> >> Someone with Admin rights needs to follow the instructions in >> https://sourceforge.net/docman/display_doc.php?docid=24202&group_id=1#tr >> acker_techs (steps 20 and 21) and add all us mere developers as Tracker >> Technicians to the particular Tracker that we're going to use. It might >> also be prudent to make at least one techie a Tracker Manager, as that >> techie can then change categories and so on within the Tracker. >> >> - Peter >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@co...> - 2005-07-25 11:42:56
|
I was referring to schema changes between stable1 and stable2... Alistair Young wrote: > My eye breaking research so far: > > 2.1.1 stable1 -> 2.4.0 > log_book_entries - columns added > log_book_pages tables - columns added > > xml_tokens - columns added > xml_words - columns added > > user_x509s created > > Colin - no sign of any tables that were deleted. That's worrying! Why > do you need to delete tables in 2.4.0? > > From a fresh install, no tables have been removed. > > Alistair > > On 25 Jul 2005, at 12:15, Colin Tatham wrote: > >> I think Alistair's starting point is what's deployed at UHI (stable2)? >> >> There were some database schema changes between stable1 and stable2 >> (from memory, although I have some notes: Logbook, XML repository) >> >> We had trouble upgrading from stable1 to 2_4, because the code that >> was supposed to run some SQL on the database to drop XML repository >> related tables didn't run, so we've ended up with a broken search >> tool (only finds resources created after the upgrade). It was looking >> for bod.properties identifying the current Bod version, which weren't >> present (and as far as I could tell don't ever get created unless you >> add them manually..) >> >> Colin >> >> Matthew Buckett wrote: >> >>> Alistair Young wrote: >>> >>>>> still accepting more stuff into HEAD >>>>> >>>> >>>> >>>> so I'll work the other way as it's an upgrade path, so it seems >>>> logical to do: >>>> 2_1_1_stable2 -> 2_4 >>>> 2_4 -> 2_6 >>>> >>>> I'll ignore the rc "releases". >>>> >>> Looking at the release notes on sourceforge the 2.1.0 series was the >>> stable one and the 2.1.1 was aimed at being shapshots for >>> experiments/developers, but I may be wrong as I wasn't around in the >>> Bodington community when these versions were released. >>> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@co...> - 2005-07-25 11:41:29
|
Yes, sorry. I was being a bit 'dof' (South African for dim). I thought there were issues, rather than just needing to assign access rights... I'll do that. Colin ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org Peter Crowther wrote: >>From: [...] Colin Tatham >>Bug trackers would get my vote. It will increase SF traffic. >>There's a >>handy mail list to subscribe to if you want to be notified of any bug >>reports, changes. We could assign developers to specific bugs. >> >>What do we need to sort out wrt access rights, Peter? > > > <consults a project where I'm an admin> > > Someone with Admin rights needs to follow the instructions in > https://sourceforge.net/docman/display_doc.php?docid=24202&group_id=1#tr > acker_techs (steps 20 and 21) and add all us mere developers as Tracker > Technicians to the particular Tracker that we're going to use. It might > also be prudent to make at least one techie a Tracker Manager, as that > techie can then change categories and so on within the Tracker. > > - Peter > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Peter C. <Pet...@me...> - 2005-07-25 11:35:46
|
> From: [...] Colin Tatham > Bug trackers would get my vote. It will increase SF traffic.=20 > There's a=20 > handy mail list to subscribe to if you want to be notified of any bug=20 > reports, changes. We could assign developers to specific bugs. >=20 > What do we need to sort out wrt access rights, Peter? <consults a project where I'm an admin> Someone with Admin rights needs to follow the instructions in https://sourceforge.net/docman/display_doc.php?docid=3D24202&group_id=3D1= #tr acker_techs (steps 20 and 21) and add all us mere developers as Tracker Technicians to the particular Tracker that we're going to use. It might also be prudent to make at least one techie a Tracker Manager, as that techie can then change categories and so on within the Tracker. - Peter |
|
From: Matthew B. <mat...@co...> - 2005-07-25 11:31:48
|
Colin Tatham wrote: > > Bug trackers would get my vote. It will increase SF traffic. There's a > handy mail list to subscribe to if you want to be notified of any bug > reports, changes. We could assign developers to specific bugs. > > What do we need to sort out wrt access rights, Peter? Shouldn't all developers be able to manage bugs? -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
|
From: Alistair Y. <ali...@sm...> - 2005-07-25 11:30:39
|
My eye breaking research so far: 2.1.1 stable1 -> 2.4.0 log_book_entries - columns added log_book_pages tables - columns added xml_tokens - columns added xml_words - columns added user_x509s created Colin - no sign of any tables that were deleted. That's worrying! Why do you need to delete tables in 2.4.0? From a fresh install, no tables have been removed. Alistair On 25 Jul 2005, at 12:15, Colin Tatham wrote: > I think Alistair's starting point is what's deployed at UHI (stable2)? > > There were some database schema changes between stable1 and stable2 > (from memory, although I have some notes: Logbook, XML repository) > > We had trouble upgrading from stable1 to 2_4, because the code that > was supposed to run some SQL on the database to drop XML repository > related tables didn't run, so we've ended up with a broken search > tool (only finds resources created after the upgrade). It was > looking for bod.properties identifying the current Bod version, > which weren't present (and as far as I could tell don't ever get > created unless you add them manually..) > > Colin > > Matthew Buckett wrote: > >> Alistair Young wrote: >> >>>> still accepting more stuff into HEAD >>>> >>> >>> >>> so I'll work the other way as it's an upgrade path, so it seems >>> logical to do: >>> 2_1_1_stable2 -> 2_4 >>> 2_4 -> 2_6 >>> >>> I'll ignore the rc "releases". >>> >> Looking at the release notes on sourceforge the 2.1.0 series was >> the stable one and the 2.1.1 was aimed at being shapshots for >> experiments/developers, but I may be wrong as I wasn't around in >> the Bodington community when these versions were released. >> > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Colin T. <col...@co...> - 2005-07-25 11:26:44
|
Bug trackers would get my vote. It will increase SF traffic. There's a handy mail list to subscribe to if you want to be notified of any bug reports, changes. We could assign developers to specific bugs. What do we need to sort out wrt access rights, Peter? Colin Peter Crowther wrote: >>From: [...] Antony Corfield >>How do we report bugs and who fixes them? We need >>something quick and clear. > > > Tracker on SF? This would, at least, give us the incentive to get the > access rights sorted out so that we can use it meaningfully... > > - Peter > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Antony C. <an...@sm...> - 2005-07-25 11:24:49
|
Once again Alexis, this seems to be the solution (how many pints is that now?) - is everyone agreed? If so, I'll split the work with you... On 25 Jul 2005, at 12:12, Alexis O'Connor wrote: > Peter Crowther wrote: >>> From: [...] Alistair Young >>> res.generic: >>> strings_en.properties: >>> system=CLAN >>> >>> templates: >>> <localise id="system" /> >>> >>> change res.generic.strings_en.properties system=Weblearn for Ox etc. >>> >>> Alistair >> Thanks - that's a much more specific answer than I could give. >> Thought >> there'd be something in place. >> - Peter > > I have to confess that I took my cue from Alistair and put strings of > the form 'foo.bar=<!-- Bodington-->Bodington' into i18n resource > property files, which I realized was retarded at the time because it > makes sense in an un-i18n-ed template for finding rendering of the > system name, but not in a resource property file ;-). > > To my mind it would probably make sense to: > > * standardize 'system' on something more meaningful like > 'institutional.system.name'. > * ensure that all templates that require this import the same generic > resource file. > * ensure that this 1 name-value pair is of the form: > institutional.system.name=CLAN (i.e. *no* HTML comment that can end up > in the title of non-compliant browsers!). > > I'm just flagging this up for now. Hey, I might even do this myself, > but I'm working on QuickLinks right now. > > > Alexis > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Colin T. <col...@co...> - 2005-07-25 11:15:20
|
I think Alistair's starting point is what's deployed at UHI (stable2)? There were some database schema changes between stable1 and stable2 (from memory, although I have some notes: Logbook, XML repository) We had trouble upgrading from stable1 to 2_4, because the code that was supposed to run some SQL on the database to drop XML repository related tables didn't run, so we've ended up with a broken search tool (only finds resources created after the upgrade). It was looking for bod.properties identifying the current Bod version, which weren't present (and as far as I could tell don't ever get created unless you add them manually..) Colin Matthew Buckett wrote: > Alistair Young wrote: > >>> still accepting more stuff into HEAD >> >> >> so I'll work the other way as it's an upgrade path, so it seems >> logical to do: >> 2_1_1_stable2 -> 2_4 >> 2_4 -> 2_6 >> >> I'll ignore the rc "releases". > > > Looking at the release notes on sourceforge the 2.1.0 series was the > stable one and the 2.1.1 was aimed at being shapshots for > experiments/developers, but I may be wrong as I wasn't around in the > Bodington community when these versions were released. > |
|
From: Peter C. <Pet...@me...> - 2005-07-25 11:14:04
|
> From: [...] Antony Corfield > Is that Gates/Bush democracy? Someone unilaterally changes the rules=20 > and everybody else has to conform... Communist democracy - you can use whatever browser you want, but IE is the only one on the system that you get handed... - Peter |
|
From: Alexis O'C. <ale...@co...> - 2005-07-25 11:12:57
|
Peter Crowther wrote: >>From: [...] Alistair Young >>res.generic: >>strings_en.properties: >>system=CLAN >> >>templates: >><localise id="system" /> >> >>change res.generic.strings_en.properties system=Weblearn for Ox etc. >> >>Alistair > > > Thanks - that's a much more specific answer than I could give. Thought > there'd be something in place. > > - Peter > I have to confess that I took my cue from Alistair and put strings of the form 'foo.bar=<!-- Bodington-->Bodington' into i18n resource property files, which I realized was retarded at the time because it makes sense in an un-i18n-ed template for finding rendering of the system name, but not in a resource property file ;-). To my mind it would probably make sense to: * standardize 'system' on something more meaningful like 'institutional.system.name'. * ensure that all templates that require this import the same generic resource file. * ensure that this 1 name-value pair is of the form: institutional.system.name=CLAN (i.e. *no* HTML comment that can end up in the title of non-compliant browsers!). I'm just flagging this up for now. Hey, I might even do this myself, but I'm working on QuickLinks right now. Alexis |
|
From: Antony C. <an...@sm...> - 2005-07-25 11:11:21
|
Is that Gates/Bush democracy? Someone unilaterally changes the rules and everybody else has to conform... On 25 Jul 2005, at 11:53, Peter Crowther wrote: > * Actually it isn't - we still have organisations who specify that the > apps we develop must work for the 90%- of users on IE5+ for PC and Mac, > and that they don't care about the other 10%+ of the Web user > community... democracy in action, I guess. |
|
From: Peter C. <Pet...@me...> - 2005-07-25 10:59:52
|
> From: [...] Alistair Young > you fancy doing it Peter? I'm doing sql! Wish I had time - as it stands I'm stealing time from two other projects on tight deadlines in order to bugfix. - Peter |
|
From: Antony C. <an...@sm...> - 2005-07-25 10:59:49
|
> Antony Corfield wrote: >> On 25 Jul 2005, at 10:35, Matthew Buckett wrote: >>> It seems like modifybig is no longer linked to from modify.html. >>> Are we not longer using modifybig.html and if so should we remove it >>> from the repository? >>> >>> I was never very keen on having these two modify pages as they >>> didn't save intermediate changes. Comments? >> Don't need it anymore > > Can we have the default textarea boxes a bit bigger then please as > they have shrunk. I can see that being able to see all the form on one > page is nice but they are now far too small to be able to type a > reasonable ammount of text in. already said yes > >>> >>> As a side note the medadocument modify.html does still link to >>> modifybig.html but that is because it hasn't been updated to the new >>> UHI Look and Feel. >> Shouldn't be there - it uses /default/modify.html > > But it should. mediadocument (Web Document) has a different use of the > introduction field and so there needs to be a comment about it. So the > modify page is needed so that the help text for the introduction is > still there when a user is editing that page. Good point! Committed with new style and above comment. Cheers, Antony > > -- > +--Matthew Buckett-----------------------------------------+ > | VLE Developer, Learning Technologies Group | > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | > +------------Computing Services, University of Oxford------+ > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
|
From: Peter C. <Pet...@me...> - 2005-07-25 10:59:28
|
> From: [...] Alistair Young > it was a joke ;) My apologies - sense of humour failure at this end since about the middle of last week. If anyone has some spare humour, I could do with some. - Peter |
|
From: Alistair Y. <ali...@sm...> - 2005-07-25 10:56:36
|
it was a joke ;) On 25 Jul 2005, at 11:53, Peter Crowther wrote: >> From: [...] Alistair Young >> >>> IE6 displays these, in violation of the HTML >>> spec. We should possibly do something to prevent their appearance. >>> >> yes, stop using IE6 >> > > Fine for me*, possibly less than ideal to tell institutions deploying > Bodington and allowing their students access from their own PCs. > > - Peter > > * Actually it isn't - we still have organisations who specify that the > apps we develop must work for the 90%- of users on IE5+ for PC and =20 > Mac, > and that they don't care about the other 10%+ of the Web user > community... democracy in action, I guess. > > - Peter > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dclick > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Alistair Y. <ali...@sm...> - 2005-07-25 10:53:50
|
you fancy doing it Peter? I'm doing sql! Alistair On 25 Jul 2005, at 11:51, Peter Crowther wrote: >> From: [...] Alistair Young >> res.generic: >> strings_en.properties: >> system=3DCLAN >> >> templates: >> <localise id=3D"system" /> >> >> change res.generic.strings_en.properties system=3DWeblearn for Ox = etc. >> >> Alistair >> > > Thanks - that's a much more specific answer than I could give. =20 > Thought > there'd be something in place. > > - Peter > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dclick > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
|
From: Peter C. <Pet...@me...> - 2005-07-25 10:53:30
|
> From: [...] Alistair Young > > IE6 displays these, in violation of the HTML > > spec. We should possibly do something to prevent their appearance. > yes, stop using IE6 Fine for me*, possibly less than ideal to tell institutions deploying Bodington and allowing their students access from their own PCs. - Peter * Actually it isn't - we still have organisations who specify that the apps we develop must work for the 90%- of users on IE5+ for PC and Mac, and that they don't care about the other 10%+ of the Web user community... democracy in action, I guess. - Peter |
|
From: Peter C. <Pet...@me...> - 2005-07-25 10:51:41
|
> From: [...] Alistair Young > res.generic: > strings_en.properties: > system=3DCLAN >=20 > templates: > <localise id=3D"system" /> >=20 > change res.generic.strings_en.properties system=3DWeblearn for Ox etc. >=20 > Alistair Thanks - that's a much more specific answer than I could give. Thought there'd be something in place. - Peter |
19 messages has been excluded from this view by a project administrator.
