On 26 May 2014 15:36, Harshi Mistry wrote:
>
> 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.
>
> boo
On 26 May 2014 19:52, Adam Pigg wrote:
> 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 instal
> On March 23, 2014, 10:51 p.m., Yue Liu wrote:
> > do you still have the gmic clang issue?
>
> RJVB Bertin wrote:
> On OSX 10.6, yes. But there one could choose to use a recent gcc version.
>
> I cannot test on the intermediate OS versions, but on OS X 10.9 the
> situation is a bi
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
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_table
Hi!
I am currently working on making AppStream metadata available for KDE
(see[1] and [2] for more information).
Adding that data will make Calligra applications visible in software
centers and give you translated descriptions of the respective
applications.
Is it okay if I push the missing metadat
