Revision as of 02:25, 15 April 2013 by Damyon Wiese (talk | contribs) (Shifter version bump: new section)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
"You are not required to run a specific version of Shifter, but this is the version that Moodle YUI modules will be built with and you may find it beneficial to do so too."

Is it problematic with requiring devs to run a specific version? Cos I suppose it'd be helpful if we all were running that same version? --Dan Poltawski 09:13, 11 March 2013 (WST)

It can be problematic, but I'm trying to improve that. If a developer works on another project also using YUI, and therefore Shifter, they may want to have a different version for that project. Shifter is typically installed in a global namespace making things tricky. I've been working on a solution by having a Moodle JS toolkit which depends upon shifter and wraps it. I completed a PoC last night ( but I'm planning to rewrite it using YUI, change it's structure, and add a few features. At this point we'll be able to ask developers to npm install mjs -g (or whatever I end up naming it) and then they can run mjs -s and it (should) do the 'right' thing. --Andrew Nicols 18:50, 11 March 2013 (WST)

unsigned PPA for ubuntu

Removed the PPA for the ubuntu install instructions. I dislike recommending an unsigned unstable PPA as a requirement for moodle dev. (Even though Googling does show lots of places recommending that ppa as a psuedo default for getting upto date versions of node).

If we require a specific version of nodejs - we should list it - otherwise people should either stick to their distribution version or get the latest from

Shifter version bump

Increased the shifter recommended version to 0.3.1 ahead of 2.5 release. (MDLSITE-2210)