Hello Gary, Hello Gary,
To be honest I didn't look at seesaw much while developing Clarity, so I didn't make any conscious decision to differentiate with seesaw. It's very interesting to see that both me and Dave Ray came up with similar solutions/features. It seems that Seesaw is more concise in comparison to Clarity, and from the project page it does look like a more mature project. On the other hand, it seems to me (and I might be wrong) that Clarity has a more complete solution when it comes to selectors because it supports "categories" on top of the IDs, and the syntax caters for arbitrary logic operations and custom selectors. It seems that Seesaw uses binding for keeping GUI values and atoms/ refs in sync, and Clarity instead provides easy ways to retrieve all the values of all components in a panel as a map (see the HasValue interface). I like Clarity's approach better because it's more de- coupled. The other thing that I think differentiates Clarity is the live preview of layouts using clarity.dev/watch-component. Finally, let me repeat that all of the above are based on a superficial reading of Seesaw's docs, I may as well be wrong! Thanks, Stathis On Dec 3, 2:52 pm, Gary Trakhman <gary.trakh...@gmail.com> wrote: > Have you looked at seesaw? What differences are there in the design and > intent? -- 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
