3 ms·
It sounds neat in theory, but there are no screenshots and I can't view any kind of demo without creating an account which is a non-starter so I have no idea wh
by kingbirdy 6y ago
It sounds neat in theory, but there are no screenshots and I can't view any kind of demo without creating an account which is a non-starter so I have no idea what the actual quality is.
- rlindskog 6y agoSorry about that, getting a video up ASAP. For now, here is a screenshot of the editor: https://twitter.com/r_lindskog/status/1251202889583865856/photo/1 https://twitter.com/r_lindskog/status/1251202889583865856/ph...
- rlindskog 6y agoHere is the demo video! https://www.youtube.com/watch?v=d96LZJJZ3dE&feature=emb_title https://www.youtube.com/watch?v=d96LZJJZ3dE&feature=emb_titl...
- kingbirdy 6y agoYou have to manually edit the display for every single instance of an item, rather than just being able to set it for all items of that type? That seems tedious and error-prone.
- rlindskog 6y agoThanks for the feedback, I get where you're coming from. I thought a lot about this. If you set it by type, then it wouldn't make sense either. Take pokemon() and pokemon() { evolutions } for example. For pokemon() you would expect a profile like component, and for evolutions you would expect a list item component, even though they are the same type (Pokemon). That being said, reusable components is on the roadmap, this is just the beginning.