Dojo Recap – April, 2016

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!

Dojo Spring 2016 events

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!

Case Study: ZOLL Web Console

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.

Continue reading Case Study: ZOLL Web Console

Dojo Recap – Week Ending January 8, 2016

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!

Case Study: Masternaut

This post continues our series of interviews with users of Dojo. This time, we interview Stéphane Le Choisnier of Masternaut.

Q: How did you first learn about Dojo?

A: At the beginning of our Connect application lifecycle (at the proof of concept stage), we were looking for a JavaScript toolkit or framework that could facilitate development of features with a good community supporting it and a roadmap for future enhancements. The context of our project was a distributed team shared between the UK and France, therefore, we needed a toolkit that encouraged people to adopt common coding practices; Dojo provides the toolkit to meet these goals.

When I started working on the project, Dojo had already been chosen. So far, nothing has pushed us to change our framework or toolkit.

Continue reading Case Study: Masternaut

Dojo Recap – Week Ending December 18, 2015

Up next in Dojo 1.x

We are actively triaging and working through issues for the Dojo 1.11 release, and updated point releases for earlier versions of Dojo. We have about 30 more issues to resolve, and then we’ll be ready for the 1.11 release! The main things we are considering for 1.11 are as follows:

Recently in Dojo 2

We’re making further progress on Dojo 2 as well. Last week our focus was on Compose, core, and parser:

core

parser

package-template

Upcoming Dojo 2 efforts

Here we’ve identified a few of our aspirations for near future. Over the holiday weeks, we have more code reviews to complete and pull requests to land. 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.

  • Review and improve the Compose and parser prototypes
  • Define and refine the approach to widgets and application architecture for Dojo 2
  • Continue to review and land code for Core, Crypto, DOM, dstore, i18n, Loader, and Routing

We are also actively working on the following:

Core

package-template

Weekly IRC meeting

Meetings are canceled for the remainder of the year.

Thanks!

The Dojo 2 loader, core, and dom are near an alpha state! Progress is being made on routing, crypto, i18, dstore, Compose and parser. Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate.

Happy holidays to you all, and thanks for your help in improving Dojo 1.x this year, and towards Dojo 2!

Dojo Winter 2015-2016 Events

There are a number of Dojo events this winter Some of these events are still tentative, so we’ll add links once they are confirmed. 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.

  • HIMSS, Las Vegas, February 29 – March 4, 2016
  • Esri DevSummit, Palm Springs, March 7-11, 2016

Meetups

  • CMV, Palm Springs, March 9, 2016
  • London Ajax, London, March 14, 2016

Training Workshops

Dojo Recap – Week Ending December 11, 2015

Recently in Dojo 1.x

Last week we made one enhancement to Dojo 1.x:

DojoX

Up next in Dojo 1.x

We are starting to put together a release plan for 1.11, and updated point releases for earlier versions of Dojo. We have about 30 more issues to resolve, and then we’ll be ready for the 1.11 release! The main things we are considering for 1.11 are as follows:

Recently in Dojo 2

We’re making further progress on Dojo 2 as well. Last week our focus was on Compose, core, and parser:

Compose

core

parser

Upcoming Dojo 2 efforts

Here we’ve identified a few of our aspirations for near future. This week in Dojo 2, we have more code reviews to complete and pull requests to land. 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.

  • Review and improve the Compose and parser prototypes
  • Define and refine the approach to widgets and application architecture for Dojo 2
  • Continue to review and land code for Core, Crypto, DOM, dstore, i18n, Loader, and Routing

We are also actively working on the following:

Core

package-template

parser

Over the last couple of months we’ve also been working on evaluating other projects out there to determine how they can benefit or inspire our efforts, or offer possible integration options. We’ve also been working on a reference application that we will be using to document and validate the APIs in Dojo 2. Work on these efforts will continue as we work to refine the vision and approach for Dojo 2.

Weekly IRC meeting

As usual, our weekly IRC meeting is on irc.freenode.net #dojo-meeting at 9am Pacific time on Tuesday.

View the Dojo weekly meeting logs

This week’s agenda

  • 1.11 release plan (we’re aiming for January for the release)
  • Discuss open 2.x challenges

Thanks!

The Dojo 2 loader, core, and dom are near an alpha state! Progress is being made on routing, crypto, i18, dstore, Compose and parser. Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate.

Dojo Recap – Week Ending December 4, 2015

Recently in Dojo 1.x

Recently we fixed the following issues in Dojo 1.x:

Dojo

Dijit

DojoX

util

themes

Up next in Dojo 1.x

We are starting to put together a release plan for 1.11, and updated point releases for earlier versions of Dojo. We have about 30 more issues to resolve, and then we’ll be ready for the 1.11 release! The main things we are considering for 1.11 are as follows:

Recently in Dojo 2

We’re making further progress on Dojo 2 as well. Recently our focus has been on Compose, core, and the package template:

Compose

parser

Ongoing discussion on consistency between parser objects and Compose objects and parser.watch() uses a callback versus synthetic events

core

dojo2-package-template

Upcoming Dojo 2 efforts

Here we’ve identified a few of our aspirations for near future. This week in Dojo 2, we have more code reviews to complete and pull requests to land. 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.

  • Review and improve the Compose and parser prototypes
  • Define and refine the approach to widgets and application architecture for Dojo 2
  • Continue to review and land code for Core, Crypto, DOM, dstore, i18n, Loader, and Routing

We have some old PRs out there that need updates and some other issues we’re working on, including:

Weekly IRC meeting

As usual, our weekly IRC meeting is on irc.freenode.net #dojo-meeting at 9am Pacific time on Tuesday.

View the Dojo weekly meeting logs

This week’s agenda

  • 1.11 release plan (we’re aiming for December or more likely January for the release)
  • Discuss open 2.x challenges

Thanks!

The Dojo 2 loader, core, and dom are roughly in an alpha state. Progress is being made on routing, crypto, i18, dstore, Compose and parser. Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate.

Dojo Recap – Week Ending November 20, 2015

Over the last few weeks we made fixes in the Dojo 1.x codebase towards the Dojo 1.11 release, and further progress towards Dojo 2. Let us know if you would like to get involved!

Recently in Dojo 1.x

Recently we fixed the following issues in Dojo 1.x:

Dojo

Dijit

DojoX

Up next in Dojo 1.x

We are starting to put together a release plan for 1.11, and updated point releases for earlier versions of Dojo. We have about 50 more issues to resolve, and then we’ll be ready for the 1.11 release! The main things we are considering for 1.11 are as follows:

Recently in Dojo 2

We’re making further progress on Dojo 2 as well:

Compose

parser

Ongoing discussion on consistency between parser objects and Compose objects and parser.watch() uses a callback versus synthetic events

core

dojo2-package-template

Upcoming Dojo 2 efforts

Here we’ve identified a few of our aspirations for near future. This week in Dojo 2, we have more code reviews to complete and pull requests to land. 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.

  • Review and improve the Compose and parser prototypes
  • Define and refine the approach to widgets and application architecture for Dojo 2
  • Continue to review and land code for Core, Crypto, DOM, dstore, i18n, Loader, and Routing

Over the last couple of months we’ve also been working on evaluating other projects out there to determine how they can benefit or inspire our efforts, or offer possible integration options. We’ve also been working on a reference application that we will be using to document and validate the APIs in Dojo 2. Work on these efforts will continue as we work to refine the vision and approach for Dojo 2.

Weekly IRC meeting

As usual, our weekly IRC meeting is on irc.freenode.net #dojo-meeting at 9am Pacific time on Tuesday.

View the Dojo weekly meeting logs

This week’s agenda

  • 1.11 release plan (we’re aiming for December or January for the release)
  • Discuss open 2.x challenges

Thanks!

The Dojo 2 loader, core, and dom are near an alpha state! Progress is being made on routing, crypto, i18, dstore, Compose and parser. Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate.