ok, second run at the KEditToolBar stuff. the constructors have now been wildly simplified; use setResourceFile to, well, set the resource file rather than setting it in the constructor. ;) This makes the KEditToolBarWidget API slightly uglyfied in that you now need to call one of the two load(..) methods before showing, but since this is almost purely an internal class it's not a big deal.

in fact, the only reason KEditToolBarWidget is even exported still is for future use by a kcm version of the dialog. ask dfaure about that if you have questions about it =)