bodington-developers — Mailing list for Bodington developers

Re: [Bodington-developers] Commit privileges to HEAD

[<mic...@bo...>]

Ohhhh I'm not sure... He sounds a bit dodgy to me  ;-)

I'll added him if no one has any objections.

mic...@bo...
___________________________

The Free Open Source VLE
Accessible, Flexible & Free
http://bodington.org/
___________________________



Adam Marshall wrote:

>Colin would be able to do that - but he's got the afternoon off. 
>
>Do we need to vote on whether Peter is allowed in? I think it's pretty clear
>that non of us would have an issue with this.
>
>adam
>
>--
>Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
>Shameless plug:      Use the Bodington VLE http://bodington.org
>Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
>Cheese of the month: Cheshire (not to be underestimated) 
>
>| -----Original Message-----
>| From: bod...@li... [mailto:bodington-
>| dev...@li...] On Behalf Of Peter Crowther
>| Sent: 26 May 2005 13:10
>| To: bod...@li...
>| Subject: [Bodington-developers] Commit privileges to HEAD
>| 
>| I've got a couple of changes to the IMS content packaging work that I'd
>| like to check in before continuing.  I don't have commit access to HEAD
>| on sf.net.  Assuming we are willing for me to make a pig's ear of the
>| system, could some kind admin type check out CVSROOT/avail, add 'ozzard'
>| to the list of users on line 4 (the bodington branch) and commit the
>| change?  If not, who's willing to undertake to check in my changes?
>| 
>| 		- Peter
>| 
>| --
>| Peter Crowther, Director, Melandra Limited
>| John Dalton House, 121 Deansgate, Manchester M3 2AB
>| t: +44 (0)161 828 8736  f: +44 (0)161 832 5683
>| 
>| 
>| -------------------------------------------------------
>| SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
>| online with coworkers and clients while avoiding the high cost of travel
>| and
>| communications. There is no equipment to buy and you can meet as often as
>| you want. Try it free.http://ads.osdn.com/?ad_idt02&alloc_id135&op=ick
>| _______________________________________________
>| Bodington-developers mailing list
>| Bod...@li...
>| https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
>online with coworkers and clients while avoiding the high cost of travel and
>communications. There is no equipment to buy and you can meet as often as
>you want. Try it free.http://ads.osdn.com/?ad_idt02&alloc_id135&op=click
>_______________________________________________
>Bodington-developers mailing list
>Bod...@li...
>https://lists.sourceforge.net/lists/listinfo/bodington-developers
>  
>

Re: [Bodington-developers] Commit privileges to HEAD

[Alexis O'C. <ale...@co...>]

Adam Marshall wrote:
> Colin would be able to do that - but he's got the afternoon off. 
> 
> Do we need to vote on whether Peter is allowed in? I think it's pretty clear
> that non of us would have an issue with this.
> 
> adam
> 
> --

Nope, not me. In fact when I was looking at the access rights a while 
ago I thought it was a bit of an anomaly that he didn't have these 
rights already!


Alexis

Re: [Bodington-developers] Commit privileges to HEAD

[Alistair Y. <ali...@sm...>]

come and join the fun Peter!

Alistair

On 26 May 2005, at 13:37, Adam Marshall wrote:

> Colin would be able to do that - but he's got the afternoon off.
>
> Do we need to vote on whether Peter is allowed in? I think it's pretty=20=

> clear
> that non of us would have an issue with this.
>
> adam
>
> --
> Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
> Shameless plug:      Use the Bodington VLE http://bodington.org
> Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
> Cheese of the month: Cheshire (not to be underestimated)
>
> | -----Original Message-----
> | From: bod...@li...=20
> [mailto:bodington-
> | dev...@li...] On Behalf Of Peter Crowther
> | Sent: 26 May 2005 13:10
> | To: bod...@li...
> | Subject: [Bodington-developers] Commit privileges to HEAD
> |
> | I've got a couple of changes to the IMS content packaging work that=20=

> I'd
> | like to check in before continuing.  I don't have commit access to=20=

> HEAD
> | on sf.net.  Assuming we are willing for me to make a pig's ear of =
the
> | system, could some kind admin type check out CVSROOT/avail, add=20
> 'ozzard'
> | to the list of users on line 4 (the bodington branch) and commit the
> | change?  If not, who's willing to undertake to check in my changes?
> |
> | 		- Peter
> |
> | --
> | Peter Crowther, Director, Melandra Limited
> | John Dalton House, 121 Deansgate, Manchester M3 2AB
> | t: +44 (0)161 828 8736  f: +44 (0)161 832 5683
> |
> |
> | -------------------------------------------------------
> | SF.Net email is sponsored by: GoToMeeting - the easiest way to=20
> collaborate
> | online with coworkers and clients while avoiding the high cost of=20
> travel
> | and
> | communications. There is no equipment to buy and you can meet as=20
> often as
> | you want. Try it=20
> free.http://ads.osdn.com/?ad_idt02&alloc_id=16135&op=3Dick
> | _______________________________________________
> | Bodington-developers mailing list
> | Bod...@li...
> | https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: GoToMeeting - the easiest way to=20
> collaborate
> online with coworkers and clients while avoiding the high cost of=20
> travel and
> communications. There is no equipment to buy and you can meet as often=20=

> as
> you want. Try it=20
> free.http://ads.osdn.com/?ad_idt02&alloc_id=16135&op=3Dclick
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers

RE: [Bodington-developers] Commit privileges to HEAD

[Adam M. <ada...@co...>]

Colin would be able to do that - but he's got the afternoon off.=20

Do we need to vote on whether Peter is allowed in? I think it's pretty =
clear
that non of us would have an issue with this.

adam

--
Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
Shameless plug:      Use the Bodington VLE http://bodington.org
Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
Cheese of the month: Cheshire (not to be underestimated)=20

| -----Original Message-----
| From: bod...@li... =
[mailto:bodington-
| dev...@li...] On Behalf Of Peter Crowther
| Sent: 26 May 2005 13:10
| To: bod...@li...
| Subject: [Bodington-developers] Commit privileges to HEAD
|=20
| I've got a couple of changes to the IMS content packaging work that =
I'd
| like to check in before continuing.  I don't have commit access to =
HEAD
| on sf.net.  Assuming we are willing for me to make a pig's ear of the
| system, could some kind admin type check out CVSROOT/avail, add =
'ozzard'
| to the list of users on line 4 (the bodington branch) and commit the
| change?  If not, who's willing to undertake to check in my changes?
|=20
| 		- Peter
|=20
| --
| Peter Crowther, Director, Melandra Limited
| John Dalton House, 121 Deansgate, Manchester M3 2AB
| t: +44 (0)161 828 8736  f: +44 (0)161 832 5683
|=20
|=20
| -------------------------------------------------------
| SF.Net email is sponsored by: GoToMeeting - the easiest way to =
collaborate
| online with coworkers and clients while avoiding the high cost of =
travel
| and
| communications. There is no equipment to buy and you can meet as often =
as
| you want. Try it =
free.http://ads.osdn.com/?ad_idt02&alloc_id=16135&op=3Dick
| _______________________________________________
| Bodington-developers mailing list
| Bod...@li...
| https://lists.sourceforge.net/lists/listinfo/bodington-developers

[Bodington-developers] Commit privileges to HEAD

[Peter C. <Pet...@me...>]

I've got a couple of changes to the IMS content packaging work that I'd
like to check in before continuing.  I don't have commit access to HEAD
on sf.net.  Assuming we are willing for me to make a pig's ear of the
system, could some kind admin type check out CVSROOT/avail, add 'ozzard'
to the list of users on line 4 (the bodington branch) and commit the
change?  If not, who's willing to undertake to check in my changes?

		- Peter

--
Peter Crowther, Director, Melandra Limited
John Dalton House, 121 Deansgate, Manchester M3 2AB
t: +44 (0)161 828 8736  f: +44 (0)161 832 5683

Re: [Bodington-developers] build.xml

[Alexis O'C. <ale...@co...>]

Alistair Young wrote:
> I agree entirely Mathew. You inspired me to rake about in bod and I've
> switched to using the request. The template's process() method gets passed
> a Request object so BuildingServlet, which handles the debug switching
> form now sets the attribute instead of putting it in bodington.properties.
> Don't know why I didn't see that earlier.
> 
> Windows problems should now all be solved as no path info is used any more.
> 
> Anyway, it works a treat without touching bodington.properties
> 
> I also changed the template's resource-file attribute to resources as it
> now supports multiple resources.
> 
> Hopefully that should be it now:
> 
> http://www.weblogs.uhi.ac.uk/sm00ay/?p=91
> 
> Alistair
> 
> 

Credit where credit's due: it does appear to work now.

(... once I built it with the changes that were committed at 09.22 today 
rather than when I first got in this morning ;-) ).


Alexis

[Bodington-developers] Template localisation HOWTO

[Alistair Y. <ali...@sm...>]

http://www.weblogs.uhi.ac.uk/sm00ay/?p=90

Re: [Bodington-developers] build.xml

[Alistair Y. <ali...@sm...>]

I agree entirely Mathew. You inspired me to rake about in bod and I've
switched to using the request. The template's process() method gets passe=
d
a Request object so BuildingServlet, which handles the debug switching
form now sets the attribute instead of putting it in bodington.properties=
.
Don't know why I didn't see that earlier.

Windows problems should now all be solved as no path info is used any mor=
e.

Anyway, it works a treat without touching bodington.properties

I also changed the template's resource-file attribute to resources as it
now supports multiple resources.

Hopefully that should be it now:

http://www.weblogs.uhi.ac.uk/sm00ay/?p=3D91

Alistair


--=20
Alistair Young
Senior Software Engineer
UHI@Sabhal M=F2r Ostaig
Isle of Skye
Scotland

> Alistair Young wrote:
>>> is there a reason why this property can't be read at startup only?
>>
>> it changes based on what you choose in useroptions. If you're having
>> trouble seeing some strings in templates, you go to useroptions and se=
t
>> up the localisation debug level and it tells you things like the bundl=
e
>> and classpath it was looking in.
>
> So is it a system wide property? If so who can change it? Just the
> sysadmin? Does it need to persist between restarts of the context if it
> is mainly used for debugging? If not could it be a context attribute?
> How many questionmarks can I put in one paragraph?
>
>> maybe bodington.properties is the wrong place to store it - but I
>> couldn't find anywhere else.
>
> I'd probably say it is the wrong place but Bodington doesn't exactly
> give many other options.
>
> --
> +--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: GoToMeeting - the easiest way to collabor=
ate
> online with coworkers and clients while avoiding the high cost of trave=
l
> and
> communications. There is no equipment to buy and you can meet as often =
as
> you want. Try it
> free.http://ads.osdn.com/?ad_id=3D7402&alloc_id=3D16135&op=3Dclick
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>

Re: [Bodington-developers] build.xml

[M. B. <mat...@co...>]

Alistair Young wrote:
>> is there a reason why this property can't be read at startup only?
> 
> it changes based on what you choose in useroptions. If you're having 
> trouble seeing some strings in templates, you go to useroptions and set 
> up the localisation debug level and it tells you things like the bundle 
> and classpath it was looking in.

So is it a system wide property? If so who can change it? Just the 
sysadmin? Does it need to persist between restarts of the context if it 
is mainly used for debugging? If not could it be a context attribute? 
How many questionmarks can I put in one paragraph?

> maybe bodington.properties is the wrong place to store it - but I 
> couldn't find anywhere else.

I'd probably say it is the wrong place but Bodington doesn't exactly 
give many other options.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

[Bodington-developers] bodington downloads

[Adam M. <ada...@co...>]

http://sourceforge.net/project/stats/index.php?group_id=87659&ugn=bodington&
type=&mode=60day

there's definite spikes in the # downloads on the day of the THES advert and
on 9/10/11 may. what happened during the w/ending 6 may?

adam

--
Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
Shameless plug:      Use the Bodington VLE http://bodington.org
Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
Cheese of the month: Cheshire (not to be underestimated) 

RE: [Bodington-developers] XML Repository and namespace prefixes

[Peter C. <Pet...@me...>]

> From: [...] Colin Tatham
> I like option 3, and storing the namespace prefix, presumably=20
> separate from the rest of the element name...

Noted.  I'm coming round to it if we can do it.

> Isn't the SAX parsing a problem for option 2 too?

Re-reading the relevant bit of spec... SAX2 guarantees that all
implementations will provide the namespace URI, the qName and the
undecorated element name, but doesn't guarantee to pass through the
xmlns:* attributes (from
http://java.sun.com/j2se/1.4.2/docs/api/org/xml/sax/ContentHandler.html)
.  LexicalHandler is also optional.  This means that there might be no
central way of retrieving qname to namespace mappings - although I now
think it's possible to pick the mappings up piecemeal in the elements
and attributes, so this may not in fact be an issue.

> If I'm understanding what you're saying, parsing (on import?)=20
> might not provide the namespace, so it won't get the URI=20
> either will it?
>=20
> In the example you quoted, is the element name being stored=20
> as imsmd:record?

Yes.

> That suggests a problem in parsing i.e. it=20
> doesn't understand what a prefix is (unless it's a quirky=20
> Bodington way to store the prefixes).

XMLRepository is currently coded to store the QName, not the localName.
So anything with namespace prefixes will be stored with those prefixes.
This is why I want to change it.

		- Peter

Re: [Bodington-developers] build.xml

[Alistair Y. <ali...@sm...>]

I've humbly put a new XmlTemplate on head that should fix the windows 
problem

Alistair

On 25 May 2005, at 16:49, Alexis O'Connor wrote:

> Alistair Young wrote:
>> cmon, give me some credit - I don't hard code!
>> bodingtonProperties is set via  
>> breq.getRealPath("/WEB-INF/bodington.properties")
>> on windows it comes out with backslashes as it should, however, this 
>> is  no normal system, this is bodington and the result has to be 
>> written as  code into a java file:
>> writer.println("bodingtonProperties = \"" + bodingtonProperties +  
>> "\";");
>> I could just do bodingtonProperties.replaceAll("\\", "\\\\");
>> the only reason I need bodingtonProperties is to get the language 
>> debug  level as BuildingContext is incapable of updating 
>> bodington.properties  - it reads it once then forgets it's there, so 
>> using  BuildingContext.getProperty() doesn't work in a dynamic 
>> environment -  unless I've missed something?
>> the alternative is to store the debug level as a user setting but  
>> that's overkill. A debug level was specifically requested and  
>> bodington.properties was the cleanest way to do it.
>
> I think I understand better now. Don't worry, I think Windoze is a 
> pile of w*nk too, but I believe they have quite a big share of the 
> desktop market, so I think we're kinda obliged to support it ;-).
>
>> I hope you meant the hardback edition of the beano annual?
>
> Is there any other!? ;-).
>
>> Would you like to do the build file update for res.jar seeing you  
>> designed the process and are more familiar with it?
>
> No worries on this score. I was working on a fix as your reply popped 
> into my inbox. Should be committed back very soon!
>
>
> Alexis
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: GoToMeeting - the easiest way to 
> collaborate
> online with coworkers and clients while avoiding the high cost of 
> travel and
> communications. There is no equipment to buy and you can meet as often 
> as
> you want. Try it 
> free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers

[Bodington-developers] wikis

[Adam M. <ada...@co...>]

The topic of wiki's has arisen here at Oxf'd.

 http://radio.weblogs.com/0120501/2004/06/10.html#a709  also
http://en.wikipedia.org/wiki/Comparison_of_wiki_software  ?

Wiki's are coming to the fore here at Oxford. We need one for ASK project
and of course we need one for bod developers. 

We need these faster that we will be able to stick one in bod (& shibb) - so
there's 3 possibilities:

1/ use the same wiki as we intend to put into Bod
2/ use another wiki from which we can export content into the eventual wiki
3/ use any old wiki with no intention of housing data under bod ever.

Colin is looking into a wiki for bod devs, aggie was looking at one for
shibbing in Bod. Howard needs one for ASK.

adam


--
Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
Shameless plug:      Use the Bodington VLE http://bodington.org
Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
Cheese of the month: Cheshire (not to be underestimated) 

Re: [Bodington-developers] build.xml

[Alistair Y. <ali...@sm...>]

> is there a reason why this property can't be read at startup only?
it changes based on what you choose in useroptions. If you're having 
trouble seeing some strings in templates, you go to useroptions and set 
up the localisation debug level and it tells you things like the bundle 
and classpath it was looking in.

maybe bodington.properties is the wrong place to store it - but I 
couldn't find anywhere else.

Alistair


On 25 May 2005, at 16:51, Matthew Buckett wrote:

> Alistair Young wrote:
> >
>> the only reason I need bodingtonProperties is to get the language 
>> debug  level as BuildingContext is incapable of updating 
>> bodington.properties  - it reads it once then forgets it's there, so 
>> using  BuildingContext.getProperty() doesn't work in a dynamic 
>> environment -  unless I've missed something?
>
> Having some properties that can be updated while bodington is running 
> and others that require a restart causes confusion and seems messy. Is 
> there a reason why this property can't be read at startup only?
>
> I'd really like Bodington to be re-configurable without requiring a 
> restart but I think this would come with a move to a more sensible 
> configuration setup (commons-configuration) and maybe property 
> listeners.
>
> -- 
> +--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: GoToMeeting - the easiest way to 
> collaborate
> online with coworkers and clients while avoiding the high cost of 
> travel and
> communications. There is no equipment to buy and you can meet as often 
> as
> you want. Try it 
> free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers

Re: [Bodington-developers] build.xml

[Matthew B. <mat...@co...>]

Alistair Young wrote:
 >
> the only reason I need bodingtonProperties is to get the language debug  
> level as BuildingContext is incapable of updating bodington.properties  
> - it reads it once then forgets it's there, so using  
> BuildingContext.getProperty() doesn't work in a dynamic environment -  
> unless I've missed something?

Having some properties that can be updated while bodington is running 
and others that require a restart causes confusion and seems messy. Is 
there a reason why this property can't be read at startup only?

I'd really like Bodington to be re-configurable without requiring a 
restart but I think this would come with a move to a more sensible 
configuration setup (commons-configuration) and maybe property listeners.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

RE: [Bodington-developers] XML Repository and namespace prefixes

[Colin T. <col...@co...>]

I like option 3, and storing the namespace prefix, presumably separate from
the rest of the element name...
Isn't the SAX parsing a problem for option 2 too?
If I'm understanding what you're saying, parsing (on import?) might not
provide the namespace, so it won't get the URI either will it?

In the example you quoted, is the element name being stored as imsmd:record?
That suggests a problem in parsing i.e. it doesn't understand what a prefix
is (unless it's a quirky Bodington way to store the prefixes).


Colin

> -----Original Message-----
> From: bod...@li...
> [mailto:bod...@li...]On Behalf Of
> Peter Crowther
> Sent: 25 May 2005 15:54
> To: bod...@li...
> Subject: RE: [Bodington-developers] XML Repository and namespace
> prefixes
> 
> 
> > From: Adam Marshall 
> > | From: [...] Peter Crowther
> [...]
> > | The next simplest is to store the namespace URI with each row in
> > | xml_elements and xml_attributes.  Cheap'n'cheerful, full-fidelity
> > | reconstruction, works with any SAX2 parser, but expensive 
> > on disk space.
> > 
> > Thumb goes up. Surely a namespaces table:
> > 
> >         String | integer
> > 
> > With the addition of a single int column the each xml element 
> > and attr row wouldn't be too bad??
> 
> That's nearer to option 3 - storing the mapping - rather than 
> option 2,
> although it could be done.
> 
> > Is this necessary - do we need to actually store the 
> > namespace prefix in Bod?
> 
> No, although it's worth storing what was the base namespace.
> 
> > Couldnt we just make up something from the URI? Ugly but works
> > perfectly? After all who's going to be hand editing our 
> exported XML?
> 
> Based on past experience... more people than you would 
> expect.  Far more
> people appear to edit XML by hand than edit HTML by hand, and 
> you still
> see plenty of 'created using Notepad' riders on Web sites.
> 
> > Surely when we move to VFS in X years time this will be 
> taken care of?
> 
> There's been some determined opposition to going that way - 
> some of that
> opposition has been visible on this mailing list and its predecessor.
> The system incorporating the VFS no longer even carries the Bodington
> family name due to this opposition.  X may be small, large or 
> infinite;
> I have no knowledge about its value, and hence cannot plan 
> assuming any
> particular value.  Do you have knowledge I'm missing?
> 
> 		- Peter
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: GoToMeeting - the easiest way 
> to collaborate
> online with coworkers and clients while avoiding the high 
> cost of travel and
> communications. There is no equipment to buy and you can meet 
> as often as
> you want. Try it 
> free.http://ads.osdn.com/?ad_idt02&alloc_id135&op=ick
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
> 

Re: [Bodington-developers] build.xml

[Alexis O'C. <ale...@co...>]

Alistair Young wrote:
> cmon, give me some credit - I don't hard code!
> 
> bodingtonProperties is set via  
> breq.getRealPath("/WEB-INF/bodington.properties")
> 
> on windows it comes out with backslashes as it should, however, this is  
> no normal system, this is bodington and the result has to be written as  
> code into a java file:
> 
> writer.println("bodingtonProperties = \"" + bodingtonProperties +  "\";");
> 
> I could just do bodingtonProperties.replaceAll("\\", "\\\\");
> 
> the only reason I need bodingtonProperties is to get the language debug  
> level as BuildingContext is incapable of updating bodington.properties  
> - it reads it once then forgets it's there, so using  
> BuildingContext.getProperty() doesn't work in a dynamic environment -  
> unless I've missed something?
> 
> the alternative is to store the debug level as a user setting but  
> that's overkill. A debug level was specifically requested and  
> bodington.properties was the cleanest way to do it.

I think I understand better now. Don't worry, I think Windoze is a pile 
of w*nk too, but I believe they have quite a big share of the desktop 
market, so I think we're kinda obliged to support it ;-).

> 
> I hope you meant the hardback edition of the beano annual?
> 

Is there any other!? ;-).

> Would you like to do the build file update for res.jar seeing you  
> designed the process and are more familiar with it?
> 

No worries on this score. I was working on a fix as your reply popped 
into my inbox. Should be committed back very soon!


Alexis

Re: [Bodington-developers] build.xml

[Alistair Y. <ali...@sm...>]

cmon, give me some credit - I don't hard code!

bodingtonProperties is set via  
breq.getRealPath("/WEB-INF/bodington.properties")

on windows it comes out with backslashes as it should, however, this is  
no normal system, this is bodington and the result has to be written as  
code into a java file:

writer.println("bodingtonProperties = \"" + bodingtonProperties +  
"\";");

I could just do bodingtonProperties.replaceAll("\\", "\\\\");

the only reason I need bodingtonProperties is to get the language debug  
level as BuildingContext is incapable of updating bodington.properties  
- it reads it once then forgets it's there, so using  
BuildingContext.getProperty() doesn't work in a dynamic environment -  
unless I've missed something?

the alternative is to store the debug level as a user setting but  
that's overkill. A debug level was specifically requested and  
bodington.properties was the cleanest way to do it.

I hope you meant the hardback edition of the beano annual?

Would you like to do the build file update for res.jar seeing you  
designed the process and are more familiar with it?

Alistair

On 25 May 2005, at 16:23, Alexis O'Connor wrote:

> Alistair Young wrote:
>> I have humbly committed an updated build.xml to jar up the res dir  
>> and bung it in WEB-INF/lib/res.jar
>> bod is now i18n
>> Alistair
>
> OK, time for Alistair to stuff a copy of the Beano annual down the  
> back of his shorts again ;-).
>
> Getting there with the build.xml. However, it would be good if the  
> res.jar followed the pattern of bodserver.jar. This would mean that  
> the resources lie in unpacked form under WEB-INF/classes (for the  
> 'deploy-local' target to take advantage of) and only get bundled into  
> a jar by 'create-war'.
>
> More importantly though, it still doesn't work on Windows :-(. (Stack  
> trace attached). An 'escaping backslash in strings' problem. Why are  
> you hardcoding the location of bodington.properties? Can you not get  
> hold of the properties via BuildingServer?
>
>
> Alexis
> Compilation messages...
> -classpath  
> /C:/j2sdk1.4.2_08/jre/lib/ext/dnsns.jar;/C:/j2sdk1.4.2_08/jre/lib/ext/ 
> ldapsec.jar;/C:/j2sdk1.4.2_08/jre/lib/ext/localedata.jar;/C:/ 
> j2sdk1.4.2_08/jre/lib/ext/pg74.215.jdbc3.jar;/C:/j2sdk1.4.2_08/jre/ 
> lib/ext/sunjce_provider.jar;/C:/j2sdk1.4.2_08/lib/tools.jar;/C:/ 
> Program%20Files/Apache%20Software%20Foundation/Tomcat%205.0/bin/ 
> bootstrap.jar;C:/Program Files/Apache Software Foundation/Tomcat  
> 5.0/common/classes/;C:/Program Files/Apache Software Foundation/Tomcat  
> 5.0/common/endorsed/xercesImpl.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/endorsed/xml-apis.jar;C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/common/lib/ant-launcher.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/lib/ant.jar;C:/Program Files/Apache  
> Software Foundation/Tomcat  
> 5.0/common/lib/commons-collections-3.1.jar;C:/Program Files/Apache  
> Software Foundation/Tomcat  
> 5.0/common/lib/commons-dbcp-1.2.1.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/lib/commons-el.jar;C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/common/lib/commons-pool-1.2.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/lib/jasper-compiler.jar;C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/common/lib/jasper-runtime.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/lib/jsp-api.jar;C:/Program Files/Apache  
> Software Foundation/Tomcat 5.0/common/lib/naming-common.jar;C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/common/lib/naming-factory.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/lib/naming-java.jar;C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/common/lib/naming-resources.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/common/lib/servlet-api.jar;C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/common/lib/tools.jar;C:/Program Files/Apache Software  
> Foundation/Tomcat 5.0/shared/classes/;/C:/Program Files/Apache  
> Software Foundation/Tomcat  
> 5.0/webapps/bodington/WEB-INF/lib/activation.jar;/C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/webapps/bodington/WEB-INF/lib/bodserver.jar;/C:/Program  
> Files/Apache Software Foundation/Tomcat  
> 5.0/webapps/bodington/WEB-INF/lib/ldap.jar;/C:/Program Files/Apache  
> Software Foundation/Tomcat  
> 5.0/webapps/bodington/WEB-INF/lib/log4j.jar;/C:/Program Files/Apache  
> Software Foundation/Tomcat  
> 5.0/webapps/bodington/WEB-INF/lib/mail.jar;/C:/Program Files/Apache  
> Software Foundation/Tomcat 5.0/webapps/bodington/WEB-INF/lib/res.jar;
> C:\Program Files\Apache Software Foundation\Tomcat  
> 5.0\webapps\bodington\WEB- 
> INF\template_classes\working\style_default_default\template_useroptions 
> _en.java:19: illegal escape character
> bodingtonProperties = "C:\Program Files\Apache Software  
> Foundation\Tomcat 5.0\webapps\bodington\WEB-INF\bodington.properties";
>                           ^
> C:\Program Files\Apache Software Foundation\Tomcat  
> 5.0\webapps\bodington\WEB- 
> INF\template_classes\working\style_default_default\template_useroptions 
> _en.java:19: illegal escape character
> bodingtonProperties = "C:\Program Files\Apache Software  
> Foundation\Tomcat 5.0\webapps\bodington\WEB-INF\bodington.properties";
>                                         ^
> C:\Program Files\Apache Software Foundation\Tomcat  
> 5.0\webapps\bodington\WEB- 
> INF\template_classes\working\style_default_default\template_useroptions 
> _en.java:19: illegal escape character
> bodingtonProperties = "C:\Program Files\Apache Software  
> Foundation\Tomcat 5.0\webapps\bodington\WEB-INF\bodington.properties";
>                                                                    ^
> C:\Program Files\Apache Software Foundation\Tomcat  
> 5.0\webapps\bodington\WEB- 
> INF\template_classes\working\style_default_default\template_useroptions 
> _en.java:19: illegal escape character
> bodingtonProperties = "C:\Program Files\Apache Software  
> Foundation\Tomcat 5.0\webapps\bodington\WEB-INF\bodington.properties";
>                                                                         
>        ^
> C:\Program Files\Apache Software Foundation\Tomcat  
> 5.0\webapps\bodington\WEB- 
> INF\template_classes\working\style_default_default\template_useroptions 
> _en.java:19: illegal escape character
> bodingtonProperties = "C:\Program Files\Apache Software  
> Foundation\Tomcat 5.0\webapps\bodington\WEB-INF\bodington.properties";
>                                                                         
>                          ^
> 5 errors
>
> Compilation exit code = 1

Re: [Bodington-developers] build.xml

[Alexis O'C. <ale...@co...>]

Alistair Young wrote:
> I have humbly committed an updated build.xml to jar up the res dir and 
> bung it in WEB-INF/lib/res.jar
> 
> bod is now i18n
> 
> Alistair
> 

OK, time for Alistair to stuff a copy of the Beano annual down the back 
of his shorts again ;-).

Getting there with the build.xml. However, it would be good if the 
res.jar followed the pattern of bodserver.jar. This would mean that the 
resources lie in unpacked form under WEB-INF/classes (for the 
'deploy-local' target to take advantage of) and only get bundled into a 
jar by 'create-war'.

More importantly though, it still doesn't work on Windows :-(. (Stack 
trace attached). An 'escaping backslash in strings' problem. Why are you 
hardcoding the location of bodington.properties? Can you not get hold of 
the properties via BuildingServer?


Alexis

RE: [Bodington-developers] XML Repository and namespace prefixes

[Peter C. <Pet...@me...>]

> From: Adam Marshall=20
> | From: [...] Peter Crowther
[...]
> | The next simplest is to store the namespace URI with each row in
> | xml_elements and xml_attributes.  Cheap'n'cheerful, full-fidelity
> | reconstruction, works with any SAX2 parser, but expensive=20
> on disk space.
>=20
> Thumb goes up. Surely a namespaces table:
>=20
>         String | integer
>=20
> With the addition of a single int column the each xml element=20
> and attr row wouldn't be too bad??

That's nearer to option 3 - storing the mapping - rather than option 2,
although it could be done.

> Is this necessary - do we need to actually store the=20
> namespace prefix in Bod?

No, although it's worth storing what was the base namespace.

> Couldnt we just make up something from the URI? Ugly but works
> perfectly? After all who's going to be hand editing our exported XML?

Based on past experience... more people than you would expect.  Far more
people appear to edit XML by hand than edit HTML by hand, and you still
see plenty of 'created using Notepad' riders on Web sites.

> Surely when we move to VFS in X years time this will be taken care of?

There's been some determined opposition to going that way - some of that
opposition has been visible on this mailing list and its predecessor.
The system incorporating the VFS no longer even carries the Bodington
family name due to this opposition.  X may be small, large or infinite;
I have no knowledge about its value, and hence cannot plan assuming any
particular value.  Do you have knowledge I'm missing?

		- Peter

Re: [Bodington-developers] XML Repository and namespace prefixes

[Matthew B. <mat...@co...>]

Alistair Young wrote:
>> The next simplest is to store the namespace URI with each row in
>> xml_elements and xml_attributes
> 
> sounds the easiest, simplest and most reliable - do we care about disk 
> space? how many nanopence is it now per Gb?

To me this sounds like the best short term solution. As long as we don't 
throw away information we can always migrate to a better solution.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

RE: [Bodington-developers] Performance profiling of Bodington

[Adam M. <ada...@co...>]

I suspect that we do not have any evidence whatsoever.=20

Also - I'd wager tomorrow's lunch (a rather nice ham sandwich) that
moodle.org has more users per day than weblearn.

adam
--
Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
Shameless plug:      Use the Bodington VLE http://bodington.org
Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
Cheese of the month: Cheshire (not to be underestimated)=20

| -----Original Message-----
| From: bod...@li... =
[mailto:bodington-
| dev...@li...] On Behalf Of Peter Crowther
| Sent: 25 May 2005 15:40
| To: bod...@li...
| Subject: [Bodington-developers] Performance profiling of Bodington
|=20
| A complete aside.  We have some anecdotal evidence that Bodington
| running under at least some Tomcat versions is "slow".  Do we have any
| more information than that as to what versions of what containers, =
what
| "slow" means, and whether anyone has done any profiling or other
| investigation ito the overall performance of a running Bodington =
system?
|=20
| We're claiming that Bodington is more appropriate than Moodle for =
large
| institutions as Moodle doesn't scale to them and Bodington does.  Do =
we
| have even a shred of evidence to support that comparison?
|=20
| 		- Peter
|=20
|=20
| -------------------------------------------------------
| SF.Net email is sponsored by: GoToMeeting - the easiest way to =
collaborate
| online with coworkers and clients while avoiding the high cost of =
travel
| and
| communications. There is no equipment to buy and you can meet as often =
as
| you want. Try it =
free.http://ads.osdn.com/?ad_idt02&alloc_id=16135&op=3Dick
| _______________________________________________
| Bodington-developers mailing list
| Bod...@li...
| https://lists.sourceforge.net/lists/listinfo/bodington-developers

RE: [Bodington-developers] XML Repository and namespace prefixes

[Adam M. <ada...@co...>]

--
Adam Marshall:       OUCS, 13, Banbury Rd. Oxford OX2 6NN.
Shameless plug:      Use the Bodington VLE http://bodington.org
Blog:                http://ramble.oucs.ox.ac.uk/blog/adamm/
Cheese of the month: Cheshire (not to be underestimated)=20

| -----Original Message-----
| From: bod...@li... =
[mailto:bodington-
| dev...@li...] On Behalf Of Peter Crowther
| Sent: 25 May 2005 15:24
| To: bod...@li...
| Subject: [Bodington-developers] XML Repository and namespace prefixes
|=20
| At present, the XML repository has no notion of namespace URIs or
| namespace prefixes.  This give rise to some rather entertaining =
problems
| with more recent IMS content packages (basically anything 1.1 and
| above).  For example, the <record> element of Aggie's 1.1.2 content
| package is stored as <imsmd:record> - which means that a content =
package
| import fails as the code can't find <record> under the <metadata> tag.
|=20

Thumb goes down.

| There are a number of ways around this.  I'm looking for input on =
which
| of these might be appropriate for other developments.
|=20
| The simplest is to strip the namespace information during import, as
| nature appears to have intended things.  This works fine... until the
| time comes to reconstruct the XML for output, at which point the
| information loss may well be sufficient that it is not possible to
| reconstruct anything useful.
|=20
| The next simplest is to store the namespace URI with each row in
| xml_elements and xml_attributes.  Cheap'n'cheerful, full-fidelity
| reconstruction, works with any SAX2 parser, but expensive on disk =
space.

Thumb goes up. Surely a namespaces table:

        String | integer

With the addition of a single int column the each xml element and attr =
row
wouldn't be too bad??

|=20
| Next harder is trying to store a mapping of namespace prefixes to
| namespace URIs, and store the prefixes with each element and =
attribute.
| It's harder because there's always the possibility of getting =
something
| without namespace prefixes, at which point they need to be =
manufactured.
| It's also not guaranteed to work with all SAX2 parsers, as returning =
the
| namespace prefix is an optional facility.  However, it reduces the =
disk
| space considerably.
|=20

Is this necessary - do we need to actually store the namespace prefix in
Bod? Couldnt we just make up something from the URI? Ugly but works
perfectly? After all who's going to be hand editing our exported XML?

| Hardest is ripping out the existing XML repository and replacing it =
with
| an off-the-shelf XML database - I'd probably use eXist, as I have some
| experience with it and it would work for this job.  This adds the
| complexity of another component and another data store (eXist uses its
| own .dbx files), but removes one more bespoke piece from Bodington.  =
I'm
| not going to be able to do this within the timeframe of the existing
| project unless someone comes up with some more dosh!

Surely when we move to VFS in X years time this will be taken care of?

|=20
| Does anyone have any preferences, before I shrug and go for the =
easiest
| approach that serves my needs for now?
|=20
| 		- Peter
|=20
|=20
| -------------------------------------------------------
| SF.Net email is sponsored by: GoToMeeting - the easiest way to =
collaborate
| online with coworkers and clients while avoiding the high cost of =
travel
| and
| communications. There is no equipment to buy and you can meet as often =
as
| you want. Try it =
free.http://ads.osdn.com/?ad_idt02&alloc_id=16135&op=3Dick
| _______________________________________________
| Bodington-developers mailing list
| Bod...@li...
| https://lists.sourceforge.net/lists/listinfo/bodington-developers

[Bodington-developers] Performance profiling of Bodington

[Peter C. <Pet...@me...>]

A complete aside.  We have some anecdotal evidence that Bodington
running under at least some Tomcat versions is "slow".  Do we have any
more information than that as to what versions of what containers, what
"slow" means, and whether anyone has done any profiling or other
investigation ito the overall performance of a running Bodington system?

We're claiming that Bodington is more appropriate than Moodle for large
institutions as Moodle doesn't scale to them and Bodington does.  Do we
have even a shred of evidence to support that comparison?

		- Peter

Re: [Bodington-developers] XML Repository and namespace prefixes

[Alistair Y. <ali...@sm...>]

> The simplest is to strip the namespace information during import, as
> nature appears to have intended things...
> ...not possible to
> reconstruct anything useful.
well that option's out then

> The next simplest is to store the namespace URI with each row in
> xml_elements and xml_attributes
sounds the easiest, simplest and most reliable - do we care about disk=20=

space? how many nanopence is it now per Gb?

> Next harder is trying to store a mapping of namespace prefixes to
> namespace URIs...
> ...not guaranteed to work with all SAX2 parsers
well that option's out then too!

> Hardest is ripping out the existing XML repository and replacing it=20
> with
> an off-the-shelf XML database - I'd probably use eXist,
eXist has been talked about here too, in connection with other=20
projects. Perhaps this is the way for tetra? I question whether large=20
sums of cash are worth pouring into bod if tetra is on the way.

from the above list, I'd vote for number 2.

Alistair


On 25 May 2005, at 15:24, Peter Crowther wrote:

> At present, the XML repository has no notion of namespace URIs or
> namespace prefixes.  This give rise to some rather entertaining=20
> problems
> with more recent IMS content packages (basically anything 1.1 and
> above).  For example, the <record> element of Aggie's 1.1.2 content
> package is stored as <imsmd:record> - which means that a content=20
> package
> import fails as the code can't find <record> under the <metadata> tag.
>
> There are a number of ways around this.  I'm looking for input on =
which
> of these might be appropriate for other developments.
>
> The simplest is to strip the namespace information during import, as
> nature appears to have intended things.  This works fine... until the
> time comes to reconstruct the XML for output, at which point the
> information loss may well be sufficient that it is not possible to
> reconstruct anything useful.
>
> The next simplest is to store the namespace URI with each row in
> xml_elements and xml_attributes.  Cheap'n'cheerful, full-fidelity
> reconstruction, works with any SAX2 parser, but expensive on disk=20
> space.
>
> Next harder is trying to store a mapping of namespace prefixes to
> namespace URIs, and store the prefixes with each element and =
attribute.
> It's harder because there's always the possibility of getting =
something
> without namespace prefixes, at which point they need to be=20
> manufactured.
> It's also not guaranteed to work with all SAX2 parsers, as returning=20=

> the
> namespace prefix is an optional facility.  However, it reduces the =
disk
> space considerably.
>
> Hardest is ripping out the existing XML repository and replacing it=20
> with
> an off-the-shelf XML database - I'd probably use eXist, as I have some
> experience with it and it would work for this job.  This adds the
> complexity of another component and another data store (eXist uses its
> own .dbx files), but removes one more bespoke piece from Bodington. =20=

> I'm
> not going to be able to do this within the timeframe of the existing
> project unless someone comes up with some more dosh!
>
> Does anyone have any preferences, before I shrug and go for the =
easiest
> approach that serves my needs for now?
>
> 		- Peter
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: GoToMeeting - the easiest way to=20
> collaborate
> online with coworkers and clients while avoiding the high cost of=20
> travel and
> communications. There is no equipment to buy and you can meet as often=20=

> as
> you want. Try it=20
> free.http://ads.osdn.com/?ad_idt02&alloc_id=16135&op=3Dclick
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers