Python based extensions and Qt6

[Juraj Oravec]

Hello Schimon

> I will look into your documentations;
> I think I will start with buku.

Feel free to ask me if you need help with it, I will try to look into 
it.

> P.S. Do you we need to update extensions manually or is there an
> update checker mechanism?

I dont think there is any update mechanism for extensions at the moment.

Best regards,
Juraj


On piatok 17. mája 2024 7:24:29 SELČ you wrote:
> Good day Juraj,
> 
> I will look into your documentations;
> I think I will start with buku.
> 
> Thank you,
> Schimon
> 
> P.S. Do you we need to update extensions manually or is there an
> update checker mechanism?
> 
> > Hello Schimon,
> > 
> > > Python extensions do not work since the Qt6 interface of Falkon.
> > 
> > Python support works properly for Falkon 24.02 based on Qt6.
> > There are python based extensions in Falkon source code working
> > fine.
> > 
> > What is broken is that python module names and some Qt related stuff
> > changed in the transition to Qt6, which means that third party
> > extensions mostly from store.falkon.org need to be adjusted to the
> > changes.
> > 
> > > I want to write a couple of new extensions for Falkon:
> > > 
> > > Bookmarks management with buku.
> > > Profile synchronization via XMPP with slixmpp.
> > > 
> > > Please advise,
> > 
> > Since both of these extensions wants to call external commands I
> > would recommend using Python or C++ for the plugin integration. I do
> > not think this can be done from within Falkon QML API support.
> > 
> > I do not think there is any "API" like thing to tap into to do this.
> > YOu most probably would need to dive into the source code for the
> > related information, signals, slots, database stuff.
> > 
> > Regarding Profile synchronization, I would start by specifying what
> > should be synced, like history, open tabs, pinned tabs, open
> > windows,
> > history, falkon configuration, website settings, installed/enabled
> > extensions.
> > 
> > For most of these you would need to tap directly into the code, read
> > the configuration file or the database.
> > 
> > I believe, the bst is to tackle this one by one.
> > 
> > Also I intend to mess it up a bit for 24.08 release with some per
> > site configuration.
> > 
> > > Schimon
> > 
> > Best regards,
> > Juraj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/falkon/attachments/20240517/cf1f7d29/attachment.sig>