Matthias, please observe that this is an English-language mailing list. Björn's German email was a mistake.
You asked how you should go about understanding the browser-based GUI approach better. Here is a suggestion: - talk to Damla Durmaz, she is implementing a simple (without input) case on the Eclipse side right now - the browser base component already exists on the Eclipse side (written by Björn Kahlert) - have a closer look at how Björns component works (it builds on top of Eclipse's SWT browser component but adds a lot of usage simplification stuff) - look at IntelliJ: What does the most suitable IntelliJ (Swing) browser component look like? Here are a few starting points: http://stackoverflow.com/questions/48249/is-there-a-way-to-embed-a-browser-in-java http://stackoverflow.com/questions/1454652/embed-browser-in-java-based-desktop-application - How would one wrap it such that it becomes fully(!) compatible to Björns Eclipse component? If necessary, we will of course modify Björns component to make this easier. - When you understand this, come back and explain it to all of us, so we can make a decision together how to proceed. Second, you said it was your understanding that parts of the Saros-E GUI were implemented in this browser-based way. No, this is not the case. Björn has built a different application where this is true. But for Saros, we only now start to look into this implementation style -- so there is plenty of free space for you to act in. Lutz Prechelt ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
