Groovy
  1. Groovy
  2. GROOVY-3177

Preserve SwingBuilder.build(Closure).

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6-rc-2
    • Fix Version/s: 1.6-rc-1
    • Component/s: Swing
    • Labels:
      None

      Description

      Danno first "deprecated" static SwingBuilder.build(Closure) and has now introduced some crazy Groovy metaprogramming code into SwingBuilder as a "workaround" to the bugs caused by his attempts to make SwingBuilder threadsafe (which shouldn't be done and is a major and trouble plagued issue with no JIRA).

      static SwingBuilder.build(Closure) was introduced (by me) in Groovy 1.5 and is what I consider the preferred method for using SwingBuilder. It specifically addresses the common case of a user wanting a Swing UI with the minimum code and correct behavior wrt. EDT without having to even know there is one.

      http://www.nabble.com/SwingBuilder.build-%28was%3A-Re%3A--groovy-user--SwingBuilder-and-the-Event-Dispatch-Thread%29-p11354341.html

      It has been in use for more than a year now and is clearly being used by Groovy folks:

      http://www.nabble.com/Adding-a-GUI-to-a-program-td20437418.html#a20437418
      http://www.nabble.com/SwingBuilding-in-a-real-application--td19274585.html#a19276077
      http://www.nabble.com/Behavior-of-action-closure-in-SwingBuilder-td15348599.html#a15348599
      and many more...

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            James P. White
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development