bodington-developers

[Bodington-developers] MySQL support now in HEAD

[Andrew B. <a.g...@le...>]

I have committed MySQL support to HEAD (documentation in docs).

Can I have an opinion about committing the peer-marker tool?

Also, I have converted the MCQ tool to the new templates and localised the
text, both template and in-code. Shall I commit it?

Aggie

Re: [Bodington-developers] MySQL support now in HEAD

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

Andrew Booth wrote:
> I have committed MySQL support to HEAD (documentation in docs).

I still feel that having a different database schema for different
database products is making a rod for our own backs and changing the
tables to:
fields -> map_fields
objects -> map_objects
classes -> map_classes

(or other) would be a better soloution in the long run.

> Can I have an opinion about committing the peer-marker tool?

I liked the tool. Do you have a patch available to look at? Does it
change anything outside the new tool?

> Also, I have converted the MCQ tool to the new templates and localised the
> text, both template and in-code. Shall I commit it?

Did you remove the <building> tags or just convert the page to <xml>?

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

RE: [Bodington-developers] MySQL support now in HEAD

[Andrew B. <a.g...@le...>]

>> I have committed MySQL support to HEAD (documentation in docs).

>I still feel that having a different database schema for different
>database products is making a rod for our own backs and changing the
>tables to:
>fields -> map_fields
>objects -> map_objects
>classes -> map_classes
>
>(or other) would be a better soloution in the long run.

I agree - and I put a comment to that effect in the code

>> Can I have an opinion about committing the peer-marker tool?

>I liked the tool. Do you have a patch available to look at? Does it
>change anything outside the new tool?

No - I don't have a patch (yet).  I have tried to keep the changes outside
the tool to a minimum. (e.g. I subclassed Faculty rather than adding yet
more code to it.)

>> Also, I have converted the MCQ tool to the new templates and localised
the
>> text, both template and in-code. Shall I commit it?

>Did you remove the <building> tags or just convert the page to <xml>?

Removed the <building> tags and converted everything to the new format.

Aggie

Re: [Bodington-developers] MySQL support now in HEAD

[Sean M. <se...@sm...>]

Greetings from flooding Southern California!

Aggie, all sounds +. If the peer marker is contained, then I would think =
a
commit to head would allow for testing and we could see what it does and
how well.

It could always roll back, non?

I think that Matthew has some strong points here about the MySQL stuff.
Surely it would be better to generalize and work from the *one* schema!

-s


<quote who=3D"Matthew Buckett">
> Andrew Booth wrote:
>> I have committed MySQL support to HEAD (documentation in docs).
>
> I still feel that having a different database schema for different
> database products is making a rod for our own backs and changing the
> tables to:
> fields -> map_fields
> objects -> map_objects
> classes -> map_classes
>
> (or other) would be a better soloution in the long run.
>
>> Can I have an opinion about committing the peer-marker tool?
>
> I liked the tool. Do you have a patch available to look at? Does it
> change anything outside the new tool?
>
>> Also, I have converted the MCQ tool to the new templates and localised
>> the
>> text, both template and in-code. Shall I commit it?
>
> Did you remove the <building> tags or just convert the page to <xml>?
>
> --
>  -- Matthew Buckett, VLE Developer
>  -- Learning Technologies Group, Oxford University Computing Services
>  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>


--=20
Sean Mehan
Head of e-Frameworks
Learning and Information Services
UHI

RE: [Bodington-developers] MySQL support now in HEAD

[Andrew B. <a.g...@le...>]

Generalising the schema is a good idea, but bear in mind that we lose
backward compatibility at that point.

Aggie

-----Original Message-----
From: bod...@li...
[mailto:bod...@li...] On Behalf Of =
Sean
Mehan
Sent: 28 March 2006 15:13
To: bod...@li...
Cc: bod...@li...
Subject: Re: [Bodington-developers] MySQL support now in HEAD

Greetings from flooding Southern California!

Aggie, all sounds +. If the peer marker is contained, then I would think =
a
commit to head would allow for testing and we could see what it does and
how well.

It could always roll back, non?

I think that Matthew has some strong points here about the MySQL stuff.
Surely it would be better to generalize and work from the *one* schema!

-s


<quote who=3D"Matthew Buckett">
> Andrew Booth wrote:
>> I have committed MySQL support to HEAD (documentation in docs).
>
> I still feel that having a different database schema for different
> database products is making a rod for our own backs and changing the
> tables to:
> fields -> map_fields
> objects -> map_objects
> classes -> map_classes
>
> (or other) would be a better soloution in the long run.
>
>> Can I have an opinion about committing the peer-marker tool?
>
> I liked the tool. Do you have a patch available to look at? Does it
> change anything outside the new tool?
>
>> Also, I have converted the MCQ tool to the new templates and =
localised
>> the
>> text, both template and in-code. Shall I commit it?
>
> Did you remove the <building> tags or just convert the page to <xml>?
>
> --
>  -- Matthew Buckett, VLE Developer
>  -- Learning Technologies Group, Oxford University Computing Services
>  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D=
121642
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>


--=20
Sean Mehan
Head of e-Frameworks
Learning and Information Services
UHI


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting =
language
that extends applications into web and mobile media. Attend the live =
webcast
and join the prime developer group breaking into this new coding =
territory!
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
_______________________________________________
Bodington-developers mailing list
Bod...@li...
https://lists.sourceforge.net/lists/listinfo/bodington-developers

Re: [Bodington-developers] MySQL support now in HEAD

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

Andrew Booth wrote:
> Generalising the schema is a good idea, but bear in mind that we lose
> backward compatibility at that point.

But don't we just provide SQL migration?

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

RE: [Bodington-developers] MySQL support now in HEAD

[Sean M. <se...@sm...>]

well, in principle, so what?-)

i mean, who but us is running!-) and if we agreed, well then, new people
wouldn't feel the pain!-)

surely we could provide a little tool to port from old to new.....

where is the great peter crowther. he usually has an (un)informed opinion=
 !-)


s


<quote who=3D"Andrew Booth">
> Generalising the schema is a good idea, but bear in mind that we lose
> backward compatibility at that point.
>
> Aggie
>
> -----Original Message-----
> From: bod...@li...
> [mailto:bod...@li...] On Behalf Of
> Sean
> Mehan
> Sent: 28 March 2006 15:13
> To: bod...@li...
> Cc: bod...@li...
> Subject: Re: [Bodington-developers] MySQL support now in HEAD
>
> Greetings from flooding Southern California!
>
> Aggie, all sounds +. If the peer marker is contained, then I would thin=
k a
> commit to head would allow for testing and we could see what it does an=
d
> how well.
>
> It could always roll back, non?
>
> I think that Matthew has some strong points here about the MySQL stuff.
> Surely it would be better to generalize and work from the *one* schema!
>
> -s
>
>
> <quote who=3D"Matthew Buckett">
>> Andrew Booth wrote:
>>> I have committed MySQL support to HEAD (documentation in docs).
>>
>> I still feel that having a different database schema for different
>> database products is making a rod for our own backs and changing the
>> tables to:
>> fields -> map_fields
>> objects -> map_objects
>> classes -> map_classes
>>
>> (or other) would be a better soloution in the long run.
>>
>>> Can I have an opinion about committing the peer-marker tool?
>>
>> I liked the tool. Do you have a patch available to look at? Does it
>> change anything outside the new tool?
>>
>>> Also, I have converted the MCQ tool to the new templates and localise=
d
>>> the
>>> text, both template and in-code. Shall I commit it?
>>
>> Did you remove the <building> tags or just convert the page to <xml>?
>>
>> --
>>  -- Matthew Buckett, VLE Developer
>>  -- Learning Technologies Group, Oxford University Computing Services
>>  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> language
>> that extends applications into web and mobile media. Attend the live
>> webcast
>> and join the prime developer group breaking into this new coding
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&da=
t=3D121642
>> _______________________________________________
>> Bodington-developers mailing list
>> Bod...@li...
>> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>>
>
>
> --
> Sean Mehan
> Head of e-Frameworks
> Learning and Information Services
> UHI
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=12164=
2
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>


--=20
Sean Mehan
Head of e-Frameworks
Learning and Information Services
UHI