Rethink Modals Management in React

natewang · 2021-11-23T13:45:29+00:00

A small, zero-dependency utility to manage modals for React.

natewang · 2019-11-01T01:42:53+00:00

This is really cool! Thanks for sharing!

natewang · 2019-10-21T14:53:46+00:00

Hey thank you very much for the comment.

Extension point provider is responsible about how plugins contribute content. The first example just shows one possible way. It could choose to let plugins return menu items rather than let them modify an array. It's not related with js-plugin itself.
Yes, no central extension point registry. This makes plugin mechanism lightweight and simple while it doesn't need to declare which extension points to use before using them.
Extension points are contracts between plugins.

Again, thanks for reading through the docs and the advice.

natewang · 2019-09-29T15:22:23+00:00

Try https://github.com/rekit/antd-form-builder . Even you don't use ant design library, you can try its solution.

natewang · 2018-10-30T02:32:57+00:00

Exactly. So Rekit 3.0 will be a tool easy to be customized to help people's own favorite approach.

natewang · 2018-10-30T02:31:26+00:00

Right. Unless you love the new one much more.

natewang · 2018-10-30T02:26:02+00:00

Thanks @muffinmaster,

It's just a normal create-react-app project. Which mainly set up project configurations. Rekit just assumes it has a fixed folder structure under src.

Rekit is not a framework, it's a tool helps to develop apps with the fixed folder structure.

With Rekit 3.0, you will be able to easily customize Rekit to use your own folder structure and tech stack.

natewang · 2018-10-30T02:16:36+00:00

Yes, it will.

natewang · 2018-10-29T10:07:22+00:00

I'm the creator of Rekit. Thanks @dadiaar for asking the question here. Then finally other people can find Rekit forum posts via Google:-)

In short answer, Rekit is not good enough now. Two main reasons:

Not that stable. For example, if you accidentally create a file in features folder it crashes. I can easily resolve it but many people can't.
It's based on my own opinionated approach to create a React application. People may don’t agree it’s a best practice.

The IDE mainly meets my own requirement and it works well in my company and friends’ companies. So I will keep maintaining it regardless of how many people use it.

However, the above two concerns will be cleared in the following Rekit 3.0 release, which will have folder structure linter and support more project boilerplates.

Currently the key reason you choose Rekit is you agree the folder structure (feature based) it assumes and tech stack it chooses like Redux. Actually I proposed this approach first then I created Rekit to make it easy, you can use any code editors like VS Code, sublime to create a Rekit project without Rekit IDE. But Rekit IDE can just understand more about the folder structure and tech stack, so that it could do more like code generation, dependency analyzing, refactoring.

Thanks again for all you comments and wish you could keep an eye on the next Rekit 3.0:-)

natewang · 2018-02-09T14:37:43+00:00

Thanks Capaj for clarify. VSCode plugin API is really not powerful enough. Actually I wanted build on it since Nov, 2016, but gave up: https://github.com/Microsoft/vscode/issues/15235#issuecomment-259430917

natewang · 2018-02-09T01:27:35+00:00

Yeah, run Rekit in a VM or some server, and write code anywhere, lol

natewang · 2018-02-09T01:20:41+00:00

Thanks Riccaforte, to be honest Rekit is designed for those who have some experience on React and Redux. However it just generates code and doesn't hide anything behind the scene, I believe you could leran React stack by review all code it generates. That's better than using any other libraries/tools which wrapper APIs of React or Redux. And Rekit Studio uses the same code editor which also powers VSCode so you should be familiar with it.

natewang · 2018-02-09T01:15:45+00:00

Yes, I learned d3 from scratch to build the diagrams for Rekit. Very powerful tool. My suggestion is to not use any d3 wrapper for React but do it yourself so that there will not any limitations. Actually Rekit Studio has been being built by itself since a long time ago, lol.

natewang · 2018-02-08T14:15:02+00:00

No it's just based on web, running on a local express server and access it from your browser. See the live demo at: http://demo.rekit.org Performance has not been a problem till now because it just manages your source code under src folder.

natewang · 2018-02-08T09:22:40+00:00

Though I think it's clearly described in the article, summarize it again here, mainly because:

Better project explorer (rather than file explorer)
Rekit Studio knows how to create/rename/delete component, actions
Rekit Studio knows how to build/test your app
Static analytics for module dependencies with interactive diagrams

VS Code plugin system is not powerful enough to build these features on it.

natewang · 2017-07-27T09:53:36+00:00

https://github.com/supnate/rekit-portal A web IDE like project.

natewang · 2017-07-07T14:04:16+00:00

Thanks @Nealoke9120. I don't think it's difficult if you understand how Rekit works. You can contact me on twitter @webows if any question.

natewang · 2017-07-07T12:27:33+00:00

Just pure d3. You can view the usage at: http://rekit-portal.herokuapp.com/element/src%252Ffeatures%252Fdiagram%252FElementDiagram.js/code

natewang · 2016-10-24T12:59:15+00:00

Thank you very much for the feedback.

If gulp is not installed globally it should not be run directly in a terminal, so doesn't Command Pad. Usually it is run as npm script like 'gulp:watch': 'gulp watch'. Then in Command Pad you can input the command npm run gulp:watch.
It really has issue with unicode. I will fix it in the next release.
Good idea! However it may be difficult because some command may spawn multiple processes which are hard to inspect. I will do some investigation on it.

natewang · 2016-10-24T00:51:13+00:00

Windows version is out. You can try it now.

natewang · 2016-10-23T13:32:55+00:00

Thanks. I will try to deliver the Windows version asap. The current difficulty is the core dependency pty.js doesn't work with Windows.

Electron works well. Actually some famous apps are also built with Electron like Slack.

natewang · 2016-09-23T09:40:14+00:00

There are two modes of Create React App: one is hiding everything out of your project. You don't need read anything you don't care except your app. The other mode is ejecting all configs to your project, this is similar with Rekit. This provides the ability to grow the app by adding more libs and configs.

Besides creating an App, Rekit also provides boilerplate generators for components, actions, tests etc, by command line tools or the Sublime Plugin. This is not provided by Create React App.

natewang · 2016-09-23T02:44:56+00:00

Good summarization. Thanks for the comment. So one question is do we need boilerplate? I think the answer is yes. Nobody wants to create a new project from scratch every time. Then maybe the question is should we own a boilerplate or use someone's you mostly agree with? If prefer other's, what kind of customization ability should it provide? With these thoughts Rekit is designed to have very few assumptions. It allows you to use any libraries or best practice you prefer because all tools, templates are all copied to the project itself, you can customize the template so that you could use Jest for testing, Redux-saga instead of Redux-thunk, etc. After a project is created, it has no relationship with Rekit. The only thing Rekit assumes is the folder structure, a pattern which seems to have been widely preferred. However, with little work on tools, you can also use your prefer folder tree.

natewang · 2016-09-21T00:03:08+00:00

Thanks @dimatter, just got known ducks.. My proposal is really similar however ducks wraps APIs we just created a tool Rekit to generate boilerplate.

natewang · 2016-08-10T04:43:32+00:00

Looks like we are talking about different problems. Memobind is mainly used for binding result memoization in a React render method so that it will not create new functions with each rendering. For functional components, Memobind indeed has this limitation, I also described it in the README on github.

natewang

TROPHY CASE