[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: DocBook DTD/ KDE 2.0 documentation
From:       Matthias Elter <me () kde ! org>
Date:       1999-04-01 8:11:58
[Download RAW message or body]

On Mon, 29 Mar 1999, Stefan Westerfeld wrote:
> Hi!
> 
> On Mon, Mar 29, 1999 at 10:47:43AM +0200, Matthias Elter wrote:
> > [...]
> > What we need is your
> > feedback and ideas for a new docu system. What features do you want to see,
> > what do you think is important. We especially need feedback from the
> > translators what problems they have with the current system and what they think
> > should be improved.
> 
> What would be especially important for me would be that you can have context
> sensitive help. Arts (the synthesizer I am writing) has about 25 filter
> modules, and right-click/Help on a module would be much better than the
> current style (having all 25 modules in one section of the SGML).

There will be context sensitive help but we are not 100% sure on how to do
this, yet.

> Another point is plugins. Suppose you had modules which you could add as
> plugins, where would their help come from? I mean, it should seamlessy
> integrate in that collapsable treeview someone mentioned, and in the
> context sensitive help.
> 
> Think of gimp's plugins. They currently provide no help at all (despite
> a few lines description in the PDB), and there is IMHO no way of doing
> so in a sensible way. The few lines in the PDB are as far as I think also
> not translatable, I suppose they are somewhere in the code, and that's
> it.
> 
> With all those KOffice plugins and component technology one certainly
> should at least think whether a new help system could support this from
> the beginning.

I don't understand the problem. Plugins are executables and you will be able to
call the help functions from your plugins the same way as you would do it in a
normal program.

Greetings,
Matthias

[prev in list] [next in list] [prev in thread] [next in thread]