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: 19 hours 46 min ago

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

Case Study: Masternaut

Tue, 01/05/2016 - 21:00

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.

Q: Why did you choose Dojo?

A: As I’ve mentioned above, when choosing a toolkit or framework, it’s important that you can think about the future with some kind of confidence. For Masternaut, it was essential that we chose a framework that would evolve and would be maintained. So the community and roadmap are important indicators. Moreover, the modular approach Dojo provides is very important for us.

We have a vast number of users on all sorts of networks and devices. So for us a lightweight framework is essential. Dojo AMD gives us the ability to serve only the modules that are required. So no JavaScript code is sent to the client that is not required for that page.

Our product is built and sold as a modular system. Using AMD allows us to have a single application without bloating the packages that are downloaded by the client browser for our different users.

The last main reason why we choose Dojo is because it doesn’t prevent us from doing something the way we want to do it. You may encounter frameworks that make implementation of 90% of your application very fast, but finally to get the last 10% done, you’ll spend a lot more than 10% of time fighting against the framework. It’s not the case with Dojo because creating your own widgets or customizing some default behaviour is accessible and easily extensible, and the source code is understandable.

Q: Were you previously using another toolkit?

A: In the past I’ve used the Google Web Toolkit. That was a very interesting framework enabling you to produce JavaScript code based on written Java code. Debugging was possible with your favourite Java IDE and to finish it was possible to benefit from the Java contract patterns and its strong typing. So it was a quite powerful tool.

Within our application, we also leverage Google Maps, which is very easy to integrate within Dojo-based applications.

Q: What does your application or service do?

A: Masternaut is one of Europe’s largest providers of telematics solutions. We provide a full end to end solution for fleet management. Our Connect application provides everything from simple capability to track a vehicle on a map to bi-directional messaging with a field engineer, KPI indicators for managers on all aspects of fleet management (fuel consumption, vehicle utilisation, driver behaviour, CO2 emissions etc.) and comprehensive reporting suite.

Masternaut DashboardMasternaut Dashboard Masternaut Live PositionsMasternaut Live Positions Masternaut Vehicle AnalysisMasternaut Vehicle Analysis Q: How does your application use Dojo?

A: We are using the AMD syntax and features a lot now. We’ve created many custom widgets that we reuse when needed. For example, our custom date picker, vehicle selector uses Dojo’s Tree and inputs selector. Our application is using the MVC pattern however not the one provided by Dojo – this is a good example where Dojo is flexible and does not force us to adopt a pattern as Angular would.

Q: How did you implement your custom theme?

A: We’re using CSS inheritance. We begin with a default theme, and then depending on the customer that logs in, we layer a customer specific CSS on top of the default theme.

Q: Overall what is your experience with Dojo?

A: We’ve been using Dojo since the beginning of the life of our Connect application, since 2011. Overall, we’re happy with this toolkit and trying to upgrade our code every time a new Dojo release is available.

Q: What’s your favorite thing about Dojo?

A: The overall modularity and flexibility offered by Dojo is incredibly useful. I also like the smart pattern for implementing patches using a loader plugin, without touching the source code.

Q: What are your future plans with Dojo?

A: First of all, moving to Intern (all of our tests are currently using DOH – there are more than 22000 statements to move). Then will come the time to upgrade to Dojo 2!

Thanks!

Thanks Stéphane 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 December 18, 2015

Tue, 12/22/2015 - 18:18
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!

Categories: Open Source, RIA

Dojo Winter 2015-2016 Events

Tue, 12/15/2015 - 13:39

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

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

Categories: Open Source, RIA

Dojo Recap – Week Ending December 11, 2015

Tue, 12/15/2015 - 12:45
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.

Categories: Open Source, RIA

Dojo Recap – Week Ending December 4, 2015

Tue, 12/08/2015 - 21:07
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.

Categories: Open Source, RIA

Dojo Recap – Week Ending November 20, 2015

Sat, 11/28/2015 - 15:13

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.

Categories: Open Source, RIA

Dojo Recap – Week Ending October 23, 2015

Tue, 10/27/2015 - 04:55

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

Inital Compose prototype is ready for your review and feedback!

parser

Initial parser prototype is ready for your review and feedback!

Recently we have spent some of our time planning out a reference application for Dojo 2, as well as evaluating a variety of options and features which will help improve the overall approach to Dojo 2.

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 approach to widgets for Dojo 2!
  • Continue to review and land code for Core, Crypto, DOM, dstore, i18n, Loader, and Routing

Over the last couple of weeks, and this week, 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 November or December 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.

Categories: Open Source, RIA