Are you also among those Moodlers who wants to learn the process of Moodle development? Do you also wants to learn about writing Moodle plugins from start to finish? Then, get ready for learning Moodle development through a crisp and short tutorial by Moodle experts.
מקור: Want to learn Moodle Development? Check out this new Tutorial prepared by Moodle experts #Moodledev – Moodle World – Moodle World
The Moodle Book github tool allows the import/export (pull/push) of Book content from/to GitHub. (and share a single book in several courses!)
Posts about moodleopenbook written by David Jones
מקור: moodleopenbook | The Weblog of (a) David Jones
Working in a group of developers on a large open source project like Moodle, I get times where I need to dig in and find who made a specific change to the code and most importantly… WHY? getting the developer’s name can help get in contact with him/her to figure out why was that piece of code was introduced. And if he/she is not available, I can infer from the commit the issue id and use the development system (#Moodle uses Atlassian’s Jira – the Tracker) to find out what was the reason it was introduced.
Laziness above all… I tried the GUI tools first:
- phpStorm (138.379) – When viewing a source code file, I can click on git – show history, And get all the git commit logs of that specific file. I can click ctrl-d and compare each on with the current version. But no string search for a specific change in a specific file 🙁 and no easy way to find out what commit introduced a specific line of code (as far as I know). now way to git blame 🙁 (edit: after posting this, I found out that phpStorm can, amazingly, do it: Can Git show history for selected lines?)
- gitk – Using the search tool and setting it to “Find commit: adding/removing string:” and clicking the “down arrow” while viewing the code in patch mode, I can see the list of changes, BUT I have to read through a lot of code in each commit to find the line I am looking for. not easy 🙁
- git gui blame [file] – which was nice but no searching and only got me as far as the last committer. Same as what I got off the github.com blame view for that file.
Next, the internet…
Luck me, help was coming from the open source Moodle developer community. Tim hunt which is a long time respected UK Open University developer in the Moodle community started throwing pearls of digested wizdom at me which helped me figure out which commit was responsible for that specific piece of code (a string) that I was looking for and when it was initially introduced into the code. Here are those pearls:
One pearl was to:
git blame last-commit-hash^ path/filename | grep "string"
Looking at the results, I found out the one that seems relevant and:
git show "commit-hash"
Another pearl was:
git log -S 'string' path/filename
So, thank you Tim hunt and I hope it’s useful for anyone else doing archeological digging into open source projects using git.
Atto Plugin Template (by:Justin Hunt)
I have a number of #TinyMCE plugins to port to #Atto, I went and made a simple template and it is available on #GitHub . Hopefully it will help others get up and running quickly.
ב-Moodle in English: Atto Plugin Template.
וגם עדכון מחברת JetBrains מפתחת סביבת הפיתוח האהובה עליי phpStorm, בנושא “Using GitHub without leaving PhpStorm”
קצת ישן אבל עדיין שימושי… עטיפת JS (בקוד פתוח) עבור SCORM ועוד מספר קישורים שימושיים: http://pipwerks.com/downloads/ https://github.com/pipwerks/scorm-api-wrapper http://ltsdevmusings.wordpress.com/2013/03/28/things-i-didnt-know-about-scorm/