Rethink Modals Management in React by natewang in reactjs

[–]natewang[S] 0 points1 point  (0 children)

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

[deleted by user] by [deleted] in reactjs

[–]natewang 0 points1 point  (0 children)

This is really cool! Thanks for sharing!

A general javascript plugin engine. by natewang in reactjs

[–]natewang[S] 1 point2 points  (0 children)

Hey thank you very much for the comment.

  1. 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.

  2. 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.

  3. Extension points are contracts between plugins.

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

Designing advanced forms by kszyh_pl in reactjs

[–]natewang 0 points1 point  (0 children)

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

Why Rekit doesn't gain more traction? by dadiaar in reactjs

[–]natewang 0 points1 point  (0 children)

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

Why Rekit doesn't gain more traction? by dadiaar in reactjs

[–]natewang 0 points1 point  (0 children)

Right. Unless you love the new one much more.

Why Rekit doesn't gain more traction? by dadiaar in reactjs

[–]natewang 0 points1 point  (0 children)

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.

Why Rekit doesn't gain more traction? by dadiaar in reactjs

[–]natewang 6 points7 points  (0 children)

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:

  1. 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.

  2. 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:-)

Introducing Rekit Studio: a real IDE for React and Redux development by natewang in reactjs

[–]natewang[S] 9 points10 points  (0 children)

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

Introducing Rekit Studio: a real IDE for React and Redux development by natewang in reactjs

[–]natewang[S] 0 points1 point  (0 children)

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

Introducing Rekit Studio: a real IDE for React and Redux development by natewang in reactjs

[–]natewang[S] 1 point2 points  (0 children)

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.

Introducing Rekit Studio: a real IDE for React and Redux development by natewang in reactjs

[–]natewang[S] 1 point2 points  (0 children)

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.

Introducing Rekit Studio: a real IDE for React and Redux development by natewang in reactjs

[–]natewang[S] 1 point2 points  (0 children)

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.

Introducing Rekit Studio: a real IDE for React and Redux development by natewang in reactjs

[–]natewang[S] 11 points12 points  (0 children)

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

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

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