SenchaCon 2016: Being Productive with the New Sencha Fiddle - Mitchell Simoens
•Télécharger en tant que PPTX, PDF•
0 j'aime•309 vues
Would you like to share code or quickly test some code? Before Sencha Fiddle, there was no good way to quickly run Ext JS code. Since its launch, Sencha Fiddle has changed the way we save code in the cloud and share it. In this session, you'll learn what Fiddle is, its new features, and how you can use it to be more productive.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à SenchaCon 2016: Being Productive with the New Sencha Fiddle - Mitchell Simoens
Similaire à SenchaCon 2016: Being Productive with the New Sencha Fiddle - Mitchell Simoens (20)
Plus de Sencha
Plus de Sencha (20)
Dernier
Dernier (20)
SenchaCon 2016: Being Productive with the New Sencha Fiddle - Mitchell Simoens
- 1. Being Productive with the new Sencha Fiddle Mitchell Simoens Senior Software Engineer, Sencha mitch@sencha.com @LikelyMitch
- 3. The Old “Fiddle” Sites Good for what they do, not great for Sencha. Aim to be library/framework agnostic code snippets. • No Sencha knowledge. - No updated framework catalog. - No understanding of Cmd packages. - Little to no access to our CDN. • Only one CSS, one JavaScript, and one HTML snippet. • No mock data functionality. • No searching!
- 4. What We Were Doing • Bugs checked into git. - Was very slow, took a while to get merged. - Polluted PR list, Ext JS PRs would be hard to find. • Didn’t have a way to share executable code. - Provide snippets only. - If an example existed, could point to that. - Use them other sites but be limited. 4
- 5. What We Needed • Means of sharing the code - In the forum, portal, docs, etc. - Internal and public. • Reproduce bugs - Save a test case with a framework version. • A web app, maybe using Ext JS! - Not checked into our private git repo. 5
- 6. Fiddle 1
- 7. Fiddle 1 (July 2013) • Savable/Forkable • Searchable • Support Latest Frameworks • Mimic local development - Yes and no • ~ 55,000 fiddles - ~7,000 distinct users - > 130,000 files - > 17,000 data files
- 8. Fiddle 1 Issues • The way it runs code with multiple files - Concatenated into a single <script> - Requiring classes may break the example • Data requests are hidden - All client side, no network requests • Tools are not functioning anymore - Was never updated due to Sencha Inspector • Funky UI 8
- 9. Fiddle 2
- 10. Fiddle 2 Fiddle 2 mimics local development. Code runs the way it should.
- 11. Fiddle 2 • Files load individually and remotely! - Much more like local development • Data requests are real network requests! - Inspectable in browser dev tools • Ext JS packages! * • Sencha Inspector integration • Better UI • * being populated
- 12. Next Week!
- 13. Demo
Notes de l'éditeur
- Before I dive into the new Sencha Fiddle, I want to first tell a story about how we got here. Why did we create the old Fiddle and why is there a new Fiddle.
- Talk about using other sites without talking bad about them. Position it in a way where Sencha Fiddle solves Sencha problems the others shouldn’t.
- This shows we weren’t being productive. We needed something to suit our needs to be productive.
- We thought about what we actually needed and saw that nothing out there would suit our needs.
- Enter Sencha Fiddle.
- Fiddle was never announced, it was just used. It was created for our use but had obvious benefits for our community.
- However it wasn’t perfect.
- Enter Fiddle 2.
- The biggest objective of Fiddle 2 is to be able to load files on demand when the code is run; that it should mimic what you’d expect locally.
- Not only the files but the data requests. We should also look at how to have tighter integration with Ext JS and Inspector. And of course we reevaluated the interface.
- Need to get out of slides and actually use it. I also have my local setup so fiddle will work offline so hopefully pesky demo gremlins won’t attack me.