Jain, Ankit wrote: > Hi Ketan, > > You said it right way to extend SWTBot functionality, Even I am also > doing the same. But I have concern with the existing API. > Let's take an example of SWTBotTable. Here the method getTableItem() is > private. So Again one has to write the same method in Extending > class(e.g MySWTBotTable extends SWTBotTable). I think these method > should be made protected so that code reusability remains.
Making methods protected would mean additional API that needs to be maintained. Also the getTableItem() is actually public api. What version of SWTBot are you using ? > Almost all classes in SWTBot I have extended, and I am copying many > private methods to the extended class, which is not good. Doing this may not work in the long run, esp as SWTBot api evolves. I'd recommend asking on the mailing list, and perhaps filing a bug. -- Ketan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ SWTBot-users mailing list SWTBot-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/swtbot-users http://swtbot.org/ - a functional testing tool for SWT/Eclipse
