> 1) Platform-dependent > 2) A compromise (=mix) between different HIG > 3) Stick to one platform HIG, give a sh.. about the others > 4) Do nothing. > > Each has pros and cons. > > I would be for 1) if somebody is willing to create the necessary > infrastructure in terms of documentation, an for 2) otherwise.
The infrastructures are there 1. ui is configurable 2. documents can reflect currently used UI using the new InsetInfo The only thing we need to do is define a ui file for each platform. A package maintainer will make one of them the default for a specific platform. I do not see any trouble in this approach. Bo