Is the icon set available separately? I also used the fugue icon set for my theme and spent a fair bit of time deciding which Fugue icons suited which Moodle icon. It would be good to contribute that effort to an icon set that others could use.
David Scotson
Posts made by David Scotson
Hi all,
if anyone is interested in running their Continuous Integration tests on Travis-CI.org then I've uploaded a configuration file to github:
https://github.com/ds125v/moodle-travis
It's currently set up to run the standard phpunit tests (as defined in phpunit.xml) on PHP 5.3 and PHP5.4 and against both a MySQL and Postgres database.
For those unfamiliar, Travis is a free service that will checkout your latest changes from Github every time you commit and then run your unit tests and drop you an email if anything fails. See http://travis-ci.org for more.
Is this something that might become part of the core distribution of Moodle? It would be nice if people creating blocks and modules didn't inadvertantly break the build like a few of the things we've looked at installing do. And this radically reduces the overhead in getting the unit tests running, at least for anyone already using github.
They also support Selenium testing, but I don't know enough about Moodle's testing infrastructure to set that up. I'd be very interested in doing so if anyone has any experience with it.
if anyone is interested in running their Continuous Integration tests on Travis-CI.org then I've uploaded a configuration file to github:
https://github.com/ds125v/moodle-travis
It's currently set up to run the standard phpunit tests (as defined in phpunit.xml) on PHP 5.3 and PHP5.4 and against both a MySQL and Postgres database.
For those unfamiliar, Travis is a free service that will checkout your latest changes from Github every time you commit and then run your unit tests and drop you an email if anything fails. See http://travis-ci.org for more.
Is this something that might become part of the core distribution of Moodle? It would be nice if people creating blocks and modules didn't inadvertantly break the build like a few of the things we've looked at installing do. And this radically reduces the overhead in getting the unit tests running, at least for anyone already using github.
They also support Selenium testing, but I don't know enough about Moodle's testing infrastructure to set that up. I'd be very interested in doing so if anyone has any experience with it.
I've submitted a pull request via github with some example paging bars that I found useful when working on a renderer to change the look. (And in general this concept of "live" examples works very well with renderers, and saves a lot of clicking around when you make changes).
A couple of screen shots to demonstrate:
http://imgur.com/a/EjL3D
A couple of screen shots to demonstrate:
http://imgur.com/a/EjL3D
Thanks for that blog link, very informative (though it made my head hurt a little, just when I thought I maybe understood what the best thing to do was I made the mistake of reading the comments).
I can't get the YUI custom-menu stuff to work on Moodle.org, in Firefox and Chrome the only link I can follow via the keyboard is the first one. Am I doing something wrong, I thought just the arrow keys should work?
I found a blog post by the Bootstrap designers about the usability ideas behind their drop-down menus and it confirmed my hunch that in Bootstrap the list items should either be links, or clickable, but not both.
http://markdotto.com/2012/02/27/bootstrap-explained-dropdowns/
Once I fix that, I think the menu will be mostly accessible by keyboard just using tab and enter, but I'll try to apply the aria stuff from that blog as well and get the arrow keys working too.
I can't get the YUI custom-menu stuff to work on Moodle.org, in Firefox and Chrome the only link I can follow via the keyboard is the first one. Am I doing something wrong, I thought just the arrow keys should work?
I found a blog post by the Bootstrap designers about the usability ideas behind their drop-down menus and it confirmed my hunch that in Bootstrap the list items should either be links, or clickable, but not both.
http://markdotto.com/2012/02/27/bootstrap-explained-dropdowns/
Once I fix that, I think the menu will be mostly accessible by keyboard just using tab and enter, but I'll try to apply the aria stuff from that blog as well and get the arrow keys working too.
Mary can you provide more details on what kind of accessability you think is missing?
I use a weird browser extension called Pentadactyl (and/or Vimperator, it's two forks of the same project) which allows you to navigate via keyboard commands and, while it's not technically an accessability aid, it's usually a pretty good analogue. And I can navigate the menu with that.
Trying with more traditional keyboard controls, I can tab through the links and use 'enter' to trigger the pop-ups, at least in Firefox on Ubuntu. I'll happily fix any such problems reported to me. I've started adding aria- tags such as labelled by, based on the Bootstrap documentation, but to be honest I'm not that familiar with how those are supposed to work, and the Bootrap docs don't go into great detail with them.
I'd be interested to hear about screen-readers, but since it's just a nested list of links I'm assuming it at least works, even if some better aria labelling might be more helpful.
edit: some more testing with the tabbing suggests that the second level links don't work because the pop-up trigger remains a link and that takes precedent over popping up the next level. I'd actually been wondering what to do with links if there's also a popup (e.g. just ignore them), this might tip that decision over the edge.
I use a weird browser extension called Pentadactyl (and/or Vimperator, it's two forks of the same project) which allows you to navigate via keyboard commands and, while it's not technically an accessability aid, it's usually a pretty good analogue. And I can navigate the menu with that.
Trying with more traditional keyboard controls, I can tab through the links and use 'enter' to trigger the pop-ups, at least in Firefox on Ubuntu. I'll happily fix any such problems reported to me. I've started adding aria- tags such as labelled by, based on the Bootstrap documentation, but to be honest I'm not that familiar with how those are supposed to work, and the Bootrap docs don't go into great detail with them.
I'd be interested to hear about screen-readers, but since it's just a nested list of links I'm assuming it at least works, even if some better aria labelling might be more helpful.
edit: some more testing with the tabbing suggests that the second level links don't work because the pop-up trigger remains a link and that takes precedent over popping up the next level. I'd actually been wondering what to do with links if there's also a popup (e.g. just ignore them), this might tip that decision over the edge.