Proposal: Demo should be moved from redux-autoform about redux-autoform HOT 20 CLOSED

Hey @JonatanSalas and @danigomez , I just thought about it thoroughly and the conclusion I got to is that we should not try to have separate branches for the demo, neither have a single unified demo. Here is why:

• Having the demo together with the UI itself doesn't mean we publish it to NPM. The NPM package has no demo at all, which means no footprint, or no overhead to the user of the library
• Having the demo together with the UI reduces the effort for debugging. If we use this "submodule" thing, we're adding overhead to the newcomers. The simpler we get, the bigger the chance we have contributors
• Having demos for multiple UI together will certainly lead to conflicting CSS (Bootstrap vs Material competing). LESS and SaSS have means of "isolating" CSS but the time I tried to make this work, I got into some troubles that I really think it's a waste of time.
• I already have the demo here bootstrap project.. And that took me time.
• What we can do, indeed, is to separate demo functionalities in a separate project to reduce duplication.

Any comments? Or can we do it that way? I really didn't want to spend time with this. I mean.. We should focus. I have a platform to build and a deadline to meet.

from redux-autoform.

Perfect job! This is growing faster! :)

from redux-autoform.

This is definitely the best way. You can either put the demo on the gh-pages branch of each UI library or you can use that website repo you created.

from redux-autoform.

André, really cool! Thank you very much! :)

from redux-autoform.

Let's keep it as is, and then when we get more advance on redux-autoform itself, we can try to get a better and simpler way to achieve this! 😄

from redux-autoform.

Thanks for the comprehension. I already moved the demo to the bootstrap project and I'm closing this issue as soon as I manage to publish the LIVE demo.

from redux-autoform.

Cool andré! We are going to do this things tomorrow! Nice work! :)

from redux-autoform.

@andrerpena Okey, I will work on the migration of the demo too.

from redux-autoform.

I'll moving the demo right now.

from redux-autoform.

Okay, thanks andré! Excuse me, I have no time to move it yesterday! :/

from redux-autoform.

@JonatanSalas don't worry. It's done and working. I'm just organizing the dependencies that are now useless and I'll publish this today.

from redux-autoform.

Hi @andrerpena , we were thinking with Joni how to solve the two points, have the demo in other branch and also allow you to work with hot reload.
Our proposal is to create a new repo with all the UI modules as submodels, in this way when you clone the demo all the git repos of all the UIs that are submodules will be downloaded and the hot reload will be possible.
Also we want to add a combo in the demo to select which UI you want to test, this way is possible to switch from UI to UI. what do you think???

from redux-autoform.

I like the unified demo thing.

I just didn't understand how can I "work" on the components and at the same time have the demo to hot-load.. Can you elaborate?

from redux-autoform.

What i mean is to have a repo, say, redux-autoform-demo which will have as git submodule redux-autoform-bootstrap-ui, redux-autoform-material-ui, etc, Because the git submodule downloads the code of the other repos as submodule, when you clone the redux-autoform-demo it will also download all the code of the UIs and then the demo will still working as is, but with te UI code in other repos. We will create a POC to check if is really possible but that's the idea 😄

from redux-autoform.

Oh now I understand. Yes..please create a POC because this seems weird. I mean.. I use WebStorm and it has pull push features. I don't know if it supports submodules.. I mean.. Now it would have to ask me which repo I'm talking about when I hit push.

The idea is neat but should be tested. I don't think I've seen it elsewhere.

Thank you.

from redux-autoform.

Excuse us! There is no trouble 😄

from redux-autoform.

I got to publish the demo here: https://redux-autoform.github.io/redux-autoform-bootstrap-ui/demo.html

Things that still need to be done:

• Remove the demo from the RAF source project
• Remove the demo from the RAF gh-pages
• Update documentation

Really.. any help is appreciated :)

from redux-autoform.

What pushed me back was that god damn bug with the localizer and I coudn't publish it without solving it. It's over now. Thank you.

from redux-autoform.

@andrerpena I only have to make an update on the documentation.

from redux-autoform.

Demo is now fine, documentation should be the problem now: #45

from redux-autoform.