it would increase the size of Deco to bundle it, but would also improve the user experience, so I think it'd be worth it. pre-build an ios binary for the katas.(I think this was the case last I checked) if vector icons is the only native module, it might not be that critical to keep it. remove native modules from that katas, so they can run using Deco's default pre-built ios app.That said, I'm wondering if just for the katas we should try to skip the build step, since it's the last bit that will have a significant delay. It will probably be necessary for advanced templates. Actually, you can expect an API for accessing the building/simulator/packager pipeline this week from It uses a separate and gives you very fine-grained control. In this case, after a template is instantiated you want to run a native build (cmd+B), so that might need an API into Deco Launch a simulator with live-reload already enabled (not sure if this already exists in default deco projects)Ī 'bootstrap' automation script. Ditch the 'starter file' comment approach, and have some sort of scripted walkthrough - which will make this editor unique, and I think the price for doing this is relatively small, since there are already many tutor libraries in the Javascript/web world (but I imagine this might add a big product/ux planning and overhead).Within the comment above, that exists in the starter file, deep-link each file mentioned into the existing project hierarcy to let the user go back and forth along the project tree.The following is two options into what I think may be a good tutor: I guess these all can be specified in package.json.In this case, while a new template is being built, as a user, I can view the first file of a template - which can be an index.js file with a nice comment that serves as an introduction into that template A 'starter file' that is opened automatically.Here's some input, that I imagine template projects will need in general: I've just finished going through some Katas with Deco, it's been even more immersive than my usual setup! Probably safe to assume we can bundle them all with the Deco binary for now, rather than downloading them on the fly. What's involved here technically: come up with a way to instantiate different default files based on project template selected. You can "save" or "save as" just as you would normally if you want to save your progress, or you can follow the template without saving and never clutter up your file system. Picking a tutorial will do what any project template will: create a react native project in the temp directory (just like we do currently) with files specific to that template. Maybe we put a ✅ by the ones I've already done. If I click it, I see a list of tutorials I can do. I know JS and React, but not React Native. After chatting with I propose we add the tutorials (called Katas) from as project templates. I want to create a new project with redux + react-native-router-flux.Ī very compelling first use case would be to help beginners learn React Native, with a focus on design. We've been discussing project templates for a while, e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |