To get the new driver to be returned in that call, you just need to put the
correct info in the .desktop file. This file is what is used to loop-up
the drivers. See
http://techbase.kde.org/Development/Tutorials/Services/Traders . Make sure
you install the .desktop file in the correct place and it should get found.
Adam
On Mon, May 26, 2014 at 2:36 PM, Harshi Mistry <harshimis...@gmail.com>wrote:
> Hi,
>
> I need some help in understading how I will inherit KexiMigrate for
> OdbMigrate and how will it show up in importTableWizard.
> As I could understand, I will have to implement following driver-specific
> virtual functions in OdbMigrate class.
>
> bool drv_connect()
> bool drv_disconnect()
> bool drv_tableNames(QStringList& tablenames)
> bool drv_readTableSchema(const QString& originalName,KexiDB::TableSchema&
> tableSchema)
>
> I am also not sure if I should implement drv_queryMaxNumber(),
> drv_queryStringListFromSQL() functions, which should only be implemented if
> database can already contain kexidb_* tables. I did not understand this.
>
> I have also noticed that in MigrateManager class there is a function
> lookupDrivers(), which uses following function call to get list of drivers.
> This list is used in importTableWizard user interface in a dropdown menu of
> mime-types.
> KService::List tlist =
> KServiceTypeTrader::self()->query("Kexi/MigrationDriver");
> I don't understand what extra I have to do than inheriting KexiMigrate for
> OdbMigrate, to get OdbMigrate in the result of this function call.
>
> Thanks,
> Harshita
>
>
>
>
> _______________________________________________
> calligra-devel mailing list
> calligra-devel@kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
>
>
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
