Skip to content

Software Development News: .NET, Java, PHP, Ruby, Agile, Databases, SOA, JavaScript, Open Source

Methods & Tools

Subscribe to Methods & Tools
if you are not afraid to read more than one page to be a smarter software developer, software tester or project manager!

The Dojo Toolkit - Announcements
Syndicate content
Unbeatable JavaScript Tools
Updated: 12 hours 5 min ago

Dojo Recap – April, 2016

Sat, 04/30/2016 - 13:53

It’s been a very productive and busy year to date as work towards Dojo 2. This post contains a quick summary of the updates we’ve made!

Dojo 1.11 released!

In late March, we released Dojo 1.11, along with updates to 1.10, 1.9, 1.8, and 1.7. Visit the Dojo download site to grab a tarball, or use GitHub, bower, or npm to install the latest versions. Note that the Google CDN has been slow to respond, and has not yet updated to 1.11.1.

The upgrade from 1.10 to 1.11 should be very straightforward, as the release is primarily a bug fix release, along with the addition of the new flat theme and a small number of additions. See the complete list of bugs closed for this release or the commits within each repository (e.g. all Dojo 1.11 commits for more information on the release!

We received a tremendous amount of community support to make this release possible. Thank you for your help!

Note that a 1.11.2 release is planned for May.

High level Dojo 2 progress

The overall Dojo 2 progress is tracked at dojo/meta:

dojo/meta status

dojo/loader and dojo/compose are now in a beta state and dojo/core and dojo/dom, while still listed as alpha due to anticipated API changes, are very usable in their current state.

In the past month, the dojo/widgets prototype has been added, and feedback is greatly appreciated. dojo/actions is another recent package addition. Kitson Kelly and Dylan Schiemann gave a brief overview of dojo/widgets and dojo/compose at a recent London Ajax event.

Support for ImmutableJS and RxJS was also added to relevant packages within Dojo 2.

Detailed Dojo 2 updates

Over the past month, we completed the following:

Core loader dom compose parser meta dojo2-package-template Dojo 2 in progress

More than 100 issues are currently in progress. Some of the highlights include:

Please let us know if you would like to get involved! Either find us on IRC, leave a comment here, or start contributing on GitHub.

I’d like to specifically thank taoqf who has become actively involved through contributions and feedback on dts-generator, dom, meta, dstore, core and loader. We greatly appreciate the help!

Categories: Open Source, RIA

Dojo Spring 2016 events

Tue, 04/05/2016 - 13:56

There are a number of Dojo events this spring and early summer. We hope to meet you at one of these events. Let us know if there’s an event you would like to host in your area.

Conferences

Conferences we’re planning to attend and/or deliver talks.

Meetups Training Workshops
  • SitePen Workshops. SitePen offers a number of online and in-person workshops focused on Dojo, ES6/TypeScript, and Intern. Paid registration required.

Let us know if you’re speaking at an event, and we’ll add you to our listings!

Categories: Open Source, RIA

Case Study: ZOLL Web Console

Mon, 01/18/2016 - 15:02

This post continues our series of interviews with users of Dojo. This time, we interview Eric W. Brown who led the technical team that created the ZOLL Web Console and ZOLL TBI Console during his days at ZOLL Medical (Eric is now with ThoughtSynth). ZOLL is a resuscitation company known for its defibrillators. Its Web Console runs on its high-end mobile monitors and defibrillators and enables the device not just to stream waveform data live to browsers on desktops or mobile devices, but also to collect the streamed output from up to forty devices for a single display on a desktop browser. This makes it easier for nurses to monitor a whole ward of patients. The TBI Console helps provide additional information for emergency personnel treating traumatic brain injury patients and is displayed on a mobile device. So far as we know, these were among the first JavaScript-based medical products to receive FDA approval.

Q: How did you first learn about Dojo?

I’ve been using Dojo for years. Its Pythonesque “batteries-included” approach made it appealing for some internal mapping products I did at another company long ago back in the Dojo 0.4.1 days. I’ve been using it off and on for various projects since.

Q: Why did you choose Dojo?

A: For the ZOLL projects we needed a solution that could accommodate several developers working in parallel on a complicated application with high demands on performance. If streaming waveform data doesn’t get displayed at its destination within a tiny fraction of a second, it’s useless to the medical personnel.

Dojo’s modules and pub/sub capabilities allowed us to nicely isolate the different components developers were working on while still delivering excellent performance.

Dojo’s extensive selection of modules also saved us a lot of work outside our project domain, and its build system enabled us to get the tightly optimized components we wanted for our embedded devices.

Dijit’s built-in i18n features and DOH were also big wins for us.

Q: Were you previously using another toolkit?

A: No, it was Dojo from the get-go.

Q: What does your application or service do?

A: The ZOLL Web Console provides two primary capabilities: it enables a nurse to watch over up to forty connected patients on a single desktop browser, and it enables emergency personnel to see patient information on a different screen in addition to the one built into the monitor itself.

Q: How does your application use Dojo?

A: It’s built with Dojo from the ground up. Visual elements are made with Dijit, and Dojo core is used everywhere.

Q: Overall what is your experience with Dojo?

A: Very positive. ZOLL has now built two products using Dojo. If it had been a bad experience we wouldn’t have built a second one.

Q: What’s your favorite thing about Dojo?

A: I have a different favorite Dojo feature associated with each Dojo project I’ve worked on, and perhaps this is Dojo’s greatest strength: whatever it is one is working on, there’s bound to be something Dojo already has that’ll save time and effort.

Q: What are your future plans with Dojo?

A: I am now working at ThoughtSynth rather than ZOLL, but when I left they were considering Dojo for additional projects. Here at ThoughtSynth we’re using it on behalf of clients in their projects plus internally to provide nicer front-ends for output on our own tests.

Thanks!

Thanks Eric for telling us about your experience with Dojo. If you would like to share your experience with Dojo, please contact us.

Categories: Open Source, RIA

Dojo Recap – Week Ending January 8, 2016

Tue, 01/12/2016 - 22:43
Up next in Dojo 1.x

We were incredibly active over the holidays triaging and working through issues for the Dojo 1.11 release. I personally read all 1300+ open tickets, and made the decision to close about 800 tickets. Given that we are starting to aggressively work on Dojo 2, it was time to be realistic about what we can actually fix, vs. what we need help from the community to fix. As such, I closed about 650 tickets as those which require a contribution or they will not get fixed, and another 150 as things that have already been fixed, or things we were able to fix over the holidays!

My feeling is that in order for the issue tracking system to be useful, it needs to have a manageable number of tickets, so that we can respond to all new issues quickly. I was also able to land nearly 100 pull requests, many of which were from the community. I wish we had been able to get to this a few years ago, and my goal is to get our number of open tickets down to below 200 within the next couple of months.

Ticket Graph

We are now aiming to finish the remaining dozen Dojo 1.11 tickets by the end of the month, do a release candidate, and then release 1.11 in February!

Rather than listing the large number of items that were fixed, I’ll simply provide some relevant links:

Recently in dgrid and dstore

dgrid 1.0 was released this week, as well as dgrid 0.4.1. dstore 1.1.1 was also released at the same time.

Recently in Intern

Work has been done to add several new features to Intern including collapsible test suites in the HTML reporter, support for CodeShip and Bamboo, documentation for driving Intern tests via Gulp, and to allow test suites to be skipped more efficiently.

Experimental work has also started on a refactor of Intern in TypeScript.

Recently in Dojo 2

We’re making further progress on Dojo 2 as well. We’ve made significant progress as follows:

Upcoming Dojo 2 efforts

We are currently working on the initial design document for Dojo 2’s widgets, and continuing to make progress on each package. If you’re interested in helping out in these areas, or other parts of Dojo 2, just let us know, either in the comments or on IRC.

Weekly IRC meeting

We’ve moved the minutes for our meetings for 2016. Meetings are still 9am US Pacific time on Tuesdays, IRC, #dojo-meeting.

Thanks!

Thanks for your help in improving Dojo 1.x and towards Dojo 2!

Categories: Open Source, RIA