Hi Melika,
Here is the procedure:
http://docs.moodle.org/en/Translation#Submitting_your_language_pack_to_the_Moodle_project
Martin Dougiamas
Posts made by Martin Dougiamas
Here is a random Google gadget embedded in a forum post:
Many more are in the Gadget directory. If you come up with any good educational scenarios using these let us know!
Note that you need to have the "moodle/site:trustcontent" capability enabled for your role if you want to do this sort of thing in your own sites (it's off by default in all versions of Moodle for security).
Many more are in the Gadget directory. If you come up with any good educational scenarios using these let us know!
Note that you need to have the "moodle/site:trustcontent" capability enabled for your role if you want to do this sort of thing in your own sites (it's off by default in all versions of Moodle for security).
In fact Moodle 1.9.3 will be next week, on Wednesday (October 1) or the next day. 
Developers, please make a special effort to get in any outstanding patches, fix new bugs or test existing fixes before the automated Weekly build on Wednesday, so that I can release it then as Moodle 1.9.3.
Developers, please make a special effort to get in any outstanding patches, fix new bugs or test existing fixes before the automated Weekly build on Wednesday, so that I can release it then as Moodle 1.9.3.
I do like the idea of option 3 from a "make it nice and tidy" standpoint, but ...
One pro for the big static JS file is it reduces hits on the server for the first time and then it caches very nicely after that (I guess the browser can also keep it precompiled too). Lots of files means lots of hits on httpd the first time at least. This may not be a huge issue but it is the number one thing that YSlow checks for (Minimise HTTP requests). Perhaps this is offset by less loading on pages that don't need it, I'm not sure.
Another small issue is that moving files around has the potential to break local customisations etc.
Overall, I think I'd vote conservatively for option 1. If that's not popular then do it properly with option 3.
One pro for the big static JS file is it reduces hits on the server for the first time and then it caches very nicely after that (I guess the browser can also keep it precompiled too). Lots of files means lots of hits on httpd the first time at least. This may not be a huge issue but it is the number one thing that YSlow checks for (Minimise HTTP requests). Perhaps this is offset by less loading on pages that don't need it, I'm not sure.
Another small issue is that moving files around has the potential to break local customisations etc.
Overall, I think I'd vote conservatively for option 1. If that's not popular then do it properly with option 3.
Hi Julian,
Is there a good description/specification somewhere of how this grading system should work? That would help us understand how much work would be involved.
Cheers
Is there a good description/specification somewhere of how this grading system should work? That would help us understand how much work would be involved.
Cheers