Hi Harsha, I took a look at your framework, but I could not get the debugger to work. Is this the correct URL?
https://github.com/harsha-mudi/esti Zubair PS: It uses macros, core.async go blocks and observers over shared atoms to get the debug information. Not so much channels though. Feel free to dig into the code and see if you like On Friday, August 8, 2014 10:12:14 AM UTC+2, Harsha wrote: > On Thursday, August 7, 2014 11:06:12 PM UTC+5:30, Zubair Quraishi wrote: > > I add a new feature so that the current Om component being debugged in the > > "render" phase now shows in the debugger. So when you click on "Debug" and > > then see the debug items on the right you will see GUI fragments of the > > current Om component, its code (in coils form) and the state passed into > > that component: > > > > http://connecttous.co/connecttous/connecttous.html?livedebug=true > > This is neat. > I have done something very similar with my framework, harsha-mudi/rdp. > > It's an important advantage you get because of modelling everything > on top of events and messaging. > > From an implementation perspective, I think the right way to approach this > would be mixins. I am not sure how mixins are done in clojurescript. > > For example, from the ui you could take a component's name and > apply debugging methods to that component with a mixin. This like > applying a breakpoint. > > I believe you have applied debugging at a channel level ? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
