Change in behaviour

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Change in behaviour

Adam Pigg-2
Hi

In the old (2.x) days, there was a 'feature' where if no data source was selected for a report, Kexi would generate a special data source with 1 record.  This was useful for single page reports with either static data, or script generated data.

In 3.x, we changed this to move the 'hack' into Kreport, with a new data source type OneRecordDataSource, which is used if no other data source is set.

This works fine, except for one thing.....the list of scripts in the project is supplied by the data source.  As we now dont set a data source from kexi all the time, and instead rely on kreport when no data source is set, we have lost the ability to have 'no data source' but still have access to kexi scripts.

Thoughts/way forward?

Adam
Reply | Threaded
Open this post in threaded view
|

Re: Change in behaviour

Adam Pigg-2
Im thinking....remove the script list from KReportDataSource, as really its just been tacked-on, and set it directly from Kexi, probably in KexiReportDesigner.  It will be an API change, but before 3.1 is best.

On Mon, 29 May 2017 at 21:35 Adam Pigg <[hidden email]> wrote:
Hi

In the old (2.x) days, there was a 'feature' where if no data source was selected for a report, Kexi would generate a special data source with 1 record.  This was useful for single page reports with either static data, or script generated data.

In 3.x, we changed this to move the 'hack' into Kreport, with a new data source type OneRecordDataSource, which is used if no other data source is set.

This works fine, except for one thing.....the list of scripts in the project is supplied by the data source.  As we now dont set a data source from kexi all the time, and instead rely on kreport when no data source is set, we have lost the ability to have 'no data source' but still have access to kexi scripts.

Thoughts/way forward?

Adam
Reply | Threaded
Open this post in threaded view
|

Re: Change in behaviour

Jaroslaw Staniek-3
On 29 May 2017 at 23:01, Adam Pigg <[hidden email]> wrote:
> Im thinking....remove the script list from KReportDataSource, as really its
> just been tacked-on, and set it directly from Kexi, probably in
> KexiReportDesigner.  It will be an API change, but before 3.1 is best.
>

Looks fine, thanks Adam

> On Mon, 29 May 2017 at 21:35 Adam Pigg <[hidden email]> wrote:
>>
>> Hi
>>
>> In the old (2.x) days, there was a 'feature' where if no data source was
>> selected for a report, Kexi would generate a special data source with 1
>> record.  This was useful for single page reports with either static data, or
>> script generated data.
>>
>> In 3.x, we changed this to move the 'hack' into Kreport, with a new data
>> source type OneRecordDataSource, which is used if no other data source is
>> set.
>>
>> This works fine, except for one thing.....the list of scripts in the
>> project is supplied by the data source.  As we now dont set a data source
>> from kexi all the time, and instead rely on kreport when no data source is
>> set, we have lost the ability to have 'no data source' but still have access
>> to kexi scripts.

>>
>> Thoughts/way forward?
>>
>> Adam



--
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek