Stathis, I use the Lazytest watcher partly out of convenience. I happen to use Lazytest for testing so it's usually already running anyway. However, some work has already been done to extract the watch functionality [1]. It might be fun to combine your viewer with it. Maybe have a naming convention for the watch entry point of an app or component so you can use it without editing the file.
[1] https://groups.google.com/group/clojure-dev/browse_thread/thread/32ab1a5e7f819196/dde7a347e7f56b0a Cheers, Dave On Tue, Dec 6, 2011 at 1:45 PM, Stathis Sideris <side...@gmail.com> wrote: > Hello Dave, > >> I'll clarify some of Stathis' remarks about Seesaw below. Obviously, >> I'm a little biased, but Clarity looks cool and I plan on "borrowing" >> some of its features for Seesaw in the next release or two :) I think >> it's great to have multiple projects like this to inspire each other >> and keep everyone honest. Keep up the nice work! > > Thanks for your kind words, if you're borrowing I must be doing > something right! I too think that it's really cool to have multiple > projects, and it may help us learn from each other! We do have similar > problems after all. > >> Seesaw selectors are basically Enlive selectors [1] ported to Swing. >> So it supports all the usually CSS hierarchical stuff, ids and classes >> (Clarity's categories). It can also select on Java class/sub-class >> relationships. I left it at that since selector+filter seemed a >> reasonable enough way to add custom predicates or whatever if >> necessary. >> >> [1]http://enlive.cgrand.net/syntax.html > > OK that looks pretty powerful too, I retract my comments about being > able to do more with Clarity's selectors. :-) > >> > The other thing that I think differentiates Clarity is the live >> > preview of layouts using clarity.dev/watch-component. >> >> I think that's very cool too. I approximate that workflow using >> lazytest's watcher to re-run my code when it changes. > > I think that's a much better way. Currently, when watching a > component, Clarity bashes the JVM by creating the component every X > seconds (I did say it was an experimental feature!). I'll look into > lazytest's code to see how it detects the code changes. I suppose it > watches for changes in the class files, right? > > Stathis > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
