Re: [Gramps-devel] print button on fanchart

[Benny M. <ben...@gm...>]

2012/9/2 Brian Matherly <br...@gr...>

> >>What if all Views had a Print button (on menu and in toolbar)? Then
>
> >>each View instance could either handle the print request themselves,
> >>or could have an associated regular Document-based report that best
> >>displays the same information. I think there is a feature request for
> >>this already, and if a View could handle the Print request directly,
> >>then we wouldn't need to do anything else.
> >>
> >
> >An option indeed. The print button is not the problem of course, it just
> means pageview.py needs a callback for it and ui definition, which I now
> only add for fanchart.
> >
> >For fanchart the print must be handled by itself as user can rotate,
> expand a node, ...
> >
> >One problem to overcome is the difference between config settings of
> views and reports. In gramplets you use the report settings for the config
> setting. I can't really figure out easily how to do this for views also.
> You will see I factored out the code used by the fanchart gramplet and the
> fanchart view, but the config is only in the view, while it would be nice
> to have a single API that can be reused by gramplet and view. This would
> then perhaps also enable in the config of a view to show the print section
> of the report option dialog. This could then drive what the print button
> does on a view.
> I like this idea a lot (all views have a print button). I think that
> adding another document generator type might cause a lot of confusion.
> Right now, we have four report types: Text, Draw and Graph. I think it is
> already confusing that you can't use Graph reports in the book report.
> Normal users just can't appreciate that the graph reports use graphiz in
> the background and can't be exported to native openoffice constructs. Also,
> I think it would be confusing to have two different fan reports (one using
> drawdoc that can be in a book report and one using canvas which can't be in
> a book report).
>
> But having a separate system that allows all views to be printed would not
> be confusing since it wouldn't be associated with the report menu. Also,
> people would be more forgiving if, for example, printing one of the views
> causes a button to be printed.
>

Ok, so if we make pygoocanvas an official view, we can move the graphviz
reports to there I suppose. Have never used pygoocanvas myself.
Perhaps you can have a look at the config settings of views, eg the
fanchartview.py, to see how we could use the system of reports and
gramplets.

Benny

>
> ~BM
>
>