GTK3 - WLX - hx_webkit_gtk3_crap

[advice2020]

My original plan was to use the wlxwebkit_gtk plugin for viewing both mhtml and pdf files.
Due to this plugin currently containing issue where some mhtml files open up blank/show the previously loaded mhtml page viewed, I saw Skif-off mention he used the hx_webkit plugin to solve this issue instead.

Am I correct that this is the hx_webkit_gtk3_crap plugins name you guys were referring to?

The complie seems to build without errors, but this plugin did not work for me.
The Detect String is blank
I copied the one string from wlxwebkit_gtk plugin where I also added mhtml and pdf
But for me it just shows mhtml files as text files.
Is this the type of plugin user should leave the Detect String field blank and it handles it somewhere within the makefile?
I only saw the "detect string = " line in that file

Is this plugin capable of viewing mhtml and pdf files?
If so could someone tell me how to assign these MIME types?

Thank You

[Skif-off]

What about

download HTML Export (hx-x-x-x-linux-x86-64.zip)
extract archive and...

so on?

[j2969719]

as i wrote earlier, think twice before using plugins with my favorite suffix in the name, because it means something stupid is going on there. in this particular case, this plugin will attempt to convert the viewed file to html using the sample executable file supplied with outsidein html export from redist dir and display the result if successful.

regarding the detectstring: the converter supports many file types, such as documents/spreadsheets/images etc. (the archive from the oracle website in /sdk/samplefiles also contains some files for testing) and you may not need them all be converted to html. detectstring like EXT="MTH"|EXT="DOC" will call this plugin only for these extensions, while EXT!="GIF"&EXT!="PNG" will call for all but these. an empty detectstring (default) will call the plugin for all files

[advice2020]

@Skif-off
Ahh I did not go through that file, I was focusing on the build dependency page at the time, did not realize there was more stuff that was needed. That site would not let me download anything anyways, said I would need an account? Not sure if this one is worth because as j2969719 said, it is "crap" :)

@j2969719
Okay okay, well a little context, you often refer to your stuff as "crap" but then you also use this suffix when a plugins dependency/application does not work well with the WLX plugin format. For example, at one time you had originally named the mpv_alt plugin mpv_crap and that plugin is amazing, so I asked you to reconsider renaming it, which you did :)
So I just have to be sure with each plugin, so I might have to ask every now and then.
Also, I was just testing this "crap" plugin :) because Skif mentioned he had success and appeared to be a solution for him for webpages, which made me think, hey maybe this one is not "crap" :)

Anyways, now this is a little unfortunate, because at least for me I do not have a solution for a mhtml viewer.
hx_webkit_gtk3_crap
In certain areas I am trying to limit the amount of setup steps needed for things as much as possible. So probably going to try to avoid this one if possible.

wlxwebkit_gtk3
Would like to be able to use this one, it works, but as we have all discussed, this plugin experiences blank pages / showing previous pages content so a little unreliable.
Also I believe I heard that GTK3 is not being developed any further, I think only security fixes so I do not think this gtk webkit is going to receive fixes for blank page/previous page issue, so this will never be able to be fixed either.
Was nice that this one also included pdf viewer in same plugin.

Anyone aware of any other options?
Firefox based browsers do not support mhtml but Chromium based browsers do. Is there maybe by any chance some kind of Chromium based "API" that a WLX plugin can be made from? It was mentioned in the past that the QT webengine plugin was a Chromium based plugin, is that because maybe the QT "webkit" is designed to use it? or could it be used for GTK3 based plugins?

GTK3
Because my DE is GTK based I was hoping to finally stop having to use QT version of DC, but I do not think that is going to be possible.
Was hoping to just be able to use the GTK3 beta + GTK3 plugins but might be too early for me. Also I have been told that most of the DC GTK3 issues I am experiencing are Lazarus based so I am sure how their development process is handled/how quickly they are able to fix bugs.

QT DC is stable and QT WLX plugins are amazing (I knew these were going to be tough to compete with) so probably going to have to use, at least for now.

Any of you guys trying to use the GTK3 version as your main version? Or are you guys just testing things out for now as well?

Thank you guys again for the responses

[j2969719]

outsidein has almost filled the bingo of proprietary software: account, elua, and regional download blocks, if remember correctly

dunno if theres a python module that can parse problematic mht files, then it could be used in the gtk_socket_tst script

as i wrote in another thread, gtk3 support in lazarus is a bit off from ideal, and existing dc builds are more for adventureseeking enthusiasts atm

[advice2020]

Thank you for response.
-Yeah okay so definitely not using that.

-Is the "Python module" you are referring to, to fix the wlxwebkit_gtk3 mhtml blank page issue?
You mentioned gtk_socket was not ideal to be used / also would Python be slow in combination with gtk_socket approach?

-How does the gtk_socket_tst plugin differ from the original gtk_socket plugin?

-I saw your response about my Chromium based webengine question, yes that is what I was referring to.
So Chromium offers some kind of "API", and then QT creates a library/kit that uses Chromium API, making it available to QT based applications/plugins.
GTK webkit does not use Chromium API for its "kit".
I know it probably does not work this way but, yeah I was just wondering if there was any hope that maybe Chromium API could somehow be used + GTK3 to create a WLX plugin.
That was the hope, but am I correct in saying that this is not possible, would have to be built into a GTK3 supported webkit in order to be used in this WLX plugin context?

-I know, I read what you mentioned about GTK3, it is just that the adventure that I was seeking was to have the GTK3 version work perfectly so I can use it, right now :)

Thanks again