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: 18 hours 14 min ago

Dojo Recap – Week Ending July 24, 2015

Mon, 07/27/2015 - 21:36

Last week we made a few fixes in the Dojo 1.x codebase, and further progress towards Dojo 2. Let us know if you would like to get involved!

Last week in Dojo 1.x

Last week we fixed the following issues in Dojo 1.x:

Dijit Util 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. The main things we are considering for 1.11 are as follows:

  • New flat theme
  • Update build profiles to include new themes repo
  • Update theme tester to include new flat theme
  • Update versions of Closure Compiler and Rhino
  • Look through all critical open issues and pull requests
Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core dstore loader i18n This week’s Dojo 2 efforts

Our efforts to complete Dojo 2 are ongoing every week. Here we’ve identified a few of our aspirations for the upcoming week. 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.

Core DOM
  • Address bugs, if any are reported
  • README updates
Routing Loader Crypto i18n dstore parser
  • Refine and update proposal
Weekly IRC meeting

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

Last week we discussed
  • Various open challenges
  • Dojo 1.11 flat theme efforts

View the Dojo weekly meeting logs

This week’s agenda
  • 1.11 release plan
  • Discuss open 2.x challenges
Thanks!

As stated last week, the Dojo 2 loader, core, and dom are near an alpha state! Progress is being made on routing, crypto, i18, dstore, class delcaration and parser. Each week we are making progress towards the Dojo 2 platform alpha release. 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 July 17, 2015

Mon, 07/20/2015 - 20:36

Last week we made a number of fixes in the Dojo 1.x codebase, and also some progress towards Dojo 2. Let us know if you would like to get involved!

Last week in Dojo 1.x

Last week we fixed a few issues with Dojo 1.x:

Dojo This week in Dojo 1.x

This week we continue to review and refine the flat theme for Dojo 1.11, and land additional stability fixes in preparation for the 1.11 release. We are also looking for help in making Closure faster in building Dojo

Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core dstore cryto loader i18n This week’s Dojo 2 efforts

Our efforts to complete Dojo 2 are ongoing every week. Here we’ve identified a few of our aspirations for the upcoming week. 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.

Core
  • Review and land open pull requests
  • Create dojo-bower organization and work on package management
  • Improve README for core and loader
Class declaration
  • Finish class declaration research
DOM
  • Address bugs, if any are reported
Routing
  • Review primary pull request and resolve loose ends in implementation
Loader Crypto i18n dstore parser
  • Refine and update proposal
Weekly IRC meeting

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

Last week we discussed
  • Various open challenges
  • Dojo 1.11 flat theme efforts

View the Dojo weekly meeting logs

This week’s agenda
  • 1.11 release plan
  • Discuss open challenges
Thanks!

Dojo 2 loader, core, and dom are near an alpha state! Progress is being made on routing, crypto, i18, dstore, class delcaration and parser. Our goal is to keep making progress towards an alpha for Dojo 2 platform. Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate efficiently!

Categories: Open Source, RIA

Dojo Recap – Week Ending July 10, 2015

Mon, 07/13/2015 - 15:00

Last week we made progress on several features for Dojo 2! Thanks for helping us get a few steps closer to Dojo 2, it would not be possible without your help. Let us know if you would like to get involved!

Last week in Dojo 1.x

Last week we fixed one issue with Dojo 1.x:

Dojo

This fix was an interesting one in that it was an issue when you had multiple aspect calls connected together, and then started removing them. We’re a little surprised that no one had reported this issue previously!

This week in Dojo 1.x

This week we continue to review and refine the flat theme for Dojo 1.11, and land additional stability fixes in preparation for the 1.11 release.

Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core dstore cryto loader This week’s Dojo 2 efforts

There are many things we have to do to complete Dojo 2. We’ve identified a few of our aspirations for the upcoming week towards making progress on Dojo 2. 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.

Core
  • Refine the release script
  • Create dojo-bower organization and work on package management
  • Improve README for core, dom, and loader
Class declaration
  • Further research various options
DOM
  • Address bugs, if any are reported
Routing
  • Review primary pull request and resolve loose ends in implementation
Loader
  • Continue development on functional tests for Loader
  • Refine the release scripts based on feedback
Crypto
  • Finish reviews and land the initial crypto API
i18n
  • Begin development efforts
dstore
  • Continue work on TypeScript conversion
parser
  • Refine and update proposal
Weekly IRC meeting

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

Last week we discussed
  • Various open challenges
  • Dojo 1.11 flat theme efforts
  • Possible change to the meeting time

View the Dojo weekly meeting logs

This week’s agenda
  • 1.11 release plan
  • Discuss open challenges
Thanks!

Thanks to everyone for their valuable contributions this past week, we’re continuing on our steady progress towards Dojo 2 platform alpha! Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate efficiently!

Categories: Open Source, RIA

Dojo Recap – Week Ending July 3, 2015

Mon, 07/06/2015 - 17:20

Last week we made progress on several features for Dojo 2! Thanks for helping us get a few steps closer to Dojo 2, it would not be possible without your help. Let us know if you would like to get involved!

Last week in Dojo 1.x

Last week a number of refinements and small bug fixes were made to Dojo, Dijit, and DojoX:

Dojo Dijit DojoX This week in Dojo 1.x

This week we hope to review and refine the flat theme for Dojo 1.11.

Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core dstore This week’s Dojo 2 efforts

There are many things we have to do to complete Dojo 2. We’ve identified a few of our aspirations for the upcoming week towards making progress on Dojo 2. 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.

Core
  • Refine the release script
  • Review open pull requests
  • Miscellaneous code clean-up and bug fixes as they arise
DOM
  • Address bugs, if any are reported
Routing
  • Resolve loose ends in implementation
Loader
  • Continue development on functional tests for Loader
  • Refine the release scripts based on feedback
Crypto
  • Finish reviews and land the initial crypto API
i18n
  • Begin development efforts
dstore
  • Work on TypeScript conversions
Weekly IRC meeting

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

Last week we discussed
  • Various open challenges
  • Current progress on platform packages

View the Dojo weekly meeting logs

This week’s agenda
  • Review Dojo 1.11 flat theme efforts
  • Discuss open challenges
Thanks!

Thanks to everyone for their valuable contributions this past week, we’re continuing on our steady progress towards Dojo 2 platform alpha! Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate efficiently!

Categories: Open Source, RIA

Dojo Recap – Week Ending June 26, 2015

Thu, 07/02/2015 - 17:29

With summer holidays and travel plans, progress is a bit slower this time of year, but we still continued making some progress last week on Dojo 2! Thanks for your help, we greatly appreciate it. Let us know if you would like to get involved!

Dojo 1.x

This past week we landed a few stability fixes to Dijit.

Progress was also made on the Dojo 1.11 flat theme.

Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core Loader
  • Further progress was made on the loader unit and functional tests, and a few small alpha releases were created to prepare loader for consumption by Dojo 2 core.
Routing
  • Initial base router pull request review is underway. We welcome and encourage feedback from everyone in the community, as we want this to be a highly useful router!
Crypto Parser

We met this week to discuss the parser and we agreed that the proposal will need a bit of an overhaul before we revisit this subject. We hope to have this revised and ready for community feedback again by mid-July.

dstore
  • An initial branch was set up to convert to TypeScript and start using Dojo 2 platform packages
This week’s Dojo 2 efforts

There are many things we have to do to complete Dojo 2. We’ve identified a few of our aspirations for the upcoming week towards making progress on Dojo 2. 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.

Due to the July 4th holiday and various summer vacations, we may be slower on progress over the next few weeks.

Core
  • Review open pull requests
  • Miscellaneous code clean-up and bug fixes as they arise
DOM
  • Address bugs, if any are reported
Routing Loader
  • Continue development on functional tests for Loader
  • Start work on bower scripts for loader and other Dojo 2 packages
Crypto
  • Finish reviews and merge the crypto API. This will unblock our ability to merge the completed provider work.
i18n
  • Create initial repo and plan initial development
dstore
  • Begin TypeScript conversion efforts
Parser
  • Work on updates to proposal
Weekly IRC meeting

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

Last week we discussed
  • Various open challenges
  • Current progress on platform packages

View the Dojo weekly meeting logs

This week’s agenda
  • Review Dojo 1.11 flat theme efforts
  • Discuss open challenges
Thanks!

Thanks to everyone for their valuable contributions this past week, we’re starting to see many things come together for Dojo 2 platform alpha! Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate efficiently!

Categories: Open Source, RIA

Dojo Recap – Week Ending June 19, 2015

Mon, 06/22/2015 - 15:36

Last week we made progress on several features for Dojo 2! Thanks for helping us get a few steps closer to Dojo 2, it would not be possible without your help. Let us know if you would like to get involved!

Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core Loader Routing Crypto This week’s Dojo 2 efforts

There are many things we have to do to complete Dojo 2. We’ve identified a few of our aspirations for the upcoming week towards making progress on Dojo 2. 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.

Core
  • Refine the release script
  • Review open pull requests
  • Miscellaneous code clean-up and bug fixes as they arise
DOM
  • Address bugs, if any are reported
Routing
  • Begin reviews on the router. If anyone in the community is strong with routing, we welcome their feedback on the initial pull request!
  • Routing proposal cleanup, as needed.
Loader
  • Continue development on functional tests for Loader
  • Refine the release scripts based on feedback
Crypto
  • Continue work on Hash and HMAC
i18n
  • Create initial repo and plan initial development
dstore
  • Set up branch to convert to TypeScript and start using Dojo 2 platform packages
Weekly IRC meeting

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

Last week we discussed
  • Various open challenges
  • Current progress on platform packages

View the Dojo weekly meeting logs

This week’s agenda
  • Review Dojo 1.11 flat theme efforts
  • Discuss open challenges
Thanks!

Thanks to everyone for their valuable contributions this past week, we’re starting to see many things come together for Dojo 2 platform alpha! Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate efficiently!

Categories: Open Source, RIA

Case Study: ApacheGUI

Wed, 06/17/2015 - 16:58

The large companies that use Dojo are widely known. This series features lesser known users of Dojo, and their stories. This time, we interview Jonathan Rossi of ApacheGUI, an open source, Java-based, Apache HTTP Server GUI.

ApacheGUI Control

Q: How did you first learn about Dojo?

A: I learned about Dojo from a co-worker who showed me a simple front end interface that was built to modify a data grid on the screen. The interface looked very professional and easy to use. It also had a lot of advanced components such as modifying the data on the grid and updating a back end database in real time without refreshing the page. My co-worker was not a front-end developer, however they managed to build a very professional front end widget with advanced front-end techniques. This got me interested in Dojo.

Q: Why did you choose Dojo?

A: I chose Dojo for two reasons:

  1. Dojo is built with an object oriented nature. All widgets are modelled as objects that can easily be extended to add custom functionality. I also like Dojo’s way of modelling classes over the vanilla JavaScript prototypical inheritance.
  2. Dojo supports a very vast set of widgets out of the box. Most of my day job is as a front-end developer, I understand how time consuming it can be to build UI widgets. Dojo is a toolkit with pre-built widgets that I can plug into my application. This saved me a lot of time in developing my application.
Q: Were you previously using another toolkit?

A: I have used jQuery UI in the past. I chose Dojo over jQuery UI due to the 2 reasons above.

Q: What does your application or service do?

A: My application provides a front end UI to manage the Apache HTTP server. The Apache HTTP server is still the most widely used http server on the internet. The application runs inside of a web browser with a desktop like interface.

Q: How does your application use Dojo?

A: Most of the front end UI is built with a set of Dojo Widgets. The code is also structured using the Dojo class declaration mechanism.

Q: Overall what is your experience with Dojo?

A: Dojo does have a steep learning curve. It is a toolkit that is really meant for seasoned developers that understand Object Oriented principles and how to simplify a large application into a collection of components. If you are this type of developer, then Dojo is a dream to use. In my opinion it is not meant for a new front-end developer who reads a set of simple online tutorials and would like to get a website up and running immediately.

Q: What are your future plans with Dojo?

A: I will continue to use Dojo in my application. There is nothing out there quite like Dojo so there is no reason to use another toolkit.

Screenshots of ApacheGUI

Additional screenshots are available via the ApacheGUI website.

Thanks!

Thanks Jonathan 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

Case Study: Everlaw

Wed, 06/17/2015 - 15:28

The large companies that use Dojo are widely known. This series features lesser known users of Dojo, and their stories. This time, we interview AJ Shankar, the CEO at Everlaw, a company dedicated to developing cutting-edge technologies that improve the practice of law.

Everlaw Analytics

Q: How did you first learn about Dojo?

A: Don’t remember! It’s one of the toolkits that keeps popping up.

Q: Why did you choose Dojo?

A: An early contractor suggested it. It provided more of a comprehensive infrastructure than frameworks like jQuery, which seem to do best when manipulating an existing DOM. We knew from the beginning that our site was going to be very rich, and we wanted a framework that would make programmatic UI construction easier.

Q: Were you previously using another toolkit?

A: Nope, we went with Dojo from the very beginning. I’ve used jQuery and Prototype in the past, and I find Dojo to occupy a happy middle ground between the two.

Q: What does your application or service do?

A: We help law firms sift through massive amounts of evidence to find the metaphorical “smoking gun” documents that make (or break) a case. There are a lot of interesting computer science problems here: search, data visualization, distributed systems, machine learning, databases, and more. But having a top-notch user experience is essential to expose lots of complex data in an understandable way.

Q: How does your application use Dojo?

A: In all kinds of ways! We used the AMD module system to manage the dozens of modules and tens of thousands of lines of JavaScript we have. We use Dijit extensively for our UI, including our own custom Dijit theme. We use the DOM, touch, and event subsystems for user interactions, the topic pub/sub system, various base modules for classes and language constructs, query for probing the DOM, and some helpful internationalization and normalization code. We’re also big fans of dojox/lang/functional!

Q: Overall what is your experience with Dojo?

A: We like that Dojo is robust in the way that many other frameworks are not: care has been put into a lot of the thornier issues (internationalization, scalability) that are easy to ignore at your own peril. I do think that documentation is lacking (especially for Dijit) when it comes to extending code, rather than just using it, so we do find ourselves plunging down the source-code rabbit hole quite often.

Q: What’s your favorite thing about Dojo?

A: It usually has what we need before we realize we need it! Many times we’ve needed to add some new functionality, only to discover that Dojo has a module that does it already.

Q: What are your future plans with Dojo?

A: We’re excited for 2.0! We’re in the process of migrating our code over to TypeScript, so we expect to use fewer of the lower-level language features, but otherwise we anticipate moving forward with Dojo for the foreseeable future.

Screenshots and videos of Everlaw

Everlaw Home

Everlaw Review

Everlaw Search

Thanks!

Thanks AJ 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

Case Study: Philips Healthcare

Tue, 06/16/2015 - 12:41

Philips Healthcare recently released a new version of their Intellispace Cardiovascular platform. Philips has been using Dojo for several year to create user interfaces for various medical devices that allow technicians to work with scans of patients, including cardiovascular scans, neural scans, and general MRIs.

In addition to using many of the standard Dojo and Dijit best practices, along with dgrid, dstore, and dojox/charting, Philips has created many custom widgets including this timeline view showing the various scans for a patient over time.

Cardiology Timeline

This is not the type of application that most Dojo users will see in their everyday lives, and definitely not something that you can visit via a traditional URL. But it does show off the power that Dojo provides for building a wide variety of powerful application. And the next time you need a medical scan, Dojo may be part of the system that helps display this important information to you and your medical professionals!

Using Dojo?

If you would like to share your experience with Dojo, please contact us.

Categories: Open Source, RIA

Dojo Recap – Week Ending June 12, 2015

Mon, 06/15/2015 - 16:32

Last week we finished several initial versions of features for Dojo 2! Thanks for helping us get a few steps closer to Dojo 2, it would not be possible without your help. Let us know if you would like to get involved!

Dojo 1.x

This past week work began on a new flat theme for Dojo 1.11. This is a work in progress, and will be completed in the near future.

Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we made progress completing initial alpha versions of several key features and packages:

Core DOM
  • Event delegation is complete!
  • A decision was made on geometry, placing this feature on hold until use cases are determined. If you have a strong use case for why this should be included in DOM, please let us know
  • The DOM package is now considered alpha complete!
Loader Crypto
  • Continued refining the proposed APIs for Hash and HMAC
This week’s Dojo 2 efforts

There are many things we have to do to complete Dojo 2. We’ve identified a few of our aspirations for the upcoming week towards making progress on Dojo 2. 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.

Core DOM
  • Address bugs, if any are reported
Routing
  • Continue development on Router
Loader
  • Continue development on functional tests for Loader
Crypto i18n
  • Create initial repo and plan initial development
dstore
  • Set up branch to convert to TypeScript and start using Dojo 2 platform packages
Weekly IRC meeting

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

Last week we discussed
  • a11yclick decision
  • dom/geometry
  • loader plugin API
  • i18n

View the Dojo weekly meeting logs

This week’s agenda
  • Review Dojo 1.11 flat theme efforts
  • Review completed DOM package
  • Discuss changes to crypto API
  • Discuss i18n
  • Discuss release process
  • Discuss open challenges
Thanks!

Thanks to everyone for their valuable contributions this past week, we’re starting to see many things come together for Dojo 2 platform alpha! Please let us know if you plan to work on any features, or would like to get involved!

Categories: Open Source, RIA

Dojo Summer 2015 Events

Thu, 06/11/2015 - 00:12

There are a number of Dojo events this summer. 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.

Meetups 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 June 5, 2015

Mon, 06/08/2015 - 21:22

We made a lot of progress towards Dojo 2 in the month of May, and continued this trend in the first week of June. Thanks for your contributions. Let us know if you would like to get involved!

Dojo 1.x

This past week we landed a few stability fixes to DojoX.

Improvements this week Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we accomplished many things including:

Core DOM Loader
  • Continue work on defining loader unit and functional tests
  • Stay synchronized with early Dojo 2 loader used by Intern, which added support for testing applications within the Electron environment which mixes Node and a WebKit environment together
Crypto
  • Refine the proposed APIs for Hash and HMAC
This week’s Dojo 2 goals

Here are a few of this week's aspirations towards making progress on Dojo 2!

Core

Our goals for Core this week include:

DOM
  • Finish event delegation and geometry
  • HTML DOM API will be considered code complete
Routing
  • Continue development on Router
Loader
  • Continue development on functional tests for Loader
  • Define the Loader plugin API
Crypto
  • Continue work on providers for Hash and HMAC.
i18n
  • Create initial repo and plan initial development.
Weekly IRC meeting

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

Last week we discussed
  • General community and contributor feedback to the Dojo 2 roadmap
This week’s agenda
  • As we are nearly code complete with an initial version of the Core package, we invite further discussion at this week's meeting
  • Discuss a11yclick decision
  • Discuss loader plugin API
  • Discuss i18n
  • Discuss how to start using and testing Dojo 2 features today
  • Discuss open challenges
  • General community and contributor feedback to the Dojo 2 roadmap
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you plan to work on any features, or would like to get involved!

Categories: Open Source, RIA

Case study: Softeco Sismat (TELL ME Project, #3)

Mon, 06/01/2015 - 19:45

The large companies that use Dojo are widely known. This series features lesser known users of Dojo, and their stories. One year ago, we conducted a case study about the TELL ME project with Stefano Bianchi from Softeco Sismat, an ICT Italian company, and a follow-up post four months ago. Here we have followed with up Stefano to get an update on their progress with Dojo.

Q: How did you first learn about Dojo?

A: We were looking for a solid JavaScript framework to develop a prototype for a complex, desktop-like web user interface (UI) to support learning activities for blue collar workers at the workplace. We evaluated several different renown frameworks and we found references to Dojo in several JavaScript framework evaluation tables – we then decided to give it a chance considering its features and the positive feedback. The experience made during the technical activities (development, testing, debugging etc.) and the feedback gathered from both developers and end users confirmed the general good impression we initially got.

Q: Why did you choose Dojo?

A: At a very first glance, Dojo seemed like a robust JavaScript framework for client-based desktop-like applications, shipped with several interesting built-in features (plenty of ready to use components and widgets, such as e.g. the Store-based Tree widget and the rich chart & graphing library). Also, the documentation (and tutorials, in particular!) was rather rich and complete, providing an incremental guide for differentiated (novice, intermediate and expert) users. The Asynchronous Module Definition (AMD) and Object Oriented (OO) approach was also a plus. As for our previous expertise in Rich Internet Application (RIA) development, what really convinced us to adopt Dojo was the possibility to replicate on client-side the same desktop-like functionality that we previously deployed with a Java-based RIA frameworks on server-side. As the project we are participating in also addresses mobile devices, the Dojo Mobile toolkit represented a valuable asset for future development. This case study focuses in particular on the development of a Mobile UI that we designed and implemented to port on smartphones some RIA functionalities we developed for plain web desktop UI, in order to provide a pervasive training experience and allow launching native multimodal apps on Android devices.

Q: What other tools have you integrated with Dojo?

A: This third case study focuses in particular on the revamp of the desktop and mobile User Interfaces (UI) for the TELL ME system, which followed the results and the users’ feedback collected during the first piloting and validation phase. The JavaScript business logic we implemented with Dojo was largely reused changing the presentation layer: in order to concentrate more on value-added functionality rather than on design, the graphical layout has been successfully adapted from DashGumFree, a great dashboard template based on Bootstrap and licensed under the Creative Commons Attribution 3.0 License by BlackTie. Furthermore, the fancy icons used to improve the visualization of information (e.g. the type of learning contents, as well as main commands/buttons) come from FontAwesome, the famous iconic font and CSS toolkit.

Thanks to Bootstrap, the UI now gently adapts to any device, from desktop PCs to tablets to smartphones, making the learning experience more pervasive and coherent than before. This approach allowed to avoid maintaining the two code bases initially developed with Dojo and Dojo Mobile, making a more effective use of CSS media queries to support mobile devices.

We initially considered also other valuable options (see the discussion on Dojo Toolkit and Bootstrap), such as Dojo for Bootstrap and dbootstrap, but we found more convenient to start adapting a nice, ready, fully adaptive template empowering the provided HTML example pages with Dojo’s features.

Each provided HTML example page was widgetized to leverage Dojo in making the UI fully interactiveEach provided HTML example page was widgetized to leverage Dojo in making the UI fully interactive Q: Were you previously using another toolkit?

A: In previous research projects, we extensively used several JavaScript libraries and frameworks – Prototype, Scriptaculous, jQuery, ExtJS to name a few. Working with Dojo represented for our Research & Innovation division a good opportunity to extend our expertise in JavaScript frameworks. All technical developments for the TELL ME learning content consumption UI (desktop and mobile) have been carried out with Dojo and Dojo Mobile from the very beginning. We found that is very easy and straightforward to use the Dojo Toolkit and use also third parties’ libraries, such as jQuery. We made an experimental page to play with several other interesting JavaScript libraries: meSpeak.js for client-side Text-To-Speech, jquery.qrcode.js for webcam-based QRCode recognition, and Cytoscape.js for complex graph visualization.

Q: What does your application or service do?

A: The prototype we developed for the front-end user interface of the TELL ME (Technology-Enhanced Learning Livinglab for Manufacturing Environments) system includes several different widgets (“chunks” of HTML5/JavaScript/CSS code that can be used independently or assembled in a portal/desktop-like layout) that provide different learning-oriented functionality. The main aim is to allow a blue collar worker to express a learning need (e.g. “what do I need to learn/be trained/recap about?”) by e.g. selecting a set of predefined tags from several complementary domain taxonomies (i.e. trees of concepts describing activities, tools etc. in a given workplace) and to receive back a learning path (i.e. a list of learning-oriented activities) including different learning contents to be consumed in order to acquire or improve specific working skills. Each type of learning content (documents, videos, pictures, lessons etc.) should be then consumed/launched in a specific widget, with the possibility to also provide social feedback such as ratings and comments. After developing the TELL ME web UI, we started designing and implementing a porting of the main functionality on mobile devices, to allow using the same REST WS back-end services and launch native apps on Android devices.

After developing the web UI, we started designing and implementing a porting of the main functionality on mobile devices, to allow using the same RESTful back-end web services and launch native apps on Android devices. Following the results of the first pilot and validation phase, anyway, we actually realized that end users were asking for a better user experience and that the maintenance of two separated code bases (one for the desktop version and one for the mobile version) was a bit too demanding for the economy of the project. We then decided to keep the business logic core part we already developed with Dojo and to refactor the presentation layer, moving a step forward with Dojo’s native templating mechanism. And it was a winning decision indeed…

Q: How does your application use Dojo?

A: The new version of the TELL ME system fully leverages the power of the Dojo Toolkit v1.10, greatly improving modularity and reusability of modules and component and UI responsiveness. All main tools and functionality have been widgetized according the toolkit native approach, which is soundly based on Progressive Enhancement (separation of concerns among presentation, structure and behaviour).

Page Structure

Any Dojo-based widget is defined by three different resources (an HTML file as a template, a CSS file for presentation, a JavaScript file for behaviour defined according to the Asynchronous Module Definition (AMD) API constraints). The modularization of code allowed to write JavaScript objects once and reuse them seamlessly throughout the UI, making visualization and behaviour much more maintainable and coherent than before: such a feature is definitively a plus when solutions must be changed/updated/upgraded on the fly during the evaluation and validation phases.

Moreover, answering one of the most pressing requests from end users, the whole UI has been internationalized to initially support 5 languages (English, Italian, Spanish, German, French). The Dojo i18n framework (multi-language support) can be easily and quickly extended (simply a matter of translating a configuration file!), so to e.g. allow easier testing in workshops and project demo sessions throughout Europe in the next months.
So far, the basic approach is based on retrieving information from the hosting HTML page through REST web services, instantiate widgets according to the data retrieved and then display/update information, leveraging HTML 5 Storage API.

Search

Q: Overall what is your user experience with Dojo?

A: After a two-years work with the Dojo Toolkit, we would like to summarize the lessons we learned for others who might be interested in giving Dojo a chance for their projects (some of these might sound obvious, but you never know):

  • Master JavaScript first! It’s not Dojo’s fault: 80% of our initial problems derived from knowing too little about ***real*** JavaScript – structures, scopes, AMD, RequireJS, etc. etc.;
  • Read tutorials and technical documentation first! This is something to recommend for any new framework or technology. Although you might be using 30% of what you read, it is always useful to know the complete set of “available tools/functionality”, as it might save precious time when addressing a new technical challenge (if only we read about Dojo XML Tools before… ;);
  • Climbing is a good training for running! Although other frameworks might be faster to learn and to release mock-ups / prototypes, Dojo pays you back for your initial effort as soon as you start mastering its native mechanisms. We heard a lot of comments such as “Why is Dojo that complicated?”, but then when we showed results people finally admitted “Mmmh, that deserves a look, uh?”.
  • Go for Widgets as soon as possible! This was indeed an error made at the very beginning: we got lost in playing with HTML directly, whereas the use of Widgets (and associated templates) would have saved a lot of efforts in code refactoring/maintenance. Using Widget allows to reuse code consistently all over your project, to always present stuff in the same way all over your UI and to build upon the large, powerful set of native Dojo Widgets (yes, your widget can include widgets, that can include widgets, that can…);
  • Experiment, have fun, contribute! As long as you proceed with development, it is possible to immediately play with Dojo in jsFiddle, for example, and share code, examples, ideas etc. etc.

    Q: What’s your favorite thing about Dojo?

    A: Dojo architecture is truly inspiring when approaching Object Oriented (OO) JavaScript, and the rich set of examples provided help understanding how to make JavaScript code modular and reusable throughout the application – the whole approach is clear, clean and scalable. Reference documentation and tutorials are also a valuable resource. The design we followed for the implementation of the desktop UI was useful also for the mobile version as several JavaScript modules were easily reused allowing to link immediately the new presentation layer with the existing REST web services business layer. If a vote must be expressed now for a really outstanding feature, no doubts: Widgets, and the possibility to build custom Widgets on top of (that is, assembling several set of) native Widgets.

    Leveraging the power to compose Widgets out of Widget and native components.Leveraging the power to compose Widgets out of Widget and native components. Q: What are your future plans with Dojo?

    A: After a first technical evaluation phase, where end-users tested the developed applications, we are now entering the final piloting phase, and the revamped UI will undergo a careful usability evaluation by end users. Results will be used for further fine-tuning of the solutions implemented.
    Moreover, we would like to study better and experiment with several features of Dojo: native configuration mechanism, builds, Data Modelling for MVC Applications (we know use a lot HTML 5 Storage API), Deferred and Promises (we already used it, but probably at 20% of its power…) etc. etc.

    We moved to Dojo 1.10, but we are definitively eager to start playing with Dojo 2.0 as soon as possible!

    TELL ME UI has been completely revamped!TELL ME UI has been completely revamped! TELL ME UI now leverages native DOJO i18n & l10n supportTELL ME UI now leverages native DOJO i18n & l10n support The Bootstrap-based DASHGUM template seamlessly adapts to any device, making the experience mobile and pervasive.The Bootstrap-based DASHGUM template seamlessly adapts to any device, making the experience mobile and pervasive. The new TELL ME UI immediately brings the trainee (i.e. the Blue Collar Worker, BCW) in the middle of learning-by-doing experiences, proposing the list of learning mixes that training/process managers have assigned to cover specific knowledge gaps, including metadata (e.g. tags), information on deadlines, and feedback of progress.The new TELL ME UI immediately brings the trainee (i.e. the Blue Collar Worker, BCW) in the middle of learning-by-doing experiences, proposing the list of learning mixes that training/process managers have assigned to cover specific knowledge gaps, including metadata (e.g. tags), information on deadlines, and feedback of progress. The visualization of proposed/assigned learning mixes leverage modern approaches such as the depicted timeline overview, which allows the BCW to quickly glance at the included contents. Visual feedback on learning contents that have been already consumed is provided as green check marks, as well as commands to (re)play, rate/comment the content, more info. The timeline view is based on a nice DOJO widget template, to put any ordered information in this modality with minimal effort.The visualization of proposed/assigned learning mixes leverage modern approaches such as the depicted timeline overview, which allows the BCW to quickly glance at the included contents. Visual feedback on learning contents that have been already consumed is provided as green check marks, as well as commands to (re)play, rate/comment the content, more info. The timeline view is based on a nice DOJO widget template, to put any ordered information in this modality with minimal effort. All functionality included in the previous prototypes – such as the search facilities based on the selection of tags from specific domain taxonomies, which leverage on Dojo’s TreeStore and Tree widgets – have been revamped and seamlessly ported to the new layout, properly leveraging its modularity and responsiveness.All functionality included in the previous prototypes – such as the search facilities based on the selection of tags from specific domain taxonomies, which leverage on Dojo’s TreeStore and Tree widgets – have been revamped and seamlessly ported to the new layout, properly leveraging its modularity and responsiveness. One of the main advancements in the new prototypes is the learning mix viewer (=“player”), which greatly simplifies the consumption of the learning contents proposed by the system to the BCW. One of the main advancements in the new prototypes is the learning mix viewer (=“player”), which greatly simplifies the consumption of the learning contents proposed by the system to the BCW. SCORM packages are now usable as the included imsmanifest.xml file is parsed to generate a simple web viewer, thanks to the powerful DojoX XML Utilities.SCORM packages are now usable as the included imsmanifest.xml file is parsed to generate a simple web viewer, thanks to the powerful DojoX XML Utilities. About TELL ME

    TELL ME (Technology-Enhanced Learning Livinglab for Manufacturing Environments) is a research project co-funded by the European Commission to improve training in small and medium-sized manufacturing environments by using the latest technologies and insights. The aim is to bring innovative learning methods to manufacturers so they can better supply the needs of their markets, which include larger industries. TELL ME is a three-year project that started in November 2012 with a partnership of 14 leading organisations in academic research, technology and industry from Italy, the UK, Finland, Sweden, France, Germany, Spain and Portugal. It is a significant €8.3m R&D project, funded by the Consortium Partners and a €5.9m research grant from the European Commission under its FP7 Framework Programme.

    Thanks!

    Thanks Stefano 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 May 29, 2015

Mon, 06/01/2015 - 18:22

We continued making progress towards Dojo 2 last week, thanks for your contributions. Let us know if you would like to get involved!

Dojo 1.x

This past week we landed a few stability fixes to Dojo and Dijit.

Improvements this week Last week in Dojo 2

Our current focus is on the packages in Dojo 2 platform. Last week we accomplished a many things including:

Core DOM Loader

Work on functional tests was started

Crypto This week’s Dojo 2 goals

Here are a few of this week's aspirations towards making progress on Dojo 2!

Core

Our goals for Core this week include:

  • Finish documentation and remaining code reviews
  • Finish initial development. (excluding features on hold: Set, WeakSet, and Reflect)
  • This includes: Encoding, Request, Map shim, and Readme updates
  • Finish initial development
DOM
  • Finish event delegation
  • Begin working on Geometry
  • Decide on a direction for Dojo 2’s version of a11yclick
Routing
  • Continue development on Router
Loader
  • Continue development on functional tests for Loader
Crypto
  • Finish work on Hash and HMAC APIs.
  • Begin work on providers for Hash and HMAC.
Weekly IRC meeting

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

Last week we discussed
  • Discuss code in core repository
  • General community and contributor feedback to the Dojo 2 roadmap
This week’s agenda
  • As we are nearly code complete with an initial version of the Core package, we invite further discussion at this week's meeting:
  • Discuss code in core repository
  • Discuss code in dom repository
  • General community and contributor feedback to the Dojo 2 roadmap
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you plan to work on any features, or would like to get involved!

Categories: Open Source, RIA

Dojo Recap – Week Ending May 22, 2015

Tue, 05/26/2015 - 16:33

Last week we made even more progress on Dojo 2 platform. Thanks for your contributions. Let us know if you would like to get involved!

Last week in Dojo 2

Last week we accomplished a number of things with Dojo 2 platform:

Core DOM

Basic DOM operations and CSS class manipulation APIs are complete!

Routing

Initial development efforts started.

Loader

We drafted some proposed functional test scenarios

This week’s Dojo 2 goals

Here are a few of this week's aspirations towards making progress on Dojo 2!

Core

Our goals for Core this week are to finish what we started last week:

  • Finish initial development. (excluding features on hold: Set, WeakSet, and Reflect)
  • This includes: Encoding, Request, Date Features, String shims, Map shim, and Readme updates
  • Finish initial development
  • This includes: Seekable Reader, Canned Streams, Iterable Interface, Readme updates, tutorials
  • Finish documentation and code reviews
DOM
  • Forms
  • Style Manipulation and Stylesheet Injections
Routing
  • Continue development on Router
Crypto
  • Setup repository
  • Begin development
Weekly IRC meeting

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

Last week we discussed
  • Discuss code in core repository
  • General community and contributor feedback to the Dojo 2 roadmap
This week’s agenda
  • As we are nearly code complete with an initial version of the Core package, we invite further discussion at this week's meeting:
  • Discuss code in core repository
  • General community and contributor feedback to the Dojo 2 roadmap
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you plan to work on any features, or would like to get involved!

Categories: Open Source, RIA

Dojo Recap – Week Ending May 15, 2015

Mon, 05/18/2015 - 20:45

Last week we completed some issues with Dojo 1.x and made more progress on Dojo 2 platform. Thanks for your contributions. Let us know if you would like to get involved!

Dojo 1.x

We continue making small updates towards a Dojo 1.11 release, as well as backporting relevant bug fixes. The 1.11 release is planned as soon as work is completed on a modern flat theme. This past week we landed a few fixes to Dojo and Dijit.

Improvements this week Last week in Dojo 2

Last week we accomplished a number of things with Dojo 2 platform:

Core DOM

Initial repository created. Initial work on basic DOM operations. dom.byId and dom.place are pending code review

Routing

Initial repository created.

Class Declaration Decision

As of May 13, 2015, our original proposal submitted to TypeScript was not accepted so we researched options that would cover Dojo 2’s needs for class declaration.

We have decided to proceed without language-level support of mixins and provide decorators to help accomplish what we need. Given that this solution is the least dependent on third-party interaction, we are choosing to explore it first. With what we know about decorators, we may be able to get exactly what we need from TypeScript. While we do not yet know for sure if this is the final solution, it is promising and something we can start working on today and then explore other options if it fails or if it is a burden to use.

This week’s Dojo 2 goals

Here are a few of this week's aspirations towards making progress on Dojo 2!

Core
  • Finish initial development. (excluding features on hold: Set, WeakSet, and Reflect)
  • This includes: Encoding, Request, Date Features, String shims, Map shim, and Readme updates
  • Finish initial development
  • This includes: Seekable Reader, Canned Streams, Iterable Interface, Readme updates, tutorials
  • Finish documentation and code reviews
DOM
  • Basic DOM access/manipulation APIs functional
  • CSS class manipulation APIs
Routing
  • Begin development on Router
Loader
  • Setup repository
  • Draft functional test scenarios
Weekly IRC meeting

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

Last week we discussed
  • Discuss code in core repository
  • General community and contributor feedback to the Dojo 2 roadmap
This week’s agenda
  • As we are nearly code complete with an initial version of the Core package, we invite further discussion at this week's meeting:
  • Discuss code in core repository
  • General community and contributor feedback to the Dojo 2 roadmap
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you plan to work on any features, or would like to get involved!

Categories: Open Source, RIA

Dojo Recap – Week Ending May 8, 2015

Tue, 05/12/2015 - 18:53
Another exciting week is underway in the Dojo camp! Dojo 1.x

In preparation for the 1.11 release planned for late Spring, we are landing high quality pull requests to fix various bugs and add enhancements to the dojo, dijit, and dojox packages.

Improvements this week Last week in Dojo 2

Initial Dojo 2 core repository is now public

In the intial core repository, you will find initial efforts in the repo for:

  • async
  • Promise
  • has
  • streams
  • WeakMap
  • decorators
  • lang
  • math
  • number
  • object observation
  • string shims
  • task queuing
Class Declaration

We've run into a small roadblock with our proposal for traits or mixins in TypeScript, so we are evaluating our options.

Style Guide

We have an updated and exhaustive Dojo 2 style guide available. Please follow these guidelines when contributing to Dojo 2.

This week’s Dojo 2 goals

Here are a few of this week's aspirations!

  • Verify all code conforms to Dojo 2 style guide
  • Further core development efforts including Encoding, Request, Events, Batch Processing, Date Features and streams (Transformers, Seekable Reader, Canned Streams, Iterable Interface)
  • Begin dom/html and history/routing development efforts
  • Refine proposals and readmes
Weekly IRC meeting

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

Last week we discussed
  • General community and contributor feedback to the Dojo 2 roadmap
This week’s agenda
  • Discuss code in core repository
  • General community and contributor feedback to the Dojo 2 roadmap
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you’d like to help out too!

Categories: Open Source, RIA

Dojo Recap – Week Ending April 30, 2015

Mon, 05/04/2015 - 20:28
Another exciting week is underway in the Dojo camp! Dojo 1.x

In preparation for the 1.11 release planned for late Spring, we are landing high quality pull requests to fix various bugs and add enhancements to the dojo, dijit, and dojox packages.

Improvements this week Last week in Dojo 2

This week we have some exciting updates to share with you on the planning and development progress of Dojo 2!

First off, we updated the Dojo 2 Roadmap to reflect the changes that took place this week. These changes include:

  1. The collection of packages we were calling "Dojo 2 Core" has been renamed to "Dojo 2 Platform" to prevent any confusion with the core package.
  2. The package combination that we outlined in last week's blog post was completed this week and the package status section of the Roadmap reflects this new package structure.
Browser support decision

We made the decision support IE9 through the launch of Dojo 2. While there are undoubtedly some pain points with supporting IE9, we believe that the effort to support it is not substantially greater than IE11. We also wanted to ensure that Dojo 2 launched with a core that would be compatible with Intern, which needs to be able to test a wide range of modern browsers. If the effort to support IE9 becomes too great, we reserve the right to amend this decision!

In other Browser Support news, we also decided to support Android Browser 4.3+. We discovered that this is the cutoff point for Android market share and that it was the most logical point for Dojo 2 to begin support for Android versions.

As we stated last week, please note that while the platform packages will support a more conservative list of browsers, widgets and other features on top of the platform packages may choose to support only more modern browsers.

Dojo 2's current Browser Support is:
  • Firefox latest and recent versions
  • Chrome latest and recent versions (desktop and mobile)
  • Safari 7+ (desktop and mobile)
  • IE 9, 10, 11
  • Microsoft Edge
  • Android 4.3 and 4.4
TypeScript compiler improvements

We are conducting research this week on compiler improvements to determine the needs of the project and best approach. We will keep you apprised of our findings as we figure things out!

This week’s Dojo 2 goals

With many of the ops kinks worked out, we hope to begin making good progress on package development this week. Here are a few of this week's aspirations!

  • Make initial efforts on the Dojo 2 core package available via GitHub
  • Core development efforts including:
  • stream: Node stream adapter implemented and tests written along with Transformer unit tests
  • platform shims: String, Map, Set, and maybe WeakMap
  • Object copying, task queuing, property observation, and date handling
Weekly IRC meeting

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

Last week we discussed
  • Core package consolidation: Discussion of included modules & approach
  • Dojo 2 Browser Support Decision: feedback received to make decision
  • General community and contributor feedback to the Dojo 2 roadmap
  • Any pressing issues with 1.x
This week’s agenda
  • General community and contributor feedback to the Dojo 2 roadmap
  • Any pressing issues with 1.x
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you’d like to help out too!

Categories: Open Source, RIA

Dojo Recap – Week Ending April 24, 2015

Mon, 04/27/2015 - 23:50
Weekly Update

A lot goes on in Dojo each week and in the past we haven’t done a great job of telling the world about it. As we begin this new chapter (working towards Dojo 2), we will be publishing a weekly update that gives some insight into what was accomplished the previous week, our goals for this week (in case you want to get involved), and a brief agenda for the weekly IRC meeting.

Dojo 1.x

In preparation for the 1.11 release planned for late Spring, we are landing high quality pull requests to fix various bugs and add enhancements to the dojo, dijit, and dojox packages.

Improvements this week
  • Fix for dijit Tree node rename when textDir is auto (#18543)
  • Convert LocalStorageProvider to AMD (#18565)
  • Add Basque language support (#18560)
  • Fix reconnect options for dojox/socket (#17761)
  • Fix RangeSlider callback notifcations (#18381)
Last week in Dojo 2 Package Template Updates

We are using this package template as the starting point for creating the Dojo 2 packages. Key changes to it were to enable TypeScript build and testing support for both atom-typescript and the included Grunt task, as well as support for a new combined CJS+AMD module format that supports both CJS and AMD in an exported module, but does not export a global like UMD. The main benefit of this is to prevent the need to compile all code twice for Node.js/io.js and browser usage of modules.

Package combination discussion

We discussed whether it truly makes sense for each package to be delineated as described on the Dojo 2 roadmap. The challenge is that some of these packages are dependent on each other, and to make them truly stand-alone in all cases may require a lightweight version of the API in one place, and then a duplicate but more complete implementation in a child package. This would be fine if they were large packages, but some of these packages are not expected to be very large. Some of these packages cannot easily be stand-alone without a shim when native capabilities aren’t available.

The current plan for each package is:
  • loader: remains stand-alone package
  • platform: combine with core
  • async: combine with core
  • stream: combine with core
  • io: combine HTTP client with core, leave remainder as stand-alone package
  • core: remains stand-alone, add core events, io, async, platform, and perhaps stream
  • dom/html: remains stand-alone, add DOM events
  • i18n: remains stand-alone
  • dstore: remains stand-alone
  • parser: remains stand-alone, in the future it may make sense to combine with dom/html
  • history/routing: remains stand-alone
  • crypto: remains stand-alone
  • events: split into core events and DOM events and merge into respective core and dom packages

These decisions may change as get further along and revisit our options, but for now, we want to find a good balance between separate packages and ease of development experience.

This week’s Dojo 2 goals Publish initial packages

We are working on getting the repositories in shape so that we can open them up to the community to start contributing!

Core package
  • platform: We expect to have some initial shims complete, and some work on polyfills.
  • async: pre-alpha implementation
  • streams: pre-alpha implementation of readable streams, progress on writable streams.
  • object copying: pre-alpha implementation
  • string functions: pre-alpha implementation
  • comparison: pre-alpha implementation
TypeScript compiler improvements

To improve the developer workflow, we will be making improvements to the TypeScript compiler.

These improvements include
  • Allowing the configuration of modules that should (or should not) emit JavaScript
  • Source map generator should be configurable to inline the TS content into the source maps rather than having to keep separate files
  • tsconfig.json should allow globbing
Browser support decision

We are currently discussing which minimum version of IE and browsers for Android we should support. For IE, we are deciding between IE9 and IE11. The popular decision is to start with IE11, but some dependencies such as Intern prefer having a core that is more widely compatible, if the effort to support IE9 for core is not substantially greater than IE11.

Similarly, we are analyzing current Android market share and effort to support Android versions to determine what the earliest version of either Android browser or Chrome for Android that Dojo 2 should officially support. It is worth noting that the core packages may support a more conservative list of browsers, whereas the widgets and other features on top of them may choose to support only more modern browsers.

Weekly IRC meeting

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

Last week we discussed
  • Why TypeScript was selected
    • interfaces, export to AMD/CJS/ES2015, typing, and an extensible compiler
  • Current status of class declaration and multiple inheritance with TypeScript
  • ES 2015 module syntax
  • GFX/charting and widgets in the Dojo 2 story
    • Not yet defined, but expected to be their own top level packages
  • Why crypto is a separate top level package
    • To make it easy to remove
  • New website feedback
  • Current status of 1.11
    • Waiting on flat theme work to be completed before finalizing the release plan
This week’s agenda
  • Core package consolidation: Discussion of included modules & approach
  • Dojo 2 Browser Support Decision
  • General community and contributor feedback to the Dojo 2 roadmap
  • Any pressing issues with 1.x
Thanks!

Thanks to everyone for their valuable contributions this past week! Please let us know if you’d like to help out too!

Categories: Open Source, RIA

The Road to Dojo 2

Thu, 04/16/2015 - 21:42

“When will Dojo 2 be released?” That’s pretty much the number one question we’ve been asked about Dojo since Dojo 1.0 was released in 2007. Over the past seven plus years, we have made numerous updates and improvements, while preserving a high level of stability for our users.

What’s in a number?

Our shift to AMD in Dojo 1.7 was a massive change that could have been called Dojo 2.0, but because we kept backwards compatibility to help developers transition over to AMD syntax, it felt right to call it 1.7. We continued building on that groundwork releasing 1.8, 1.9 and 1.10!

What should Dojo 2 do?

We have spent many months collecting thoughts and ideas from our users as well as reviewing the current and near future state of the web, to decide what Dojo 2 should and should not do.

Moving to the next major version number is an opportunity for us to assess our strengths and weaknesses, and to formulate a vision for 2.0.

The Roadmap

We’ve added a new section to our (brand new!) site, the Dojo 2 Roadmap. On the roadmap you will find a proposal for each of the planned Dojo 2 core packages. We will continue to update the Roadmap as we progress through the various phases of development for Dojo 2.

Get Involved!

We are very interested in community feedback on the package proposals. Some of the proposals are very polished, and others are less complete and noted as such. If you are interested, now is the time to take a deep look at these proposals!

We plan to discuss packages at each of the upcoming Dojo weekly meetings, IRC, 9am Pacific time on Tuesdays, irc.freenode.net, #dojo-meeting. For April 21st, we will start with the loader and platform packages. If you cannot make the meeting, or have feedback you want to provide prior to then about a specific package, please leave comments within each package proposal document found in the roadmap. We don’t want to lose your feedback, so the best place to offer that feedback is within the proposal documents.

On Widgets…

The roadmap currently excludes Dijit and other user interface elements, as we’re aiming to get core planning finalized and development underway, and then determine the path forward for user interfaces and widgets. The team at IBM has been working in parallel on an effort called Delite and Deliteful, and we hope that we will be able to efficiently align efforts in the near future.

Thanks!

We look forward to working together to release Dojo 2 in the near future. Thank you for your ongoing support and interest!

Categories: Open Source, RIA