Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: why deku.createApp? #391

Open
rstacruz opened this issue Jan 24, 2016 · 1 comment
Open

Question: why deku.createApp? #391

rstacruz opened this issue Jan 24, 2016 · 1 comment

Comments

@rstacruz
Copy link
Collaborator

I see this was changed sometime between rc11 and rc15. What was the rationale for this?

@anthonyshort
Copy link
Owner

The idea is that the core of deku should be a element, a diffing function, and then two renderers that know how to respond to the diff. But if we only go that far, we're not help users and there will be a huge barrier to entry.

So I wanted to seperate the idea of kickstarting an app. The one included with Deku will be simple and work most of the time, but people can roll their own if they want to do something different. It will hook everything up to the store so users can just start building a UI, similar to Elms StartApp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants