on documentation

Andreas Pakulat apaku at gmx.de
Sun Feb 1 14:12:12 UTC 2009


On 01.02.09 11:57:06, David nolden wrote:
> Am Sonntag 01 Februar 2009 11:43:18 schrieb Andreas Pakulat:
> > But thats the standard way in kdevplatform to ask a plugin (or whatever)
> > for something that should be shown in an already known parent. So we
> > should use the same pattern here, that way the API is consistent in such
> > cases.
> But it moves complexity from one place(Where the widget is used/integrated) to 
> many places(All the documentation plugins), and is inflexible(What about 
> layouts etc.?).

Maybe I'm misunderstanding how this widget would be used, but isn't this
simply embedded "standalone" into a toolview? 

Or are you expecting to have multiple widgets from different doc plugins
visible at the same time? How are you imagining that to work?

Even if the latter I don't see why the function should have the parent
member, it makes it a lot easier for doc-plugin writers to use the right
parent for whatever widget they want to return. They don't need to think
about wether they should use "0" or mainwindow or something else, they
can simply take what is given to them via the API.

Andreas

-- 
You fill a much-needed gap.




More information about the KDevelop-devel mailing list