We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback
00:00

Formal Metadata

Title
MiniTalk
Title of Series
Number of Parts
37
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
13
Thumbnail
07:51
VideoconferencingCodeXML
Interior (topology)Parameter (computer programming)Disk read-and-write headMaxima and minimaOnline helpWindowMenu (computing)Execution unitMIDIRoyal NavyPointer (computer programming)Data modelConvex hullTheoremTotal S.A.Web pageGamma functionSpecial unitary groupCAN busRange (statistics)Revision controlCommodore VIC-20Sign (mathematics)Twin primeCNNFunction (mathematics)Hill differential equationNormed vector spaceComputer-generated imagerySoftware testingDifferent (Kate Ryan album)Presentation of a groupData structureRevision controlRight angleComputer fileStandard deviationExistenceSubsetHash functionLevel (video gaming)Computer configurationUniform resource locatorSystem callOpen sourceDefault (computer science)Web pageTouchscreenAutomationMultiplication signOnline helpPerfect groupCodeFront and back endsCore dumpRoutingSoftware maintenanceSlide ruleResolvent formalismTwitterView (database)MereologyProcess (computing)NumberField (computer science)Computer animation
Set (mathematics)Asynchronous Transfer ModeVideoconferencingService (economics)Event horizonXML
Transcript: English(auto-generated)
My name's Gaurav Manjal, I'm a front-end engineer at HedgeServe, and I'm a maintainer of Ember
Twiddle and an all-around open source contributor. I actually had slides prepared like a couple of weeks ago, but so much has happened in Ember Twiddle since that I decided not to bother with those slides.
So this is what Ember Twiddle now looks like. One of the major differences between this and last week is that we are no longer using pod structure by default, we are now using the standard structure by default. This was done because pods are no longer apparently the future, I don't know why, but they aren't.
So we also, it's a little easier for newcomers who have first got into Ember and have no idea what pods are, they can dive right in more easily. But a lot of your existing twiddles are in pods, so what are we going to do about that?
If you look in, there's a file called twiddle.json in every single twiddle that you create. One of the things that it nicely does is tell you what version of Twiddle it was created in so that we can ensure that your twiddles will remain compatible forever.
The options over there is use pods. If you were to switch that to true, it will start creating new files in pod structure rather than in traditional structure, just like a generator would.
And if you already have a twiddle in pod structure, you may just want to set this tag true in that twiddle so that you can continue where you left off. But you don't have to, you can mix and match, the Ember Resolver understands that just fine. The next thing I'd like to point out is if you have worked with Ember Twiddle in the past,
you might have noticed that you had to copy and paste from gist to find your old twiddles. You no longer have to do that. We have a save twiddles page which brings up all your twiddles.
You can see all my twiddles forever, I have too many of them. And you can just click on one of the twiddles and just bring it right back up. And I'm back to just where I was a second ago, which is great. And the next thing I'd like to point out is we've really been working on tests very hard in Ember Twiddle.
Now, this was a long effort, but we've managed to make it possible for you to actually run an automated test in Ember Twiddle. This is great if you want to show the core team that, hey, why is this test not working?
The code works, which happens a lot. So it used to be, and I actually had a whole presentation on how to write a test because it was so difficult. You had to bring in blueprints and create files and all that stuff. You no longer have to do that.
You can just go to file, add, go down to this new tests bar. And if I can get it to stay there, you can see that you get your, what did Liz call it, the stages of acceptance or something like that?
Anyway, you just, okay, this is not fun. Believe it or not, I can't see the screen in front of me.
Now, another wonderful thing we've done is all you basically have to do when you're creating a new test is make sure that your file name is correct for the test you want to create. You click okay, and it does everything you need.
It creates all the blueprints you need for tests to run and adds them to your Twiddle. And of course, the test fails because the route that I just are testing doesn't exist. But that can be fixed. Anyway, I'm going to move on. If you go back to, one of the things you can now do is actually open an earlier revision of a gist.
I'm going to open a new test. And the only thing with this is the UI isn't there for it yet, but we're working on that.
But in the meantime, you just pick any gist you happen to have, go to the revisions tab, pick the revision you want to open, go up to the URL bar, grab the hash, and this is going to be fun, a hash of the gist and the hash of the revision,
and just copy and paste it back to your Twiddle, bring the URL bar back.
And I can't see if that's right, but one of the new features we also happen to have is that when you happen to have changed anything in your Twiddle, and you probably have done this,
you've accidentally navigated away from the page, you will find that you lost your data. But now we actually have a confirmation dialogue. This will hopefully save a lot of people a lot of time. So where is the extra letter?
Right there? Like that? Perfect.
And once again, we have the revision of the gist that we had at the beginning. Thanks a lot for listening. There's plenty more going on in Ember Twiddle land. We are looking for help, help wanted tags in the GitHub.
My name is Gorev0 on GitHub, 9576 on Twitter.com. Please feel free to contact me and help us out.