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: Paul T. <pau...@co...> - 2005-07-13 16:55:29
|
Hi, Just a snippet from thread on JISCMAIL to highlight PLEs and PDAs: >Date: Wed, 13 Jul 2005 17:13:36 +0100 >From: Tom Franklin <to...@FR...> >Subject: Re: [VLES] VLE - A case for Moodle >To: VL...@JI... < ... > >Oh, and one more thing, the DfES is currently getting very excited about >personal learning environments - I don't think that it has quite decided >what this means yet, but if it means the student having their own "VLE" that >they take with them then how will this relate to your VLE and the way you >are implementing it? PLEs seem to connote many different things, e.g. from VLEs running offline on your laptop (as in the Manchester PLE) to whatever is supporting your learning on the move. I guess most people would consider being able to run Bodington on a PDA as a PLE scenario. Colin was trying out Bodington on his iPaq just the other day and found that since the revised work on stylesheets, navigating Bodington has become much easier, though stylesheets can take a while to process. Some while ago I found I could do most of what I needed with a clamshell device (HP Jornada 720) and Aggie carried out some tests on his iPaq, with some success. So I think it would be useful to have this done more systematically and if Bodington proves quite workable, it may be worth marketing. Perhaps a nice project for a student? Incidentally, Andy Ramsden in Bristol has run some tests on Blackboard and Moodle, see e.g. http://www.mobile-learning.blog-city.com/accessing_moodle_via_a_wirlessly_connected_palm_os.htm Regards, Paul P.S. The thread was actually in response to Stuart's "free lunch" article. |
From: Paul T. <pau...@co...> - 2005-07-13 16:54:52
|
At 11:09 13/07/2005, Peter Crowther wrote: > > From: Paul Trafford > > Anyway, we certainly need to work on documentation and < .. > >Getting user documentation together would be a big start. Jon Maber has >some on bodington.org, but the formatting isn't ideal and much of it is >now out of date. Dunno whether John Smith at UHI has anything as part >of his material for use when teaching staff about Clan? User docs is what I'm concentrating on initially plus installation stuff. Paul Wheatley has pointed me to quite a number of guides, including some for Floor managers, very handy. > > So my first request is for someone to co-ordinate the development > > documentation. Anyone like to step forward and carry out > > this important and honourable role? > ><looks round> > ><steps back> > >Unfortunately not - we don't have the spare effort that would be needed >to co-ordinate this. That's okay. We'll still welcome any comments on what's produced. - Paul |
From: Matthew B. <mat...@co...> - 2005-07-13 15:46:44
|
Alistair Young wrote: > I'd rather you sent the source file - patches don't work too well here Attached. -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-07-13 15:06:43
|
Alistair Young wrote: > I'd rather you sent the source file - patches don't work too well here The patch should apply cleanly to bodington_head. > What was the problem with facility calls? they worked here ok. > Presumably you know as you patched something? Can you explain why they > weren't compiling? Just grab a copy of Bodington HEAD and try building with skip.compile.templates unset. -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-07-13 15:04:46
|
Alistair Young wrote: > can you describe what you've done Mathew? There may not be a problem at > all. I may have localised some #defines - it's difficult to tell them > apart from Facility calls that should be localised, such as "Enter web > site" Localised some #defines? > Before you start hacking the code, can you make sure it's not a #define > that's been localised? I havn't commited it back to CVS because you know more about this but I couldn't get the templates to compile. This patch to XmlTemplate adds <localise> as a valid part of an expression (expressions are used in a <call>). >> Index: src/org/bodington/servlet/template/XmlTemplate.java >> =================================================================== >> RCS file: /cvsroot/bodington/bodington/src/org/bodington/servlet/ >> template/XmlTemplate.java,v >> retrieving revision 1.39 >> diff -u -r1.39 XmlTemplate.java >> --- src/org/bodington/servlet/template/XmlTemplate.java 6 Jul 2005 >> 17:11:03 -0000 1.39 >> +++ src/org/bodington/servlet/template/XmlTemplate.java 13 Jul >> 2005 14:22:47 -0000 >> @@ -102,7 +102,8 @@ >> "literal", >> "variable", >> "assign", >> - "call" >> + "call", >> + "localise" >> }; >> >> private static final String[] htmlfragment_tag_names= >> @@ -963,6 +964,12 @@ >> private void compileLocaliserCall(Element e) { >> writer.println("writer.println(res.getString(\"" + >> e.getAttribute("id") + "\"));" ); >> } >> + >> + private Class compileLocaliser( Element e) >> + { >> + writer.print( "res.getString(\"" + e.getAttribute("id") + >> "\")"); >> + return String.class; >> + } >> >> private void compileInputCall(Element e) { >> NamedNodeMap attrs = e.getAttributes(); >> @@ -1108,6 +1115,8 @@ >> return compileAssign( element ); >> else if ( "call".equals( element.getTagName() ) ) >> return compileCall( element ); >> + else if ( "localise".equals( element.getTagName() ) ) >> + return compileLocaliser(element); >> >> throw new ServletException( "Template bytecode compilation >> error: unknown expression." ); >> } This shows how the templates will have to change with my patch. >> Index: tomcatadd/webapps/bodington/templates/style_default/default/ >> applettop.html >> <parameters> >> <variable name="request"/> >> <variable name="writer"/> >> - <literal type="String"><localise id="page.title.text" /></ literal> >> + <localise id="page.title.text"/> >> </parameters> -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-07-13 15:03:27
|
Alistair Young wrote: > how do I compile bod without shibadd? shibadd is gone but the build is > broken as it uses it by default. I want to see these facility template > errors I've commited back a new build.xml that removes some of the shibbadd dependancies that allow the build to run (some references still remain). -- +--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-13 15:00:30
|
I'd rather you sent the source file - patches don't work too well here What was the problem with facility calls? they worked here ok. Presumably you know as you patched something? Can you explain why they weren't compiling? Alistair On 13 Jul 2005, at 15:52, Matthew Buckett wrote: > Alistair Young wrote: > >> what about the classpath part of the properties file - are you >> suggesting hard coding that into the template compiler? >> > > I'm suggesting setting the default value to the path of the > template (converted to the resource file classpath) but still allow > a different resource file to be specified if needed. > > Shall I hack up a patch that might explain this a little clearer? > > -- > +--Matthew Buckett-----------------------------------------+ > | VLE Developer, Learning Technologies Group | > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | > +------------Computing Services, University of Oxford------+ > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ > go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Alistair Y. <ali...@sm...> - 2005-07-13 14:54:00
|
how do I compile bod without shibadd? shibadd is gone but the build is broken as it uses it by default. I want to see these facility template errors Alistair |
From: Matthew B. <mat...@co...> - 2005-07-13 14:52:06
|
Alistair Young wrote: > what about the classpath part of the properties file - are you > suggesting hard coding that into the template compiler? I'm suggesting setting the default value to the path of the template (converted to the resource file classpath) but still allow a different resource file to be specified if needed. Shall I hack up a patch that might explain this a little clearer? -- +--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-13 14:41:34
|
what about the classpath part of the properties file - are you suggesting hard coding that into the template compiler? Alistair On 13 Jul 2005, at 15:36, Matthew Buckett wrote: > Alistair Young wrote: > >>> Could have a default behaviour, that if the properties file >>> isn't named at all, it looks for one with the same name as the >>> template >>> >> The Localiser doesn't know the name of the template - it's a >> system- wide localiser so that won't work >> > > But the template compiler knows the name of the template. If the > template compiler expanded in the default resource names (from the > template name and loction) this could save allot of typing (and > typos). > > -- > +--Matthew Buckett-----------------------------------------+ > | VLE Developer, Learning Technologies Group | > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | > +------------Computing Services, University of Oxford------+ > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ > go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Alistair Y. <ali...@sm...> - 2005-07-13 14:38:57
|
can you describe what you've done Mathew? There may not be a problem at all. I may have localised some #defines - it's difficult to tell them apart from Facility calls that should be localised, such as "Enter web site" Before you start hacking the code, can you make sure it's not a #define that's been localised? Alistair On 13 Jul 2005, at 15:29, Matthew Buckett wrote: > At the moment I don't seem to be able to complie template that have > localised facility calls. Attached is a patch that seems to fix this. > What do people think of it? > > -- > +--Matthew Buckett-----------------------------------------+ > | VLE Developer, Learning Technologies Group | > | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | > +------------Computing Services, University of Oxford------+ > Index: src/org/bodington/servlet/template/XmlTemplate.java > =================================================================== > RCS file: /cvsroot/bodington/bodington/src/org/bodington/servlet/ > template/XmlTemplate.java,v > retrieving revision 1.39 > diff -u -r1.39 XmlTemplate.java > --- src/org/bodington/servlet/template/XmlTemplate.java 6 Jul > 2005 17:11:03 -0000 1.39 > +++ src/org/bodington/servlet/template/XmlTemplate.java 13 Jul > 2005 14:22:47 -0000 > @@ -102,7 +102,8 @@ > "literal", > "variable", > "assign", > - "call" > + "call", > + "localise" > }; > > private static final String[] htmlfragment_tag_names= > @@ -963,6 +964,12 @@ > private void compileLocaliserCall(Element e) { > writer.println("writer.println(res.getString(\"" + > e.getAttribute("id") + "\"));" ); > } > + > + private Class compileLocaliser( Element e) > + { > + writer.print( "res.getString(\"" + e.getAttribute("id") + > "\")"); > + return String.class; > + } > > private void compileInputCall(Element e) { > NamedNodeMap attrs = e.getAttributes(); > @@ -1108,6 +1115,8 @@ > return compileAssign( element ); > else if ( "call".equals( element.getTagName() ) ) > return compileCall( element ); > + else if ( "localise".equals( element.getTagName() ) ) > + return compileLocaliser(element); > > throw new ServletException( "Template bytecode compilation > error: unknown expression." ); > } > Index: tomcatadd/webapps/bodington/templates/style_default/default/ > applettop.html > =================================================================== > RCS file: /cvsroot/bodington/bodington/tomcatadd/webapps/bodington/ > templates/style_default/default/applettop.html,v > retrieving revision 1.9 > diff -u -r1.9 applettop.html > --- tomcatadd/webapps/bodington/templates/style_default/default/ > applettop.html 12 Jul 2005 20:30:30 -0000 1.9 > +++ tomcatadd/webapps/bodington/templates/style_default/default/ > applettop.html 13 Jul 2005 14:22:47 -0000 > @@ -42,7 +42,7 @@ > <parameters> > <variable name="request"/> > <variable name="writer"/> > - <literal type="String"><localise id="page.title.text" /></ > literal> > + <localise id="page.title.text"/> > </parameters> > > </call></h3></td> > Index: tomcatadd/webapps/bodington/templates/style_default/default/ > error403.html > =================================================================== > RCS file: /cvsroot/bodington/bodington/tomcatadd/webapps/bodington/ > templates/style_default/default/error403.html,v > retrieving revision 1.4 > diff -u -r1.4 error403.html > --- tomcatadd/webapps/bodington/templates/style_default/default/ > error403.html 12 Jul 2005 20:31:01 -0000 1.4 > +++ tomcatadd/webapps/bodington/templates/style_default/default/ > error403.html 13 Jul 2005 14:22:47 -0000 > @@ -26,7 +26,7 @@ > <parameters> > <variable name="request"/> > <variable name="response"/> > - <literal type="String"><localise id="navigation.text" /></ > literal> > + <localise id="navigation.text" /> > </parameters> > > </call></p><p>&nbsp;</p><p>&nbsp;</p> > Index: tomcatadd/webapps/bodington/templates/style_default/default/ > login_anon.html > =================================================================== > RCS file: /cvsroot/bodington/bodington/tomcatadd/webapps/bodington/ > templates/style_default/default/login_anon.html,v > retrieving revision 1.3 > diff -u -r1.3 login_anon.html > --- tomcatadd/webapps/bodington/templates/style_default/default/ > login_anon.html 12 Jul 2005 20:32:20 -0000 1.3 > +++ tomcatadd/webapps/bodington/templates/style_default/default/ > login_anon.html 13 Jul 2005 14:22:47 -0000 > @@ -118,7 +118,7 @@ > <parameters> > <variable name="request"/> > <variable name="writer"/> > - <literal type="String"><localise > id="enter.website" /></literal> > + <localise id="enter.website" /> > </parameters> > </call> > </p> > Index: tomcatadd/webapps/bodington/templates/style_default/default/ > login_step4.html > =================================================================== > RCS file: /cvsroot/bodington/bodington/tomcatadd/webapps/bodington/ > templates/style_default/default/login_step4.html,v > retrieving revision 1.9 > diff -u -r1.9 login_step4.html > --- tomcatadd/webapps/bodington/templates/style_default/default/ > login_step4.html 12 Jul 2005 20:19:06 -0000 1.9 > +++ tomcatadd/webapps/bodington/templates/style_default/default/ > login_step4.html 13 Jul 2005 14:22:47 -0000 > @@ -74,7 +74,7 @@ > <parameters> > <variable name="request"/> > <variable name="writer"/> > - <literal type="String"><localise > id="enter" /></literal> > + <localise id="enter" /> > </parameters> > </call> > <br /><br /> > |
From: Antony C. <an...@sm...> - 2005-07-13 14:36:57
|
They're free to early adopters. A clever lad like you should be able to work it out !-) Apologies for getting ratty but I've just taken all morning to get a working version off HEAD (yes it's in a state of flux) and build.. Happy committing On 13 Jul 2005, at 15:23, Alexis O'Connor wrote: > Antony Corfield wrote: >> Thanks, finally!! actually, my last email was sent before I received >> your other one so thanks. Anyway, no need to document build.xml - I >> just wrote my own version!-) >> Antony > > Hmmm... 'transparent', 'self-describing' 'fool-proof' ... > > Thanks for the UHI CLAN icons and hyperlinks in Bodington HEAD - nice > touch! > > Alexis > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event hosted > by HP, AMD, and NVIDIA. To register visit > http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Matthew B. <mat...@co...> - 2005-07-13 14:36:56
|
Alistair Young wrote: >> Could have a default behaviour, that if the properties file isn't >> named at all, it looks for one with the same name as the template > > The Localiser doesn't know the name of the template - it's a system- > wide localiser so that won't work But the template compiler knows the name of the template. If the template compiler expanded in the default resource names (from the template name and loction) this could save allot of typing (and typos). -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-07-13 14:29:54
|
At the moment I don't seem to be able to complie template that have localised facility calls. Attached is a patch that seems to fix this. What do people think of it? -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Alexis O'C. <ale...@co...> - 2005-07-13 14:23:35
|
Antony Corfield wrote: > Thanks, finally!! actually, my last email was sent before I received > your other one so thanks. Anyway, no need to document build.xml - I just > wrote my own version!-) > Antony > Hmmm... 'transparent', 'self-describing' 'fool-proof' ... Thanks for the UHI CLAN icons and hyperlinks in Bodington HEAD - nice touch! Alexis |
From: Peter C. <Pet...@me...> - 2005-07-13 14:10:02
|
> From: Alistair Young [mailto:ali...@sm...]=20 > Python? That is for children. A Klingon Warrior uses > only machine code, keyed in on the front panel switches > in raw binary. Heh. It's 20 years since I last had to do that... one of the disk packs failed on the mainframe, and we had to boot it off punched card. We had to toggle the bootloader in on the front panel switches. Marginally worse than the time some idiot ran a disk exerciser for so long that the power transistors driving the disk arm overheated, melted their solder and fell out of the PCB... - Peter "Where's me Zimmer frame?" Crowther |
From: Antony C. <an...@sm...> - 2005-07-13 14:07:08
|
Thanks, finally!! actually, my last email was sent before I received your other one so thanks. Anyway, no need to document build.xml - I just wrote my own version!-) Antony On 13 Jul 2005, at 14:57, Alexis O'Connor wrote: > Antony Corfield wrote: >> Ok Alexis, as a developer, I don't want to deploy a war file, I just >> want to build the webapp and copy the contents of build directory to >> ${catalina.home}/webapps wherever that might be. If I use the build >> target catalina.xml and web.xml are missing from the resulting >> WEB-INF folder. Which build target should I use? > > Deploying in the way you specify - webapp. > > You do *not* need a context.xml for that. > > Alexis > > P.S. In a quiet moment, you might like to look at the deploy-local > target. This does *not* deploy via a war file either. > > P.P.S. I had been thinking at the back of my mind that I probably did > need to write a document that describes the rationale and design of > the build.xml. This probably makes the case ;-). > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event hosted > by HP, AMD, and NVIDIA. To register visit > http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Alistair Y. <ali...@sm...> - 2005-07-13 13:59:47
|
I like 6 and 8! Klingon Programmer Top 20 things likely to be overheard if you had a Klingon Programmer: Defensive programming? Never! Klingon programs are always on the offense. Yes, offensive programming is what we do best. Specifications are for the weak and timid! This machine is GAGH! I need dual Pentium processors if I am to do battle with this code! You cannot really appreciate Dilbert unless you've read it in the original Klingon. Indentation?! - I will show you how to indent when I indent your skull! What is this talk of 'release'? Klingons do not make software 'releases'. Our software 'escapes' leaving a bloody trail of designers and quality assurance people in its wake. Klingon function calls do not have 'parameters' - they have 'arguments' -- and they ALWAYS WIN THEM. Debugging? Klingons do not debug. Our software does not coddle the weak. Bugs are good for building character in the user. I have challenged the entire ISO-9000 quality assurance team to a Bat- Leth contest on the holodeck. They will not concern us again. A TRUE Klingon Warrior does not comment his code! By filing this bug report you have challenged the honor of my family. Prepare to die! You question the worthiness of my code? I should kill you where you stand! Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are! Our competitors are without honor! Python? That is for children. A Klingon Warrior uses only machine code, keyed in on the front panel switches in raw binary. Klingon programs don't do accountancy. For that, you need a Ferengi. Klingon multitasking systems do not support "time-sharing". When a Klingon program wants to run, it challenges the scheduler in hand-to- hand combat and owns the machine. Perhaps it IS a good day to die! I say we ship it! My program has just dumped Stova Core! Behold, the keyboard of Kalis! The greatest Klingon code warrior that ever lived! |
From: Alexis O'C. <ale...@co...> - 2005-07-13 13:57:26
|
Antony Corfield wrote: > Ok Alexis, as a developer, I don't want to deploy a war file, I just > want to build the webapp and copy the contents of build directory to > ${catalina.home}/webapps wherever that might be. If I use the build > target catalina.xml and web.xml are missing from the resulting WEB-INF > folder. Which build target should I use? > Deploying in the way you specify - webapp. You do *not* need a context.xml for that. Alexis P.S. In a quiet moment, you might like to look at the deploy-local target. This does *not* deploy via a war file either. P.P.S. I had been thinking at the back of my mind that I probably did need to write a document that describes the rationale and design of the build.xml. This probably makes the case ;-). |
From: Alistair Y. <ali...@sm...> - 2005-07-13 13:52:36
|
> Could have a default behaviour, that if the properties file isn't > named at all, it looks for one with the same name as the template The Localiser doesn't know the name of the template - it's a system- wide localiser so that won't work > Doesn't it just involve renaming the properties files all the directories under res/templates/style_default need to be deleted, all the properties need to be moved up one level to res/ templates/style_default and then renamed to the name of the template they work with. A lot of cvs work. The references aren't that bad as there aren't that many templates to be done. If it really bugs you go ahead. I'm easy but I don't have time to do it. Alistair On 13 Jul 2005, at 14:45, Colin Tatham wrote: > Alistair Young wrote: > >>> Better to fix it now >>> >> it ain't "broken"! >> > > True, I just meant better to change it now, before we embark on > this (and all the future) template conversion efforts. > > > >> I see your point about an editor but that's the editor's problem, >> not the properties files' >> Is it worth putting this to the vote as it's a lot of work. >> > > Is it a lot of work? Doesn't it just involve renaming the > properties files, and the references? (Could have a default > behaviour, that if the properties file isn't named at all, it looks > for one with the same name as the template -- that's from The > Bucket :-) > > Colin > > > Who will do > >> it if it's seen as a problem? >> Alistair >> On 13 Jul 2005, at 14:29, Colin Tatham wrote: >> >>> > why bother? hasta manyana babe. It looks good to me as is >>> >>> Better to fix it now rather than try do it later. >>> Having 100's of properties files with the same name is *bound* >>> to cause confusion at some point (like you have 3 open in your >>> editor at once, and they all have the same name in the tag at >>> the top of the editor?). >>> >>> >>> Alistair Young wrote: >>> >>> >>>>> Renaming the properties files? Removing the individual folders >>>>> for each template? >>>>> >>>>> >>>> why bother? hasta manyana babe. It looks good to me as is >>>> Alistair >>>> On 13 Jul 2005, at 13:54, Colin Tatham wrote: >>>> >>>> >>>>> >>>>> I was actually getting a bit confused there... I didn't mean >>>>> to suggest that the properties files all get added to the >>>>> present templates folder, although that was what I ended up >>>>> suggesting... >>>>> >>>>> Renaming the properties files? Removing the individual folders >>>>> for each template? >>>>> >>>>> >>>>> Colin >>>>> ____________________________________ >>>>> Colin Tatham >>>>> VLE Team >>>>> Oxford University Computing Services >>>>> >>>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>>> http://bodington.org >>>>> >>>>> >>>>> Colin Tatham wrote: >>>>> >>>>> >>>>> >>>>>> Alistair Young wrote: >>>>>> >>>>>> >>>>>> >>>>>>> res/templates/style_default/default >>>>>>> -- each template has it's own directory under default, >>>>>>> within which, it's >>>>>>> strings file resides. >>>>>>> >>>>>>> >>>>>>> >>>>>> We had a discussion here, I'll try to summarise. >>>>>> (The ideas only came up when we started doing some work on >>>>>> the localisation.) >>>>>> - All the properties files have the same name, which makes >>>>>> editing a collection of them confusing. >>>>>> - Having additional folders within the folders makes it >>>>>> slightly more difficult to match templates to properties files. >>>>>> Would there be any problems if we: >>>>>> - name properties files with the same name as the template >>>>>> they refer to. >>>>>> - have the properties files in the same folder as the >>>>>> templates. They would appear in a listing along with the >>>>>> template, and any other properties files that relate to that >>>>>> template. >>>>>> Admittedly that means the style_default/default folder could >>>>>> have loads of files in it, but that's OK innit? >>>>>> Colin >>>>>> ____________________________________ >>>>>> Colin Tatham >>>>>> VLE Team >>>>>> Oxford University Computing Services >>>>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>>>> http://bodington.org >>>>>> ------------------------------------------------------- >>>>>> This SF.Net email is sponsored by the 'Do More With Dual!' >>>>>> webinar happening >>>>>> July 14 at 8am PDT/11am EDT. We invite you to explore the >>>>>> latest in dual >>>>>> core and dual graphics technology at this free one hour >>>>>> event hosted by HP, AMD, and NVIDIA. To register visit >>>>>> http:// www.hp.com/go/dualwebinar >>>>>> _______________________________________________ >>>>>> Bodington-developers mailing list >>>>>> Bod...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> This SF.Net email is sponsored by the 'Do More With Dual!' >>>>> webinar happening >>>>> July 14 at 8am PDT/11am EDT. We invite you to explore the >>>>> latest in dual >>>>> core and dual graphics technology at this free one hour event >>>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>>> www.hp.com/ go/dualwebinar >>>>> _______________________________________________ >>>>> Bodington-developers mailing list >>>>> Bod...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>>> >>>>> >>>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by the 'Do More With Dual!' >>>> webinar happening >>>> July 14 at 8am PDT/11am EDT. We invite you to explore the >>>> latest in dual >>>> core and dual graphics technology at this free one hour event >>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>> www.hp.com/go/dualwebinar >>>> _______________________________________________ >>>> Bodington-developers mailing list >>>> Bod...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>> >>>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by the 'Do More With Dual!' >>> webinar happening >>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >>> in dual >>> core and dual graphics technology at this free one hour event >>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>> www.hp.com/ go/dualwebinar >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >>> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >> happening >> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >> in dual >> core and dual graphics technology at this free one hour event >> hosted by HP, AMD, and NVIDIA. To register visit http:// >> www.hp.com/go/dualwebinar >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ > go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Colin T. <col...@co...> - 2005-07-13 13:43:42
|
Alistair Young wrote: >> Better to fix it now > > it ain't "broken"! True, I just meant better to change it now, before we embark on this (and all the future) template conversion efforts. > I see your point about an editor but that's the editor's problem, not > the properties files' > > Is it worth putting this to the vote as it's a lot of work. Is it a lot of work? Doesn't it just involve renaming the properties files, and the references? (Could have a default behaviour, that if the properties file isn't named at all, it looks for one with the same name as the template -- that's from The Bucket :-) Colin Who will do > it if it's seen as a problem? > > Alistair > > > On 13 Jul 2005, at 14:29, Colin Tatham wrote: > >> > why bother? hasta manyana babe. It looks good to me as is >> >> Better to fix it now rather than try do it later. >> Having 100's of properties files with the same name is *bound* to >> cause confusion at some point (like you have 3 open in your editor at >> once, and they all have the same name in the tag at the top of the >> editor?). >> >> >> Alistair Young wrote: >> >>>> Renaming the properties files? Removing the individual folders for >>>> each template? >>>> >>> why bother? hasta manyana babe. It looks good to me as is >>> Alistair >>> On 13 Jul 2005, at 13:54, Colin Tatham wrote: >>> >>>> >>>> I was actually getting a bit confused there... I didn't mean to >>>> suggest that the properties files all get added to the present >>>> templates folder, although that was what I ended up suggesting... >>>> >>>> Renaming the properties files? Removing the individual folders for >>>> each template? >>>> >>>> >>>> Colin >>>> ____________________________________ >>>> Colin Tatham >>>> VLE Team >>>> Oxford University Computing Services >>>> >>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>> http://bodington.org >>>> >>>> >>>> Colin Tatham wrote: >>>> >>>> >>>>> Alistair Young wrote: >>>>> >>>>> >>>>>> res/templates/style_default/default >>>>>> -- each template has it's own directory under default, within >>>>>> which, it's >>>>>> strings file resides. >>>>>> >>>>>> >>>>> We had a discussion here, I'll try to summarise. >>>>> (The ideas only came up when we started doing some work on the >>>>> localisation.) >>>>> - All the properties files have the same name, which makes >>>>> editing a collection of them confusing. >>>>> - Having additional folders within the folders makes it slightly >>>>> more difficult to match templates to properties files. >>>>> Would there be any problems if we: >>>>> - name properties files with the same name as the template they >>>>> refer to. >>>>> - have the properties files in the same folder as the templates. >>>>> They would appear in a listing along with the template, and any >>>>> other properties files that relate to that template. >>>>> Admittedly that means the style_default/default folder could have >>>>> loads of files in it, but that's OK innit? >>>>> Colin >>>>> ____________________________________ >>>>> Colin Tatham >>>>> VLE Team >>>>> Oxford University Computing Services >>>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>>> http://bodington.org >>>>> ------------------------------------------------------- >>>>> This SF.Net email is sponsored by the 'Do More With Dual!' >>>>> webinar happening >>>>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >>>>> in dual >>>>> core and dual graphics technology at this free one hour event >>>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>>> www.hp.com/go/dualwebinar >>>>> _______________________________________________ >>>>> Bodington-developers mailing list >>>>> Bod...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >>>> happening >>>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >>>> in dual >>>> core and dual graphics technology at this free one hour event >>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>> www.hp.com/ go/dualwebinar >>>> _______________________________________________ >>>> Bodington-developers mailing list >>>> Bod...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>> >>>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >>> happening >>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in >>> dual >>> core and dual graphics technology at this free one hour event hosted >>> by HP, AMD, and NVIDIA. To register visit http:// >>> www.hp.com/go/dualwebinar >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >> happening >> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual >> core and dual graphics technology at this free one hour event hosted >> by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ >> go/dualwebinar >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by > HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Antony C. <an...@sm...> - 2005-07-13 13:39:52
|
Ok Alexis, as a developer, I don't want to deploy a war file, I just want to build the webapp and copy the contents of build directory to ${catalina.home}/webapps wherever that might be. If I use the build target catalina.xml and web.xml are missing from the resulting WEB-INF folder. Which build target should I use? On 13 Jul 2005, at 14:12, Alexis O'Connor wrote: > Antony Corfield wrote: >> Why are web.xml and context.xml in this directory and not WEB-INF? >> Or, why doesn't build.xml put them there? >> > > OK, here's a comprehensive answer! > > Both the web.xml and context.xml in /etc are never used *as-is*. Each > contain tokens intended to be replaced with text strings that are > more meaningful @DISPLAY_NAME@ and @DOC_BASE@ respectively. Therefore > their use is entirely driven from the build.xml. > > The web.xml does indeed end up under ${build}/../WEB-INF/, having had > it's display name set to something like 'bodington (v2.4.3)' (in > Tomcat this appears in the HTML manager application). > > The context.xml is in particular required by the target > deploy-local-5_5. In order to deploy a web-app from a local file > system ('deploy local') that isn't under ${catalina.home}/webapps onto > Tomcat 5.5 requires this jiggery-pokery. I came to this through trial > and error, so I know that it is necessary, but that it does work(!). > It *can* go under ${build}/../WEB-INF/ if you're deploying it as a war > file), but that's not how I use it (it would be superfluous for a war > deployed to JBoss say). > > Alexis > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event hosted > by HP, AMD, and NVIDIA. To register visit > http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |
From: Alistair Y. <ali...@sm...> - 2005-07-13 13:36:27
|
> Better to fix it now it ain't "broken"! I see your point about an editor but that's the editor's problem, not the properties files' Is it worth putting this to the vote as it's a lot of work. Who will do it if it's seen as a problem? Alistair On 13 Jul 2005, at 14:29, Colin Tatham wrote: > > why bother? hasta manyana babe. It looks good to me as is > > Better to fix it now rather than try do it later. > Having 100's of properties files with the same name is *bound* to > cause confusion at some point (like you have 3 open in your editor > at once, and they all have the same name in the tag at the top of > the editor?). > > > Alistair Young wrote: > >>> Renaming the properties files? Removing the individual folders >>> for each template? >>> >> why bother? hasta manyana babe. It looks good to me as is >> Alistair >> On 13 Jul 2005, at 13:54, Colin Tatham wrote: >> >>> >>> I was actually getting a bit confused there... I didn't mean to >>> suggest that the properties files all get added to the present >>> templates folder, although that was what I ended up suggesting... >>> >>> Renaming the properties files? Removing the individual folders >>> for each template? >>> >>> >>> Colin >>> ____________________________________ >>> Colin Tatham >>> VLE Team >>> Oxford University Computing Services >>> >>> http://www.oucs.ox.ac.uk/ltg/vle/ >>> http://bodington.org >>> >>> >>> Colin Tatham wrote: >>> >>> >>>> Alistair Young wrote: >>>> >>>> >>>>> res/templates/style_default/default >>>>> -- each template has it's own directory under default, within >>>>> which, it's >>>>> strings file resides. >>>>> >>>>> >>>> We had a discussion here, I'll try to summarise. >>>> (The ideas only came up when we started doing some work on the >>>> localisation.) >>>> - All the properties files have the same name, which makes >>>> editing a collection of them confusing. >>>> - Having additional folders within the folders makes it >>>> slightly more difficult to match templates to properties files. >>>> Would there be any problems if we: >>>> - name properties files with the same name as the template they >>>> refer to. >>>> - have the properties files in the same folder as the >>>> templates. They would appear in a listing along with the >>>> template, and any other properties files that relate to that >>>> template. >>>> Admittedly that means the style_default/default folder could >>>> have loads of files in it, but that's OK innit? >>>> Colin >>>> ____________________________________ >>>> Colin Tatham >>>> VLE Team >>>> Oxford University Computing Services >>>> http://www.oucs.ox.ac.uk/ltg/vle/ >>>> http://bodington.org >>>> ------------------------------------------------------- >>>> This SF.Net email is sponsored by the 'Do More With Dual!' >>>> webinar happening >>>> July 14 at 8am PDT/11am EDT. We invite you to explore the >>>> latest in dual >>>> core and dual graphics technology at this free one hour event >>>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>>> www.hp.com/go/dualwebinar >>>> _______________________________________________ >>>> Bodington-developers mailing list >>>> Bod...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>>> >>>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by the 'Do More With Dual!' >>> webinar happening >>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >>> in dual >>> core and dual graphics technology at this free one hour event >>> hosted by HP, AMD, and NVIDIA. To register visit http:// >>> www.hp.com/ go/dualwebinar >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >>> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >> happening >> July 14 at 8am PDT/11am EDT. We invite you to explore the latest >> in dual >> core and dual graphics technology at this free one hour event >> hosted by HP, AMD, and NVIDIA. To register visit http:// >> www.hp.com/go/dualwebinar >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ > go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Alexis O'C. <ale...@co...> - 2005-07-13 13:32:13
|
Antony Corfield wrote: > but the build target doesn't! Can build be updated so that it does? The webapp target is a "super target" of build, in that it also signs the applet jar and compiles the templates. If you want both of these operations to be skipped (but want everything else to occur) when you run webapp, then add ensure 'skip.applet.sign' and 'skip.compile.templates' are set in your build.properties file. If the (optional) description attribute of a target element exists, then this should describe what that target does. 'build' and 'webapp' have these. Any target element which has a description attribute is described as "top-level". To get a list of all the top-level targets in a build.xml, type the following: $>ant -projecthelp > What's the reason for putting them in the etc directory? > See the other e-mail. Alexis |
From: Colin T. <col...@co...> - 2005-07-13 13:27:59
|
> why bother? hasta manyana babe. It looks good to me as is Better to fix it now rather than try do it later. Having 100's of properties files with the same name is *bound* to cause confusion at some point (like you have 3 open in your editor at once, and they all have the same name in the tag at the top of the editor?). Alistair Young wrote: >> Renaming the properties files? Removing the individual folders for >> each template? > > why bother? hasta manyana babe. It looks good to me as is > > Alistair > > > On 13 Jul 2005, at 13:54, Colin Tatham wrote: > >> >> I was actually getting a bit confused there... I didn't mean to >> suggest that the properties files all get added to the present >> templates folder, although that was what I ended up suggesting... >> >> Renaming the properties files? Removing the individual folders for >> each template? >> >> >> Colin >> ____________________________________ >> Colin Tatham >> VLE Team >> Oxford University Computing Services >> >> http://www.oucs.ox.ac.uk/ltg/vle/ >> http://bodington.org >> >> >> Colin Tatham wrote: >> >>> Alistair Young wrote: >>> >>>> res/templates/style_default/default >>>> -- each template has it's own directory under default, within >>>> which, it's >>>> strings file resides. >>>> >>> We had a discussion here, I'll try to summarise. >>> (The ideas only came up when we started doing some work on the >>> localisation.) >>> - All the properties files have the same name, which makes editing a >>> collection of them confusing. >>> - Having additional folders within the folders makes it slightly >>> more difficult to match templates to properties files. >>> Would there be any problems if we: >>> - name properties files with the same name as the template they >>> refer to. >>> - have the properties files in the same folder as the templates. >>> They would appear in a listing along with the template, and any >>> other properties files that relate to that template. >>> Admittedly that means the style_default/default folder could have >>> loads of files in it, but that's OK innit? >>> Colin >>> ____________________________________ >>> Colin Tatham >>> VLE Team >>> Oxford University Computing Services >>> http://www.oucs.ox.ac.uk/ltg/vle/ >>> http://bodington.org >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >>> happening >>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in >>> dual >>> core and dual graphics technology at this free one hour event hosted >>> by HP, AMD, and NVIDIA. To register visit http:// >>> www.hp.com/go/dualwebinar >>> _______________________________________________ >>> Bodington-developers mailing list >>> Bod...@li... >>> https://lists.sourceforge.net/lists/listinfo/bodington-developers >>> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >> happening >> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual >> core and dual graphics technology at this free one hour event hosted >> by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ >> go/dualwebinar >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by > HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |