Hi Mathias, >>>Good examples: MediaDescriptor and EmbeddedObjectContainer in comphelper. >>Are you volunteering to introduce those two helper? :) > > No.
What a pity. > Meanwhile I think we should better have some UNO services replacing > the helper classes. Wrapper classes for UNO interfaces or services > mostly indicate that the API is too cumbersome and a more user friendly > one is needed. You seem to implicitly assume that the helpers are mostly to workaround combersome UNO APIs. Like Christoph's assumption that 95% of them are useless and can be removed, I question this. IMO, there are enough which ease implementing UNO components, or which ease using them on a level where introducing a dedicated API does not make sense for several reasons. We can verify or falsify those assumptions only if somebody has a look at every single of the helpers. I had the hope that we can do this together, by having all of us, with our combined experience, a look at them. So, what's on the list so far as desired outcome: - more developers are aware of useful helper implementations - we can discuss existing helpers and - identify and replace obsolete helpers - identify helpers which just work around missing UNO API - we can identify helpers which with are mature and useful enough to become part of the SDK None of those items can be done by a single person, IMO. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
