Regarding the idea to use the SWT browser component for Saros-E as well as Saros-I:
Holger wrote: > do we really want to include SWT in our libraries? If it makes our life simpler: yes. Does it make our life simpler?: We need to find this out. - There is obviously no problem for Eclipse. - Can SWT be a separate plugin in IntelliJ? - Is it common in IntelliJ that users have an SWT plugin already? - If not: What mechanisms are there in IntelliJ to load the SWT library at Saros-install-time? - If none: How difficult would it be for us to release three(?) different versions of Saros-I, one per platform? The result may well be: Too difficult, we don't do all this. But so far it still looks promising to me. Lutz ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
