The miscommunication I see is this: In many SPA frameworks like Angular and Ember, the resuable components cannot work as is across frameworks. Therefore, they have certain dependencies on the framework that cannot be packaged and carried across the framework boundary. Try taking an Angular widget and using it out of the box with Meteor or Ember (well, Ember and Angular just announced a partnership so that may actually be coming! not a great example but translate that to components should be reusable across "SPA frameworks using React for view layer"
If we don't have a standard for reusable components then what I may develop my components for "SPA Framework XYZ using React for view layer" (say my own Reagent SPA framework) may not work out of the box on "SPA Framework ABC using React for view layer" (say re-frame) because I did not design my components for out-of-the-box re-usability across "all frameworks that use React for view layer" For example, I may have expected the framework to have a state manager that does all state updates, or I may have expected a data caching service where instead the other framework keeps refetching data, so I may have time breaks in the UX that I didn't expect. What does a framework need to have at minimum besides React for the view layer? And more importantly how should I define my component (in code) in order for it to be usable by any SPA framework using React for view layer? (e.g. Om+etc) Do we have a standard for that? if not, then how will I be able to keep hopping on the latest greatest SPA framework that uses React for view layer? I wouldn't be able to. I'd be wedded to the framework where my components work On Mon, Mar 9, 2015 at 9:14 PM, Mike Thompson <m.l.thompson...@gmail.com> wrote: > On Tuesday, March 10, 2015 at 2:35:24 PM UTC+11, marc fawzi wrote: > > Since when can an Angular component work as is in a React environment or > a Backbone "component" (view) work in another Backbone implementation > without changes? > > > > > > That is what I mean, and I don't have to get into the re-frame specifics > to tell you that a component built for my architecture won't work out of > the box with your architecture or at least it won't leverage it properly. > > > > > > This is the ABC of app development: components are built to leverage the > abstractions offered by specific frameworks. Web Components were supposed > to change all that but they're stuck in standardization hell, four years > now. > > > > > > There is no confusion on my part that so far we've been building React > components, Backbone views (some based on handlebars and some on underscore > and some on custom view layers etc) and Angular components, and all those > "Components" are framework specific. > > > > > > So if you've come up with a framework that can work with ANY component > architecture then that must be some great innovation because I'm not sure > how you'd be able to account for all the services and framework facilities > that a given component expects. > > > > > > If we don't have a Standard for reusable components in ClojureScript > that crosses SPA framework boundary we will not have anything better than > what is available in JS in terms of re-use potential of components across > frameworks. > > > > There quite a miscommunication happening here. I was saying that you can > build lots of different re-usable component libraries on top of Angular. > Angular doesn't mandate one. The Angular widget libraries and Angular are > different layers. > > Similarly, re-frame doesn't mandate a single reagent reusable component > library. In the future there might be many, who knows. re-frame and a > reagent reusable component library are different layers. > > -- > Mike > > > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojurescript+unsubscr...@googlegroups.com. > To post to this group, send email to clojurescript@googlegroups.com. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
