I think it's self-contained. I just copied the relevant folder (admintool/elementlibrary) into my Moodle. I have a vague recollection of it not working (or perhaps just complaining about version requirements) on a specific version of Moodle (maybe 2.3?) but it's working for me on master.
David Scotson
Posts made by David Scotson
I just noticed you said this generator doesn't have a UI. So is this a replacement for the generator found at :
/admin/tool/generator/index.php
(which also has a CLI interface). If it is something different, do you have a link to where it's being worked on?
/admin/tool/generator/index.php
(which also has a CLI interface). If it is something different, do you have a link to where it's being worked on?
If we continue the analogy to Unit Tests (where you test each thing in isolation) then Tim's idea is more of an integration test (where you combine the smaller units into something bigger). Both are complementary and have unique capabilities to find problems.
As an example, the page I added was for the paging bar renderer. This is used in various places in Moodle e.g. course logs or lists of students but should work the same in each place. As shown in my screenshot link above, I create page 1 through 7 out of 7, 1-20 out of 20, and 50-60 out of 60 for a total of 37 paging bars all on one page (it should really include a few more short bars as well e.g. page 1 of 2 etc.) Seeing that all in one place is vital to get an overview of this little component and how it behaves along a couple of dimensions of change (number of total pages and current page). Changing one bit of markup could effect any and all of those states, so you need to see them all in order to have the confidence to iterate quickly without breaking things.
But, if that paging bar looks out of place when used in the logs, or the student lists, then it's still not right. So links to actual usages, and a data generator to create them if necessary would be good too. It would probably be a good way to check that the data generator is actually creating useful data for development and testing. For example I noticed recently when looking at editing categories that the generator doesn't create any. I feel this might have been a factor in people putting some buttons at the bottom of a list which, when the list of categories grows, get pushed off the bottom of the screen.
As an example, the page I added was for the paging bar renderer. This is used in various places in Moodle e.g. course logs or lists of students but should work the same in each place. As shown in my screenshot link above, I create page 1 through 7 out of 7, 1-20 out of 20, and 50-60 out of 60 for a total of 37 paging bars all on one page (it should really include a few more short bars as well e.g. page 1 of 2 etc.) Seeing that all in one place is vital to get an overview of this little component and how it behaves along a couple of dimensions of change (number of total pages and current page). Changing one bit of markup could effect any and all of those states, so you need to see them all in order to have the confidence to iterate quickly without breaking things.
But, if that paging bar looks out of place when used in the logs, or the student lists, then it's still not right. So links to actual usages, and a data generator to create them if necessary would be good too. It would probably be a good way to check that the data generator is actually creating useful data for development and testing. For example I noticed recently when looking at editing categories that the generator doesn't create any. I feel this might have been a factor in people putting some buttons at the bottom of a list which, when the list of categories grows, get pushed off the bottom of the screen.
Hi Mary,
your suggestion here seems to indicate that you can override core js from the theme. Is that really possible? It would be pretty useful if it was.
your suggestion here seems to indicate that you can override core js from the theme. Is that really possible? It would be pretty useful if it was.
Moodle in English -> Themes -> Need "blank" pix -> Re: Need "blank" pix
by David Scotson -
You should be able to set the size of the spacer via CSS.