Community
Participate
Working Groups
The currently existing legacy RSE base actions framework and class hierarchy is currently far to overloaded, heavyweight and to far from the core Eclipse action framework. SystemBaseAction and it's subclasses tries to solve far to much things for contributor through far to much hierarchy levels. This might be nice in a closed product taking as much as possible of undifferenciating core stuff away from the developers, in a open-source context this is more distracting and frustrating contributors than it helps. Contributors who are used to the standard Eclipse action framework basically does not find anything really familiar within the RSE legacy action framework. The whole SystemBaseAction hierarchy is going totally to far here. Reducing the action framework to a real lightweight, as close as possible to standard Eclipse, one needs to be a major plan item for after RSE 2.0. There are really very few things that are common to all actions and therefor the layer needs to be very, very thin.
Won't get to this for 2.0 - in the future, we should consider using command/handler extensions.