>> This doesn't remove the use of the nifty KDE print dialog, does it?
>So this change looks very wrong to me.

Solution

class KReportViewer: public MReportViewer
{
public:
	void printReport(); // this method will use KPrinter, it  also can be virtual
}

Kugar Shell should use KReportViewer. So, MReportViewer will remail
qt-only and KPrinter will be used where it is expected to be used.


Further Kugar engine plans:
add database support strict into report engine (using qt database classes)

I think of following structures (this is a draft of my thoughts):

<DataSource Name="" ParentName="" Driver="" Database="" HostName="" Port=""
			Query="" Username="" Password="">
	<DataField X="" Y="" ... />
	<Label ... />
</DataSource>

<DataDetail Height="" DataSource="">
</DataDetail>

DataSource will not be printed. DataDetail will be printed according to it's
location in report template (after another details, between them or before
them).

To supply passwords for data sources in runtime there should be
specialized classes. That classes can be passed to report engine
in creation via MReportViewer's constructor and used further when 
accessing the database. So passwords will not be used in templates.
ParentName in DataSource definition can point to a master datasource,
so we can simply establish master-detail-subdetail-... relationtips
and automatically arrange details while printing.

Those are only additions to report engine. They will not break an idea
of using data files, independed from data storage. I want just to add 
some new (optional) functionality.

Awaiting for your comments.

WBR, Alexander Dymo
Ukrainian State Maritime Technical University
cloudtemple@mskat.net
http://www.cloudtemple.mksat.net

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel