Hi Scott, As I recall, there was really only one big sticking point, and that was that some Swing components painted directly to the display, which wreaked havoc with Pivot's own paint() calls. Basically, it caused paint artifacts since the Pivot components weren't notified that they needed to repaint. For some Swing components, it worked perfectly, so if you have a specific use case in mind, it may suit your needs.
The last that SwingAdapter saw the light of day was in Pivot 1.0.1, so you can see it in the tags folder: http://svn.apache.org/repos/asf/pivot/tags/v1.0.1/wtk/src/pivot/wtk/SwingAdapter.java http://svn.apache.org/repos/asf/pivot/tags/v1.0.1/wtk/src/pivot/wtk/SwingAdapterListener.java Cheers, -T On Tue, Feb 23, 2010 at 4:49 PM, Scott Baxter <[email protected]>wrote: > Todd, > > What were the sticking points with the Swing adapter? It seems like a > Swing adapter would add a lot of extensibility to Pivot that may be needed > as it grows. Specifically, there is a commercial Swing component (Ephox > LiveEdit) that I'd like to integrate into the content management type app > I'm prototyping now in Pivot. I'm sure other potential Pivot developers > have other Swing components they'd like to integrate as well. At the > moment, I'm afraid once I move to the implementation stage, I might have to > switch back to a JavaScript framework, which I'd really like to get away > from. > > Is your SwingAdapter code available for me (or anyone else) to look at as a > starting point? (Not that I'd put much confidence in my ability to get it > to work if you haven't had any success.) > > Scott >
