Comments (4)
Ben is right in his comment: #21 (comment) The dojo modules and their locations has significantly changed from 1.6 to 1.7.
We'll have to be careful that we don't break compatibility with dojo 1.6, or else we'll have to declare that wire 0.x+ requires dojo 1.7.
from wire.
hence my comment that it's more like supporting 2 libraries rather than 2 versions of the same library. in my opinion, they're not nearly compatible enough to support both as "dojo". you'd need to have specific "dojo16" plugins for just dojo 1.6 and then i'd suggest "dojo" would be for dojo 1.7+ or as @unscriptable says - declare that dojo 1.7 is the minimum you support.
from wire.
That sounds good to me. I like the idea of providing dojo 1.6 and dojo 1.7 variants of the current wire/dojo/* plugins. We can let people know that all new dojo plugin dev will be for 1.7+. We can probably copy the existing plugins to a "wire/dojo16" dir, and then dojo 1.6 users can configure their loader to point wire/dojo to wire/dojo16 and not have to modify any of their wire specs.
from wire.
I'm scheduling this for v0.9.0 for now. I'm not sure if we'll make it, but we'll try. If not, we'll include it in a v0.9.1 release
from wire.
Related Issues (20)
- wire/builder/cram interprets any property called "create" as a factory HOT 1
- duplicate wire/dom wire/dom HOT 1
- Wire does not work with 'when' 3.0.0. HOT 3
- Empty `create: {}` should cause a loud error
- Add when 3.0 compat HOT 6
- Context Usage HOT 5
- BDD + CujoJS HOT 5
- wire/builder/cram should call require.toUrl() before fetching modules HOT 1
- 'import' a context into another HOT 4
- Allow import of a context-spec into another. HOT 5
- Remove artificial dot traversal limit HOT 2
- Container Compilation? HOT 1
- wirejs and dojo using the dojo build system seems impossible
- AOP plugin causing potentially unhandled rejections HOT 2
- Using properties or methods of other modules or components as components
- Using components from child and sibling contexts
- create factory should invoke function with context if module is a method of an object
- Dependencies when destroying a context?
- Bundling with Webpack doesn't work well HOT 3
- Not es6 ready - does not work with es6 classes HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wire.