ScrambleBook and Calibre 4

[jackie_w]

I hope you haven't wasted any time on this yet. I think I may know what's wrong.

[kovidgoyal]

In The plugin you have a separate ui.py. All is needs to do is run

self.gui.job_manager.launch_gui_app('webengine-dialog', {'module':  'calibre_plugins_your_plugin_import_name.main',  'path': path_to_book})

Then in the main.py file have a function named

def main(path_to_book):

this can run the actual plugin with the webengine based UI

[jackie_w]

Originally Posted by kovidgoyal

@jackie here is a demo plugin that shows you how to run webengine in a separate process. Note that it only works with calibre version >= 3.99.4 which will be released in an hour or so. No need to mess around with calibre-debug anymore.

When its button is clicked it asks for a URL and then opens that in a QwebEngineView

Sorry I've only just seen your new post. Thanks for taking the time to write this

Are you suggesting I do this rather than eschwartz's cli_main() method?

Whatever the answer I will be experimenting with your new demo in case I need a QWebEngineView widget in a future UI plugin.

ETA: Oops! Cross-posted.

[kovidgoyal]

Feel free to use either, whichever works better for you.

[jackie_w]

Originally Posted by kovidgoyal

Feel free to use either, whichever works better for you.

OK, will do. It's 3am so I'd better get some sleep and come back to it tomorrow.

[jackie_w]

Originally Posted by kovidgoyal

In The plugin you have a separate ui.py. All is needs to do is run

self.gui.job_manager.launch_gui_app('webengine-dialog', {'module':  'calibre_plugins_your_plugin_import_name.main',  'path': path_to_book})

Then in the main.py file have a function named

def main(path_to_book):

this can run the actual plugin with the webengine based UI

It's working, let joy be unconfined! I decided to use a hybrid solution which uses eschwartz's cli method if running standalone and your new 3.99.4 method when running from the calibre GUI.

I'd like to clarify something about the latter.

In the show_dialog called by genesis() I have

self.gui.job_manager.launch_gui_app('webengine-dialog',
    kwargs={
        'module':'calibre_plugins.scrambleebook_plugin.main',
        'path_to_ebook':path_to_ebook,
        'book_id':book_id,
        'from_calibre':True
        }
    )

and a separate main.py file in the plugin containing only a single function

def main(path_to_ebook, book_id, from_calibre)

Are the 2 red names constant or can you choose your own. I'm assuming they are constant?

[kovidgoyal]

webengine-dialog is constant, you can override main, like this:

self.gui.job_manager.launch_gui_app('webengine-dialog',
    kwargs={
        'module':'calibre_plugins.scrambleebook_plugin.main',
        'func': 'some_name',
        'path_to_ebook':path_to_ebook,
        'book_id':book_id,
        'from_calibre':True
        }
    )

then replace main with some_name

[jackie_w]

Thanks for the info.

Many thanks to both you and eschwartz for your patience nursing me through this

[eschwartz]

Great, cool!

My rationale for tilting you at the run-plugin method is because you know, when all you have is a hammer, everything looks like a nail. But I like CLI interfaces, and it surely cannot hurt to have one (and it might come in handy for some people). So why not add both methods, indeed...

[eschwartz]

BTW I noticed when testing the standalone version of ScrambleEbook, that the gui window for the preview was appearing behind the main ScrambleEbook dialog. This occurred regardless of whether I ran calibre-debug scrambleebook.py, or whether I used my modified plugin with the cli_main method. I believe you need to raise() it.

[jackie_w]

Originally Posted by eschwartz

BTW I noticed when testing the standalone version of ScrambleEbook, that the gui window for the preview was appearing behind the main ScrambleEbook dialog. This occurred regardless of whether I ran calibre-debug scrambleebook.py, or whether I used my modified plugin with the cli_main method. I believe you need to raise() it.

I didn't see this at all during testing. Is is a Win vs. Linux thing do you think?

Don't laugh but in my several years of dabbling with this GUI stuff I've never once coded a .raise_(). I noticed it was there in both your cli main.py and Kovid's run-as-extra-process main.py, so obviously I kept them in.

However, both main.py's are for calling the main parent dialog and I think you're talking about the child dialogs activated by a pushbutton. At the moment all of these are currently coded as 2-liners, e.g.

dlg = EbookScramblePreviewDlg(args)
dlg.exec_()

Are you suggesting this would fix the problem?

dlg = EbookScramblePreviewDlg(args)
dlg.exec_()
dlg.raise_()