OK, I don't know if others are more familiar with one API than the other, I just don't remember seeing anything saying one way or the other. If someone does know swing very well then that might be a good reason.
Michael Whapples On 04/11/10 22:21, qubit wrote:
I also gathered from her emails that Yuemei, who is doing the UI for this program, is experienced in SWING and not in SWT, so I was thinking of simplifying her learning curve. Just a thought. --le ----- Original Message ----- From: "Sina Bahram"<sbahram@xxxxxxxxx> To:<brailleblaster@xxxxxxxxxxxxx> Sent: Thursday, November 04, 2010 11:51 AM Subject: [brailleblaster] Re: Are there sample programs comparing SWT and swingwt? It doesn't include parts of the SWT that don't map the other way, because you can always use SWT along side, so there's no exclusion , just inclusion. It's fine if we don't wish to use SwingWT, it was just a suggestion as I feel swing's code is much cleaner and easier to work in than SWT's. Take care, Sina -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples Sent: Thursday, November 04, 2010 12:13 PM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: Are there sample programs comparing SWT and swingwt? I have a couple of questions on this. The first big question is, what is our need for swingwt? We are writing the code from scratch so why work to the swing API of swingwt rather than the SWT API, it may be different if there were swing code we want to move to use SWT components. As far as I know nobody has said they are particularly skilled in swing. If someone was then it may be less of a learning curve to use swingwt. As I understand the situation either API would need to be learnt. Always using a mapping layer (particularly when mapping between two separate existing APIs) may limit the possible flexibility of the toolkit being used and may introduce new bugs. What I mean here is, how well does the swing API really fit over the SWT API? If we needed a custom control what flexibility in creating that custom control would swingwt offer? We also are concerned with how well the java accessibility API maps over the SWT accessibility API (most important when creating a custom control but we may need it on a few standard controls). I'm really not finding reasons to use swingwt. So that leads to the other question, when saying its between 90% and 95% complete, does this include parts of the SWT API which don't really map to the swing API? Michael Whapples On 04/11/10 14:16, Sina Bahram wrote:I don't think we're really communicating on this one. SwingWT and swt, are not different. SwingWT simply allows you to use Swing syntax to generate SWT bindings, that's all. Thus, the limitation of a translational mapping would be measured by the level of completeness of that mapping. This particular issue is discussed on the website for SwingWT, but essentially themapping is like 90 to 95% there.Take care, Sina -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer Sent: Thursday, November 04, 2010 3:38 AM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Are there sample programs comparing SWT and swingwt? It would be nice to see some. What advantages does swingwt have over SWT besides being easier for the programmer? I've learned to be wary of things that are supposedly easy. Thanks, John -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities
