Publicaciones hechas por por Urs Hunkler

Moodle in English -> Testing and QA -> Moodle Documentation and Themes

por Urs Hunkler -
Imagen de Core developers

Hi,

the documentation has it's very individual styling with it's own CSS not caring about the themes. I added a JS switch to the german doc files for testing:

If the docs are opened from within Moodle the php code within the JS is parsed and replaced by the path to the active theme. The JS tests if the php function is parsed and replaced -> this means the doc file is opend within Moodle. If it finds the php code -> this means the doc file is opened directly. If and only if the doc file is opened within Moodle the JS writes the statements for loading "styles.php" and "docstyles.php" from the themes folder into the document and the doc is styled according to the selected theme.

Why using JS? The docs can be opened directly for example before installing Moodle for information purposes. JS is neccessary to hide the php code in the directly opened html doc, or else it would be shown on top of the doc. The call for the doc CSS "docstyles.css" is written before the JS, so anybody can see the styled doc, even if JS is deactivated.

For two themes I added the CSS for the docs "docstyles.php"

  • "cornflower"
  • "standardxhtml"

Can please anybody test it (please choose the language "Deutsch (de)") and report bugs, proposals etc.

Thank you
Urs

Promedio de valuaciones (ratings): -

Moodle in English -> General developer forum -> overlib -> Re: overlib

por Urs Hunkler -
Imagen de Core developers

Hi Gustav,

please look at the outline of the planed DIV frameset of Moodle. Could you use the "wrapper" DIV for overlib, which is planed to surround the whole page?

Great to get to know somebody who knows where in the Moodle code DIVs can be placed best parpadeo. At the moment the DIVs "wrapper", "header", "nav-bar" "containerContent" and "footer" are planed to be written in "header.html" and "footer.html". Can you propose a better place?

Regards
Urs

Imagen de Core developers

Hi everybody,

the discussion here is about knowledge and knowledge management. A lot of knowledge collecting software uses one repository to store the infomation and filters like categories or flags to be able to retrieve the information in different contexts.

One needs a second way to assign the posts in the Moodle forums to different contexts. The Moodle Glossary for example uses just this technique. Otherwise you end with something I want to call exaggerated the "Forumitis".

In my opinion additional flags or better an expandable list of categories would be a big advantage for the moodle forums.

The scenario could look - like others described already:

  • Forums directly connected to the parts of Moodle and the Moodle development - as it is
  • Categories to filter for example "Usability" aspects out of all forums in one go

How to realize the infomation retrieval? It would be great to have something like "Metaforums" - one per category - just showing the collected content from other Forums without the need to search for it.

@Martin: yes, a good bug tracking will make development much more comfortable, but I doubt, that it is the best way to discuss Usability. Discussion about usability aspects of Moodle has rarely got to do with bugs.

My two cents
Urs

Moodle in English -> Themes -> multiple edit icons -> Re: multiple edit icons

por Urs Hunkler -
Imagen de Core developers

hello eugine,

> Is there a simple way to have a second /t/ folder in the pix directory?

There is no need to patch moodle. You can have a theme with your own icon set - look at the theme cordoroyblue.

You add  a parameter to your config.php like:

$THEME->custompix    = true;       // If true, then this theme must have a "pix" 
                                   // subdirectory that contains copies of all
                                   // files from the moodle/pix directory
                                   // See "cordoroyblue" for an up-to-date example.


And you copy the pix folder into your theme folder and can replace the icons as you like.

I wish you good luck and good progress with your theme
Urs

Imagen de Core developers

Hi everybody,

_ 2-Column Page
in this 2-column startpage the underlying 3-column layouttable simply "looses" it's right column by hiding it with CSS.

_ Reading on Screen
65 characters per line are much better readable on screen than the about 120 chars/line and more you get in a standard wiki page.
Proposal
- You can make the column smaler.
Objection - In a smaller column the amount of char/line decreases rapidly when you enlarge the font size.
Solution - What about letting the width of the column grow
corresponding to the growth of font size? The length of the line will stay about the same.
Can i try it? - Please have a look here.

_ Change of the Block Switch
The first approach of the block switch disabled the icons within editing mode triste. Now you switch only via the cross-icon. I think this solution is not too bad.

I'm very interested in your opinions.
Urs

Promedio de valuaciones (ratings): -