Blog

Oct 26

Exploring WebVR

By on October 26, 2016 12:12 pm

This October, we delivered meetup talks on WebVR in London and Phoenix on the same day to share our early efforts in exploring WebVR with TypeScript, Dojo 2, Intern, and A-Frame.

What is WebVR?

WebVR is an experimental JavaScript API that provides access to Virtual Reality (VR) devices, such as the Oculus Rift, HTC Vive, Samsung Gear VR, and¬†Google Cardboard. These VR devices are used with your web browser. Native browser support is currently limited to experimental releases of Chrome, Firefox, and Samsung Internet Browser for Gear VR. You can¬†also try it using shims that add support to today’s browsers. WebVR is not another graphics rendering engine, but instead adds APIs that support rendering VR scenes with WebGL in the¬†web browser’s Canvas.

Oct 7

SafetyNet 2016 recap

By on October 7, 2016 8:41 am

SafetyNet is an annual conference hosted by Pulsiam and is focused on trends in software for the safety industry. Because of our expertise in shaping the modern web and our ongoing work with Pulsiam’s application development efforts, I was invited to deliver a keynote about the past, present, and future of the web, as this industry begins to transition to web-based solutions.

Sep 29

Improving TypeScript modules

By on September 29, 2016 3:15 pm

improving typescript modules

One of the main challenges with creating modern JavaScript web applications is the relatively incomplete approach to ES modules. As an interim solution until all necessary use cases are solved, many developers create source code with ESM, and then transpile to either AMD, CJS, or UMD for easy usage within today’s browsers. As we work on creating Dojo 2 in a manner that is easy to use for both TypeScript and JavaScript users, one challenge we faced was how to support loader plugins and/or other dynamic module loading. AMD has long supported loader plugin syntax, and SystemJS supports loader plugins as well as System.import.

Aug 24

The long and winding road to Dojo 2

By on August 24, 2016 10:46 am

Recently on GitHub, someone accused Dojo 2 of being vapourware. This opinion came from a position of misinformation. I was glad the individual then engaged with the Dojo 2 project to understand where we are today. We are making swift progress and a beta is on the horizon. It has taken Dojo 2 a long time to get here and to really solidify our vision. We first started brainstorming about plans for 2.0 almost 5 years ago! Around a year ago we solidified our plans and have been unwavering in moving down that path.

Aug 19

Mixing Dojo widgets and Angular 2 components

By on August 19, 2016 9:10 am

Mixing Dojo widgets & Angular 2 components

We were recently asked about options for mixing Dojo widgets and Angular 2 components into the same application:

  • Is it possible to render an Angular 2 component and Dojo widgets on the same page?
  • Are there any special configuration settings needed?
  • What’s the best way for Angular 2 and Dojo to communicate and/or send messages?
  • What kind of complex challenges and communication issues should we be aware of?
  • For an application that assembles many different components, if some of these are are Dojo widgets and some are Angular 2 components, how can we get them to play nicely together?