to point 3|
discussion needed.
i think it would be very helpfull to collect the possible versions and describe the individual advantages and disadvantages. possibly in a table in the wiki, so everybody can contribute directly with his version and arguments? on this base we can more easyly and faster come to a decision.
urs
Urs Hunkler
Posts made by Urs Hunkler
to point 2|
david and i discussed the framework of the pages in the wiki. i've got the impression, that we agree in most points. so i'll draw new diagramms, to show the actual state. on that basis we, martin and the responsible persons can decide about them.
is that ok for everyone?
urs
david and i discussed the framework of the pages in the wiki. i've got the impression, that we agree in most points. so i'll draw new diagramms, to show the actual state. on that basis we, martin and the responsible persons can decide about them.
is that ok for everyone?
urs
to point 1|
in the desveloper wiki i started to collect the necessary informations to be able to build up a naming scheme.
who are the persons to decide about it - it's martin. And other developers?
_ who are they?
_ how are such decisions made in the moodle developer community?
urs
in the desveloper wiki i started to collect the necessary informations to be able to build up a naming scheme.
who are the persons to decide about it - it's martin. And other developers?
_ who are they?
_ how are such decisions made in the moodle developer community?
urs
hello david,
i agree in all points.
but you cannot start removing parts in the templates without adding the style definitions to the css.
the steps - as i see them - are:
1| set up a naming scheme and achieve agreement with the developers
2| define the framework of the pages to get the necessary styling hooks (tables and divs with ids and classes determined in 1|)
3| decide about the strukture of the css files (1 css file + config.php, 2 css files, 2 css files + non standard css, etc.)
4| rework the css files to meet the decided structure
5| remove the formating (font tags, inline styles) in the templates (php and html) and add the formating as css definitions to the css files
6| build new themes to reflect the extended possibilities
7| write a documentation with two levels: a) all the basics needed to adjust the styling for simple changes b) detailed descriptions for advanced design changes
8| create a moodle course about styling moodle???
urs
i agree in all points.
but you cannot start removing parts in the templates without adding the style definitions to the css.
the steps - as i see them - are:
1| set up a naming scheme and achieve agreement with the developers
2| define the framework of the pages to get the necessary styling hooks (tables and divs with ids and classes determined in 1|)
3| decide about the strukture of the css files (1 css file + config.php, 2 css files, 2 css files + non standard css, etc.)
4| rework the css files to meet the decided structure
5| remove the formating (font tags, inline styles) in the templates (php and html) and add the formating as css definitions to the css files
6| build new themes to reflect the extended possibilities
7| write a documentation with two levels: a) all the basics needed to adjust the styling for simple changes b) detailed descriptions for advanced design changes
8| create a moodle course about styling moodle???
urs
I've searched the code and found the relevant locations in the code
if you are interested you can have a look at the Developer Wiki / "Reforming the CSS" / "Template Changes - First step"
urs
if you are interested you can have a look at the Developer Wiki / "Reforming the CSS" / "Template Changes - First step"
urs