Marty.js – A JavaScript library for state management in React applications
1–10 of 95 posts
Re: Marty.js – A JavaScript library for state management in React applications
#2The fact it's got a Chrome extension and what appears to be comprehensive documentation bodes well. I'm currently using reflux because I like its simplicity (no dispatcher and no action creators) but Marty has definitely piqued my interest.
Edit: Question for the author. Any thoughts on isomorphic apps with Marty? Edit2: Answering my own question: https://github.com/jhollingworth/marty/issues/13
Re: Marty.js – A JavaScript library for state management in React applications
#3For me Marty is the best Flux implementation available right now. When reviewing other frameworks I found them to be either too restrictive by imposing non-flux limitations or the complete opposite by not implementing the flux principles well enough.
Re: Marty.js – A JavaScript library for state management in React applications
#4Re: Marty.js – A JavaScript library for state management in React applications
#5I'm scanning the documentation for this now and the "state sources" concept looks useful. Stores seem to be a bit cleverer than in other Flux implementations too. The fact it's got a Chrome extension and what appears to be comprehensive documentation bodes well. I'm currently using reflux because I like its simplicity (no dispatcher and no action creators) but Marty has definitely piqued my interest. Edit: Question f…
Re: Marty.js – A JavaScript library for state management in React applications
#6Re: Marty.js – A JavaScript library for state management in React applications
#7The examples look for me the same, except some additional functions to declare things.
Re: Marty.js – A JavaScript library for state management in React applications
#8In Marty: since you attach a Store to a React via a Mixin that looks for a singleton, can you have a dynamic number of stores when you have a dynamic number of React components of the same type?
I'm not very technical, by the way.
Re: Marty.js – A JavaScript library for state management in React applications
#9Can't see a difference between marty and fluxxor. The examples look for me the same, except some additional functions to declare things.
Some areas that Marty differs in: - State sources: http://martyjs.org/api/state-sources/index.html - Contants are handled more intelligently: http://martyjs.org/api/constants/index.html - Dev tools: http://martyjs.org/devtools/
Re: Marty.js – A JavaScript library for state management in React applications
#10Can't see a difference between marty and fluxxor. The examples look for me the same, except some additional functions to declare things.
- Fetch API for fetching data asynchronously without callbacks http://martyjs.org/guides/stores/fetching-data.html - State Mixins for binding stores to views http://martyjs.org/api/state-mixin/ - State sources for syncing state from heterogeneous sources http://martyjs.org/guides/state-sources/index.html - Chrome Developer extension (beta) for visualising the data flow and state of stores http://martyjs.org/devtools/