The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.
Friday, 25 April 2014 16:13
A new version of Modules Anywhere has been released.
25-Apr-2014 : v3.4.3
^ Updated translations: id-ID
# Fixed issue with html structure issues when tags are directly inside html 5 elements
# [J3.3] Fixed some Joomla 3.3 incompatibility issues
Read more https://www.nonumber.nl/news/releases/891-modules-anywhere-v3-4-3-released
Read more https://feeds.joomla.org/~r/JoomlaExtensions/~3/xocY1xT7WvY/27112
Read more https://feeds.joomla.org/~r/JoomlaExtensions/~3/BAz6pVr6Yis/27106
The Joomla! Project is pleased to announce the availability of the Joomla! 3.3 Release Candidate. Community members are asked to download and install the package in order to provide quality assurance for the forthcoming 3.3 release, which is scheduled for release on or around April 30th, 2014.
A big thank you goes out to everyone that contributed to the 3.3 release! Joomla! 3.3 will be our most stable release ever. Right now we're at about 395 commits since 3.2.3's release with 44 different people contributing to those commits (not including testers and other non-coding activities). Best of all is that the new features are awesome!
The 3.x release series is the latest major release of the Joomla! CMS, with 3.3 the fourth release in this series. Please note that going from 3.2 to 3.3 is a one-click upgrade and is NOT a migration. The same is true is for any subsequent versions in the 3.x series. That being said, please do not upgrade any of your production sites to the release candidate as it is ONLY intended for testing....
Read more https://feeds.joomla.org/~r/JoomlaAnnouncements/~3/CZN1Cqiesfo/5544-joomla-3-3-rc-released.html
Marc Harter, who is working with me on Node.js in Practice, recently published Managing Node.js Callback Hell:
Callback hell is subjective, as heavily nested code can be perfectly fine sometimes. Asynchronous code is hellish when it becomes overly complex to manage the flow. A good question to see how much “hell” you are in is: how much refactoring pain would I endure if
doAsync2
happened beforedoAsync1
? The goal isn’t about removing levels of indentation but rather writing modular (and testable!) code that is easy to reason about and resilient.
The example he uses is nested asynchronous file operations, with a counter to determine completion. This is compared to a version that uses async, and another that uses promises with q.
The post was originally published on StrongLoop’s blog, here: Managing Node.js Callback Hell with Promises, Generators and Other Approaches. StrongLoop’s blog is worth subscribing to if you’re a Node developer – it has general tutorials and coverage of interesting npm modules.
Tom Boutell sent in a blog post about OO in JavaScript, called “this” considered harmful (sometimes):
Most JavaScript implementations of “classes” do have certain features in common. They rely on the “this” keyword to refer to the current object; after all, it’s built into the language. They provide a convenience function to implement subclassing, because it’s tricky to get right, especially in older browsers. And they have a really tough time handling callbacks in methods, because “this” ceases to refer to the object you expect.
Tim Oxley posted some comments discussing how to use Function.prototype.bind
as well.
Read more https://feedproxy.google.com/~r/dailyjs/~3/tbXaPrX8M90/callback-hell
Page 782 of 1299