Confirmed users
656
edits
No edit summary |
|||
| Line 90: | Line 90: | ||
[[File:Brackets-CSS-Lint.png|800px]] | [[File:Brackets-CSS-Lint.png|800px]] | ||
===Issues=== | |||
Brackets isn't fully supported yet in browsers. At the time of writing there is an [https://groups.google.com/forum/#!topic/brackets-dev/HR4lwxEKt6M experimental in-browser branch] that uses a node.js-websocket based backend to simulate the file system and other services. The resulting editor can be hosted in a web page, but is far from universally usable across various HTML5 browsers. Here is a screenshot of it running in WebKit (top) and Gecko (botom): | |||
[[File:Brackets-WebKit-vs-Gecko.png]] | |||
Making Brackets work cross-browser would be necessary, which would mean writing/adding shims for various WebKit-only dependent APIs (e.g., File System API), and dealing with <code>-webkit</code> prefixed CSS. The backend node server would also likely need work, and getting all this landed in master vs. as an experimental branch would be ideal. | |||
==Conclusion== | |||
In providing a platform for learning open web technology and development, Webmaker has to balance the need for simplicity at the beginning stage, and a gradual expansion of capability as learning progresses. The web is easy to start learning, but becomes more complex quickly. Expert developers know that one only manages such complexity with tools and augmented environments that make navigation, discovery, and validation possible. A successful learning strategy will not only include an ever increasing difficulty in lessons and examples, but also more powerful and advanced features in the learning environment. Providing these too early will mean learners are overwhelmed and distracted. Not providing them will mean that learning beyond the basics becomes more difficult. The progression from Thimble to Nimble could help ease the transition for learners and teachers without requiring a false dichotomy between simple vs. powerful. | |||