@ jacadcaps - thanks for explaining in more detail the functionality and use of the 'Script Manager', which I really appreciate you taking more of your valuable time to answer my questions. It certainly sounds like its functionality should be made good use of.

Quote:

The User Script manager had been part of Wayfarer since version 1.5. That's how the Edura inspector was added.

Quote:

Yes. Basically both lists being empty means "load on every site". Putting anything on White List means "only load on matching sites" while putting anything on Black List means "load on sites except...".

Quote:

That looks correct, yes.

Quote:

Once you get a script to work including white/black, etc you can export all of those settings incuding the script itself into one JSON file which you can then distribute on MorphOS Storage or whatever. It simpy bundles the JS script with its settings as one file, while Import unpacks those.

Quote:

I have no idea - I would imagine they are outdated.

Quote:

I'll write up a FAQ, eventually :) I have zero interest in creating or maintaining any user scripts for Wayfarer at least, but I'll try to support anyone who would want to create one.

@ jacadcaps - so what scripts currently have been tested with the introduction of this User Scripts Manager that originated with OWB/Odyssey in MorphOS?

As a reference, the YouTube.js script that was originally intended for OWB/Odyssey seems to be correctly installed by the way I explained I did it in my previous comment #1263, and seems to be confirmed as being the correct method by you in your comments above - though there is still no mention of which parameters might need to be used/added.

However, if you have gone to all this trouble to implement this 'script manager', then surely to ensure it works in the way you want it to you used a script to test it does what you intend it to do, so to what extent did you test this feature out?

You mentioned the OWB/Odyssey script manager specifically so surely those scripts were considered or tried to see what happened when they were added, so were they tested to see how they reacted, or was some other script tested?

I take it the 'White List' is the equivalent to the 'Allowed Sites' of OWB's script's window, and the 'Black List' is the equivalent to the 'Forbidden Sites' of OWB's script's window, so parameters for the scrips to work seem to be needed to be added into those sections additionally for the script to function as intended, so for the YouTube.js script the additional 'Allowed Sites' parameters of:

https://youtube.com/watch*
https://*.youtube.com/watch*
https://youtube.*/watch*
https://youtube-nocookie.com/watch*
https://youtube-nocookie.*/watch*
https://*.youtube.com/user/*

. . . also would then need to be added individually into the 'White List', is that correct?

Originally the parameters of the script were "http" based, but I have not added them as they would seem to be irrelevant in any case these days.

In what way would the Import/Export options deal with Wayfarer's json format? How would these options be used/useful to an everyday MorphOS user?

I am just trying to figure out how useful the OWB scripts that FAB made available to us all, are still likely to be useful, even if they need to be 'tweaked' in Wayfarer, in this Script Manager you have now developed/added into your program.

As I mentioned above, it seems to me, that a 'one liner' stating that there is now a 'Script Manager' in Wayfarer doesn't really explain its usefulness or method of using it fully to me, and probably many others.

So, I'm just asking for some clarification on what you intended it to be used for, seeing as you mentioned the OWB scripts in the first place, even though you state that . . . Quote: Why not - were the original OWB scripts not tested at all, or are you, or someone else, intending to supply some useful 'known to be working/functional' scripts to use with Wayfarer, to make the Script Manager actually useful?

@NewSense

Basically all you need to do is to Add a new script, then select the file via the Path popup button and hit Apply. Import/Export only deal with Wayfarer's json format.

Of course, whether a script adapted for OWB will work or not I cannot say. It should be possible to debug those in the WebInspector.

Quote:
So, how do the scripts get imported, and where from these days?

If I try to import, for example, the YouTube_EZDownload.js script clicking on the import option brings up a requester, but the script file is not recognised in the requester, nor can it be typed into the input field and imported that way either, as the whole scripts GUI remains basically blank. Having checked for a bit longer though I also noticed the Add option in the top section of that Script GUI and then realised by doing that there is a 'tiny' system gadget 'unghosted' to click on to find a file within the system HDDs and directories, and then the script can be selected, but even once that is added and then "Apply"-d, then the script is shown in the top section of the GUI but initiaily it didn't seem to do anything, but eventually a bottom-right-side menu is generated, but is this the correct way to use it/them, or is there some other way to import/recognise the script files?

The script files as an archive doesn't seem to be on MorphOS-Storage to download?

Though I can see that some of them are still on FAB's OWB Script folder, but some of them don't seem to be on there, and I can't remember where I got the rest of them from that worked with OWB originally anyway, though it could have been via Grunch, which doesn't seem to do what it "says on the tin" as it is still http: only I believe, so cannot access some sites (https:) where files are/were hosted.

Though there are some instructions on Wayfarer's FAQ page for some features of Wayfarer that might seem to need some instructions as to how to set them up, there is no information on how these newly implemented Scripts options are supposed to work, which would be very helpful if such instructions were added.

Thanks a lot jacadcaps !!!

Excellent idea the cookies in ram:

A new major update of Wayfarer has just landed! Version 5.0 brings the WebKit engine to WebKitGTK 2.38.5, released just mid last month.

Wayfarer 5 also introduces the User Scripts Manager known from Odyssey. It's also possible to relocate the cookies database to RAM while running, to reduce the amount of writes to SSD drives and improve performance.

@Blasterreal

That's called Safari ;)

x86_64Bit version added :)

Awesome! What a milestone!

New webkit branch

version 5.0?!?

....Updated WebKitGTK?

Notice something new? :)

Quote:

Thank you !

Thanks jaca!

Thanks once again for your considerable efforts. I feel an 'itch' in my fingers to open my wallet again, as some finances need to fall out in your direction fairly soon.

Wayfarer 4.9 is now out!

- Added a workaround for YT changing quality mid-stream by simply feeding the player video data in different format instead of using the MSE APIs to do this
- Added a workaround for MSE initialization race with seeking for streams not starting at pos=0
- Updated cURL and nghttp2 libraries
- Updated EasyList

Quote:
The Javascript trackers found on exec.pl are used by many other websites.

Quote:
I perfectly understood that the issue only occurs when Wayfarer may be starved for resources.

My proposed test was intended to help figure out if the issue is related to Javascript (said ad trackers).

Quote:
No, I don't use nay adblocks. The problem occurs not only on exec.pl. I often explore this webpage using Wayfarer and everything is ok. The problem occurs sometimes (very rarely) when in background CPU is extremely used.

@MDW

Do you have Adblock enabled? If not, would you mind enabling and trying again?

exec.pl has a boatload of Javascript trackers running in the background. Perhaps there is some relation.

Quote:
It occurs again. Reproduction steps are the same:

1. Start long compilation in FlowStudio with G++11 - CPU usage almost all the time is 100%.
2. Open Wayfarer 4.8.
3. Open morph.zone webpage.
4. Open next tab (Cmd+T) and open exec.pl. :)
5. Progress indication on morph.zone tab stops (about 90%) - webbage is white.
6. Progress indicator on exec.pl is loaded, I can scroll the website.
7. I can't close both tabs but after many many clicks on close button I closed morph.zone tab.
8. Exec tab works normally but I can't close the Wayfarer (Cmd+Q, Quit, close gadget on the window).

On list of tasks in Scout I see:
Code:

If I clicked a link on webpage exec.pl, the Wayfarer crashed. I sent the crash report.

Wetransfer (https://wetransfer.com) has issues again: Transfer won't start. Instead CPU goes most time up to 100%.
Worked definitive 2 weeks ago.....think, they have added too much of this background-crap on their website!

I cannot really say much without you providing any data to back this claim. All prevoius versions can be downloaded from wayfarer.icu/history.

Quote:
No I meant Before 4.7/4.8!

@Jacad: Thank you! Will try it!