text
stringlengths
0
1.17k
[2220.02 --> 2226.02] even had the help of bounty source um still had to be you know the final bit taken care of by mozilla
[2226.02 --> 2231.14] and big shout out to mozilla too you know i'll give them a thanks i know you already have but on the
[2231.14 --> 2237.86] show that's that's awesome to support tim like that so yeah they're awesome tim you mentioned um in
[2237.86 --> 2243.54] that in the video that we keep mentioning your demo uh a pro version what is that on the horizon that's
[2243.54 --> 2247.54] is that something that you're thinking about you just mentioned free code you know and no charge
[2247.54 --> 2253.86] for infrastructure so does does a pro version fit into that um i don't know i've sort of scrapped that idea
[2253.86 --> 2258.42] i do still have a hosting platform i've been developing and that's actually my only private
[2258.42 --> 2266.34] repo on github and we haven't talked about the t edit build system yet but yes that was pretty neat
[2266.34 --> 2272.74] too high level it's a build system like grunt or gulp or whatever but it works completely different
[2272.74 --> 2278.98] and you don't need a command line but this the same build system i've implemented in a node web service
[2278.98 --> 2286.74] where i can host your t edit based web apps and it's basically github pages but with a bunch of
[2286.74 --> 2294.26] smarts baked in so one idea is i could charge for that hosting because it's a service i don't mind i
[2294.26 --> 2297.62] don't mind charging for services i just don't want to charge for the infrastructure code
[2299.86 --> 2305.38] but hosting is a hard thing to make money from the the build system that you mentioned is that um
[2305.38 --> 2311.38] is that where you were piping into like app cache and the other tools that are available to to build
[2311.38 --> 2318.66] something because you use the use t edit to rebuild another version of t edit right right so let me let
[2318.66 --> 2325.70] me go into that so the original goal was i wanted a full development environment so once i have get done
[2325.70 --> 2331.22] and i've implemented push and pull and merge and diff and all that fun stuff i have version control i have
[2331.22 --> 2338.18] sharing and i've done dependencies with the easy sub modules i can add a package manager on top of
[2338.18 --> 2344.26] that that just eases setting up these sub modules but you still need a way to build files in modern web
[2344.26 --> 2348.74] development maybe some people use coffee script maybe you like writing common js but you're running
[2348.74 --> 2354.26] in a browser you need you need build steps and so the t edit build system is kind of unique
[2355.06 --> 2359.62] the way it works is you create these rule files i think there were some links in the video yeah
[2359.62 --> 2364.90] but now they're rule files dot rule they're actually written in john which is a subset of jack
[2365.54 --> 2370.74] like json is a subset of javascript so they look like json they're just a little more flexible
[2371.38 --> 2377.86] and you basically say all right this so you take the file that you want to exist i need an app cache
[2377.86 --> 2384.10] manifest or manifest app cache and then you add dot rule to the file name mark it as executable because
[2384.10 --> 2390.10] you can do that cross-platforming git because i'm not using real files and what the system will do
[2390.10 --> 2396.66] is when it sees an executable dot rule file when it's serving over the web or exporting to disk or
[2396.66 --> 2402.34] going through anything that needs the built version of the files it will execute that rule and the rule
[2402.34 --> 2408.50] itself will be an arbitrary program the user writes and i'm going to maintain a library of some useful
[2408.50 --> 2413.62] things and so these are the equivalent of your your gulp or grunt plugins and so i have one called app
[2413.62 --> 2419.30] cache and you give it a listing of files and what it will do is it will search the git tree the built
[2419.30 --> 2425.38] version find the e-tag of all those files and append them as comments in the app cache and if you've
[2425.38 --> 2429.78] worked with that cache before you know that the the file needs to change every time any file it depends
[2429.78 --> 2435.30] on changes and so that way you don't have to constantly go update some timestamp in your app cache
[2435.30 --> 2440.66] so when you refresh in the browser it automatically grabs the new app cache and you always have the
[2440.66 --> 2447.54] latest code and there's there's other compilers there's the the one i just built for my cross
[2447.54 --> 2454.50] platform stuff i called what did i call it js compiler something really really plain but what
[2454.50 --> 2461.14] it does is it takes a tree of source code that's in common js node style and then builds it as a bunch
[2461.14 --> 2469.22] of amd modules and then i have a really really minimal amd loader that injects those as script
[2469.22 --> 2475.46] tags in the web page and loads them on demand and i'm going to add another version that builds a
[2475.46 --> 2481.70] single concatenated file for websites that want to work offline and so what you'll do is you'll have
[2481.70 --> 2485.86] all your javascript in the one big concatenated file and then your app cache manifest will point to
[2485.86 --> 2490.50] that file and then anytime anything changes the e-tag of the big file will change which will then
[2490.50 --> 2496.18] cause them app cache to change and so you'll have automatic concatenation we can throw in
[2496.18 --> 2500.98] minification you can have any other filters you want we could do coffee script i have a
[2502.02 --> 2506.98] i've put facebook's regenerator in there because i really like using generators so now i can use
[2506.98 --> 2513.46] generators in any web app or chrome app i want and all of this works without a command line without node
[2513.46 --> 2519.62] without anything let's pause the show for just a minute give a shout out to our sponsor top towel
[2519.62 --> 2524.34] now we've been working with top towel for about a year now almost a year now and we thought it would
[2524.34 --> 2530.74] make sense to circle back and talk to some of our listeners who have applied to top towel and have
[2530.74 --> 2535.46] been accepted because only about two to three percent of the engineers who apply make it past their strict
[2535.46 --> 2541.22] elite engineering process and daniel lauzon a long-time listener and fan of the changelog
[2542.26 --> 2548.74] is now living the dream he's an elite engineer top towel and i say living the dream because he's now able to
[2548.74 --> 2554.50] have 100 control of the types of projects and technologies he's working on as well as the rate
[2554.50 --> 2561.30] he wants to charge daniel earns 100 of his income as a top towel engineer and he wanted me to pass on
[2561.30 --> 2566.18] his seal of approval of the top towel experience for those of you out there who are freelancing or
[2566.18 --> 2571.30] like to test out freelancing you've got to check out top towel if you think you have what it takes head to
[2571.30 --> 2577.94] top towel.com slash developers that's t-o-p-t-a-l.com slash developers to get started tell them the
[2577.94 --> 2578.74] changelog sent you
[2581.30 --> 2584.66] you mentioned in the video too since you're mentioning node and npm i think you mentioned earlier
[2584.66 --> 2592.10] um you know on a chromebook so you're this is just to kind of recap this is pointed right now it's a
[2592.10 --> 2596.98] chrome app and i think it seems like if i'm if i'm hearing you correctly it seems like it's a chrome
[2596.98 --> 2600.90] app now not because you don't want to be cross-platform but because you have limited time
[2600.90 --> 2606.98] and you need to make progress um is that is that accurate to say well i need i need the extra
[2606.98 --> 2612.74] primitives the web version has serious limitations right i can't get github or bitbucket to turn on
[2612.74 --> 2617.14] cores i have asked them multiple times and i don't know if they have security security concerns or what
[2617.14 --> 2624.42] but a web page cannot clone from github because it's cross domain yeah right now there is the rest api
[2624.42 --> 2628.90] which i use extensively but it's it's much slower and it's proprietary to them and it's not the same
[2630.50 --> 2635.38] so with a chrome app i have full access to everything and also i can access the file system
[2635.38 --> 2642.18] i can create a local http server and so you can write a web app in the chrome app host it start
[2642.18 --> 2646.98] the web server in the chrome app and then another tab in your chromebook you can then run your web app
[2647.54 --> 2652.34] and all of the build files will be built by t-edit in the chrome app and everything works end to end
[2652.34 --> 2657.46] and then like you mentioned you can also self-host the t-edit itself so i can build a chrome app with
[2657.46 --> 2663.46] a chrome app that's awesome let me just stop you for a second and say you're doing some really cool
[2663.46 --> 2668.58] stuff when i watched that jared up my i was like i seriously almost fell over i had to catch myself
[2669.86 --> 2674.10] i feel like there's certain people out there that like everybody should they should just be given a
[2674.10 --> 2678.42] bunch of money and be like just go do your thing and we're all going to be better off and i got a
[2678.42 --> 2685.94] feeling you're one of those guys sounds good to me well we're offline i mean what i think uh i think
[2685.94 --> 2691.14] what jared's trying to say is you have our full support whatever we can ever do to help you we're
[2691.14 --> 2694.90] going to be there for you and i'd like to talk to you more about some ways we can be a part of that and
[2694.90 --> 2702.34] just help make your life a little easier if we can so you um you touched on the web server part of it
[2702.34 --> 2707.22] um is there any more we can mention about that i think it's just kind of unique that it's it's all
[2707.22 --> 2714.50] encompassing t-edit it's it not only is it it's a full-on ide it's it's uh edit straight from git i
[2714.50 --> 2721.54] mean this is pretty some pretty amazing stuff um you know you can run the app itself with it um
[2722.74 --> 2727.62] and i think one other quote you said you're not building an editor you're building a workflow
[2727.62 --> 2734.10] and it seems like this is you know not only is it it's got all these complex back-end pieces but
[2734.90 --> 2740.10] you're also able to serve up whatever you've built and then the offline part that i think you touched
[2740.10 --> 2744.74] on in the video that i'm not sure how accurate it is now because that was in february but you were
[2744.74 --> 2750.50] able to kill the current web server and still serve up the game from the app cache right so app cache
[2750.50 --> 2755.70] lets apps work offline and when i get the web version of t-edit done it's going to have its own app cache
[2755.70 --> 2761.78] so you can you can go on an android tablet go to t-edit.creationx.com it'll run today but you have
[2761.78 --> 2767.86] to be online but once i get all of that done and i've implemented offline sync then you'll be able
[2767.86 --> 2775.30] to add this to home screen it'll work offline just like any native app which which i'm very excited about
[2776.26 --> 2781.62] how has uh mounting a github repo changed it see i couldn't tell from the video how
[2781.62 --> 2787.38] it seemed like you had to like manually type in you couldn't just like what maybe some users at
[2787.38 --> 2792.90] least i was thinking that you might just be able to choose um you know from the repo versus like
[2792.90 --> 2799.78] hand typing in creation x slash t edit i have an app for example to to kind of and then you also had
[2799.78 --> 2804.66] to point back i think a sha1 code can you talk about mounting a github repo maybe how that's changed