Christian Ridderström wrote:
> Ok, that (sort of) explains why I have four more options in my
> 1.3.2-xforms version then? This means the documentation should say
> something like:
>
>         To modify the preamble open Layout->Premable (Xforms-version) or
>         open Layout->Document->Preamble (Qt-version).

Yes (unfortunately). I don't know if there are still plans to move the xforms 
preamble to the document dialog too, but there are still the differences 
between the (more fine grained) qt panes in QDocument and the tabfolders in 
in xforms. This will not change I suspect. 

But thinking about it, I think that the branches feature (the one Martin is 
currently developping) could be useful in the future. We could use a branch 
for each frontend in the documentation and put the frontend specific 
statements into a branch inset. That would be o.k. as a visual clue on 
screen, and for printing, only the relevant frontend could be chosen.
This is of course still bit of a pain for the documentation team, but I think 
it's less pain than always using those if-then-else sentences that'll blow 
the docs.

> Sigh.. If there aren't too many differences like this, it might work but
> would be a bit tedious. Do you think the menus will stay "identical" in
> the future?

I think there will be a common base but there might be more and more frontend 
specific issues. We should take care that the differences are not too big, 
but if you look at the QT/Mac frontend, you'll see that we cannot even decide 
this in any case.

> I guess the default keyboard binding is also not specific to the frontend.

Right. They are bound to lfuns. The bindings inside the dialogs are defined 
per frontend, though.

> So we're only left with specify the location within a dialog.. hmm, do we
> know that the dialogs will actually contain the same thing?

Only by comparing. Actually, quite a number of "redundant" functions from 
xforms have disappeared in qt. We have to live with compromises.

> Does anybody know of another program that is GUI independent, and how
> their documentation handles it?

No. But I think the branches way is worth considering. Waht do you think?

Regards,
Juergen.

Reply via email to