[Kst] kst2 problems...

[Brisset, Nicolas]

I can't really help you with the details here, all I can say is:
- we use the datasource config stuff very often (especially with ASCII)
- something I had in mind when I did the first prototype (which George
then improved heavily :-)) and which was never implemented would be to
remember extension <-> settings so that we can switch settings from a
combobox. It is not high priority, though as long as saving/loading
remembers the settings for each datasource as it currently does...  
- even in the 1.x series, configuring the datasource from the first
datawizard page does not always work. I forgot the scenario but there
are cases when you'd run into problems. I think it happens if you come
back to the first page after you create a datasource instance, e.g. if
you see only numbers in the list of fields when you expected to see
names. I believe the datasource does not get destroyed and reconstructed
with the new settings, but that needs to be checked. I guess this is
pretty complex to implement properly...

> I'd like to get this working, but wondering about the best approach.
> 
> In 1.4 the datasources expected the application to pass a 
> KConfig object when loading the config widget.
> 
> For portto4 I'd like to explore the plugins themselves being 
> responsible for managing their settings object.  However, 
> maybe this is not possible...
> 
> Is it true for 1.4 that the settings object passed to the 
> datasource plugin was particular to the session you were running?
> 
> Adam
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
> 
>