Hi Regarding explorability, what would be the best way to provide an repl directly in a Seesaw app?
/kevin On Dec 21, 2011 10:12 AM, "Sam Aaron" <samaa...@gmail.com> wrote: > Hi Dave, > > very cool - I love that you're working on improving the explorability of > the system. It's clearly a focus that REPL driven development emphasises > and I hope we see more people working in this area. > > Sam > > --- > http://sam.aaron.name > > On 21 Dec 2011, at 03:24, Dave Ray wrote: > > > Hi, > > > > I've just release Seesaw 1.3.0. Details of this release can be found > > in the release notes [1]. There are a few features I'm pretty happy > > about, so I'll mention them briefly here. > > > > Interactive development: So far, learning Seesaw has meant getting > > familiar with Java and Swing. I think that element will always be > > there, but it can be made better. Toward that end, two new functions, > > (seesaw.dev/show-options) and (seesaw.dev/show-events) can be used at > > the repl to ask a widget about it's options and events respectively. > > Hopefully this will save a few trips to the Javadocs. I've already > > used it several times myself. Example output can be found in this gist > > [2] > > > > Value Semantics: As I threatened, I've borrowed the value semantics > > which Stathis Sedaris introduced in Clarity [3]. (seesaw.core/value) > > will give you the "value" of a widget, or a map of values for > > composites. It's really a nice way to work, especially for forms. > > > > Key Mapping: Like everything else in Swing, setting up key > > mappings/bindings is a pain in the ass. This interface hopefully makes > > that much easier. For example, to handle the enter key in a list box, > > just do (map-key my-box "ENTER" (fn [e] ... do something ...)). > > > > Improved Interop: Seesaw will now play nicely with whatever widget you > > give it whether it was created by Seesaw or not. This should make it > > straightforward to use UIs built with wysiwyg editors from Clojure. > > > > Those are the biggies. There have also been several bug fixes and > > minor improvements. > > > > Cheers, > > > > Dave > > > > > > [1] https://github.com/daveray/seesaw/wiki/Release-Notes > > [2] https://gist.github.com/1450241 > > [3] https://github.com/stathissideris/clarity > > > > -- > > 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 -- 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
