11

We are using Dojo (1.9.3) as a JS framework for building a single page application. We are however spending too much time on the quirks of Dojo, so even simple tasks take a long time to implement. And since there is lack of proper documentation, we often have to resort to reading the source code and then implementing a workaround.

I feel that we would speed up development, and make it easier to maintain the code if we moved to some other framework. Our codebase is rather large, since it is a complex application, so we do not have time to re-write the whole thing at once. I was therefore hoping that it might be possible to combine Dojo with some other framework, so that we can move away from Dojo incrementally. I have only dabbled with these other framework in my spare time, and only wrote some small example apps, so I do not feel that I can really say whether or not they would play well with another framework, so I'm hoping that some of you out there can.

The frameworks I've been looking into - in the order of what I'd prefer based on my short investigation, but feel free to convince me otherwise.

  1. Ember
  2. React
  3. Polymer
  4. Angular (last due to me being scared of the major 2.0 overhaul)

While the main question is whether or not it is possible, please also advice on if you think it is a bad idea to do so.

mflodin
  • 1,093
  • 1
  • 12
  • 22

2 Answers2

10

The most I can say from the Dojo end of things is that Dojo itself is a toolkit, not a framework per se, and thus generally should not interfere with other scripts or frameworks. The reverse, on the other hand, can't always be said. So while I can't speak for all of the choices in your list, I do not think that Dojo itself will get in your way.

One possible exception I can think of is if any of the frameworks in question augment native prototypes, particularly Object, since that will affect enumerable properties in all objects and can wreak havoc on any scripts that use for...in loops without hasOwnProperty.

The only other exception I can think of is whether any of the frameworks in question for some reason do not coexist well with an AMD module loader.

That being said, I would also advise you to take the "promise" of frameworks with a grain of salt - you say that right now you are finding that implementing things with Dojo takes effort, and naturally the frameworks you list are attractive because they make certain parts of application development easy by offering patterns and conventions - but the question you should ask is, how hard does your framework make your job the moment you need to do something outside or against those conventions? Dojo may have a learning curve, but it generally doesn't prevent you from doing anything.

Ken Franqueiro
  • 10,559
  • 2
  • 23
  • 40
  • 1
    Thanks for your input. Regarding the "promise" of other frameworks: I just feel that finding info or help on how to do stuff when you get stuck rather hard with Dojo, and since the other frameworks are a lot more popular I expect it to be easier with them. – mflodin Dec 22 '14 at 15:37
  • 3
    You should try Dojo's mailing list, #dojo on irc.freenode.net, or this SO tag more often :D – Ken Franqueiro Dec 22 '14 at 22:46
6

You can use them together, but it also depends on what you're trying to do. Some actions might take more time for integration than others.

Dijit

I only have experience with Ember.js and AngularJS, but a common concept in these frameworks is data binding. Data binding allows you to simply update the model and the view will reflect the changes in the model.
However, these usually do not work nicely with widgets. Widgets (like the Dijit library) create their own DOM and because of it, frameworks like Ember.js or AngularJS are not "aware" of these changes and cannot update the view in that case.

To make it work, you will have to wrap your widgets into components (Ember.js) or directives (AngularJS). An example of such wrapping can be found in this answer.

Dependency loading

Dependency loading might be confusing. AngularJS comes with their own dependency injection system, and means that you will have to use the Dojo AMD loader for Dojo modules and AngularJS dependency injection for AngularJS. The two work nicely together as far as I know (I've seen examples with the RequireJS AMD loader, so it should be possible).

With Ember.js I had a bit more troubles integrating with the AMD loader. The creator of Ember.js (Tom Dale) does not believe in AMD, and I've seen several issues trying to load Ember.js components with an AMD loader.

It all depends on how you wish to use these frameworks and what extra effort you want to make. To me it looks like you're not even sure what to use these frameworks for, since React.js or Polymer has a completely different purpose than AngularJS or Ember.js for example.

Community
  • 1
  • 1
g00glen00b
  • 41,995
  • 13
  • 95
  • 133
  • Thanks for your input. Yes I agree that React and Polymer is different from Angular and Ember, in that they rather offer a way to make components, and I am not sure which way we want to go yet. But I felt a first step was to check if it was even possible to do so. – mflodin Dec 22 '14 at 15:40
  • This a good answer. The difficulty of integrating Dijit widgets into Angular databinding scenarios is definitely a real source of frustration. In terms of using Angular with the AMD, or other module formats, it's actually quite workable depending on how you structure your application. The key is to NOT register directives, services, etc with ```angular.module('app').service(...)``` at their definition site, but rather to define them as modules. Then you only need to worry about the global nature of angular in a few places, and your code will be cleaner and more portable as a bonus. – Aluan Haddad Nov 24 '15 at 05:08