Quote:

Would be kind of cool though...

Quote:

Yes of course - what else? A dancing banana? A facepalming Cp. Picard?

Quote:

What I wrote. But a good share of MorphOS is uniqueness is about keeping control of the machine. Hence my suggestion to make this behaviour selectable which is probably not a biggie...

Quote:

Just curious, what would you like to happen with non-URL’s if *not* passed on to a search engine? An error message?

I think this has become a standard feature that is kind of expected in a modern web browser.

Some times there could be local network services that obviously does not resolves through a top-level domain “dot” domain. At work we have network printer configurations and other stuff handled through a web interface on the LAN this way. Also common for NAS machines as well as routers etc. But most browsers handles this just fine if you just type in http:// or https:// and personally I’m fine with that.

Quote:

Albeit I know this feature is nowadays ubiquitous (and indeed very handy!), I don't like it too much.
Hence i hope that behaviour will become selectable (option to pass on non url matching inputs to seach engine of choice/duckduckgo.com or not).

But I think it's a good feauture as most ppl know it from other systems (and it's indeed handy).


[ Editiert durch Zylesea 20.09.2020 - 16:27 ]

Quote:
Au contraire, typing in "chickens" is being correctly identified as a search term as opposed to a web address, thus correctly and conveniently triggers an internet search.

@ jacadcaps -> Is this a ...

1. What came first the chicken or the browser question?
2. A duckduckgo search for backyard chickens question?
3. What's our opinion of duckduckgo as a new search engine in Wayfarer additional to other search engines question?
4. Some other statement or observation that is too obtuse to work out if it's a question ... or not?

I don't get it. Chickens break your browser?

Chickens anyone?

Wow, you are truly amazing!

@ jacadcaps - . . . . {I'm virtually speechless ... in speech-bubbles }

No news for a while doesn't mean that lot is isn't happening in the project:

I've fixed several crashes inside WebCore that would hurt when browsing in low-memory situations. Implemented the MemoryPressureHandler which is basically a watchdog that can flush WebCore's caches on low memory. Figured some compilation settings that reduced the binary size by about 8MB. Made ftp and mailto delegate to the default apps configured in OpenURL. Figured out how to setup the default CSS so that checkmarks and radios are drawn if the website doesn't override those in its CSS. Added more settings to Wayfarer - it's now possible to control interpolation quality when scaling images (this has big impact on speed on slower machines).

Also, bubbles!

That's not something I'm willing to work on - but anyone is free to come forward and write scripts to do just that :) Already spoke to one of the betatesters about this.

@ jacadcaps - Thanks for the replies to my queries, as usual answered comprehensively and timely.

Forgot to ask, if Bookmarks can be imported as a whole .HTML or .JSON file from other browsers, including OWB, Firefox/TenFourFox, etc.?

[ Edited by NewSense 03.09.2020 - 01:22 ]

Quote:

It saves RAM/CPU by killing the underlying browser object.

Quote:

Post 3.14.

Quote:

Support for plug-ins isn't planned. Flash is dead anyway.

Quote:

So far I have not seen issues like this and none have been reported to me. This is a vastly newer WebKit and Apple is generally trying to keep some reins on JS - since it has to work on low-end iPhones. That said, there's still room for improvement.

Quote:

Bigfoot has shared his JIT code, but the JavaScriptCore has diverged quite a bit and it won't merge without significant amount of work. Might take a look at this at a later stage.

Quote:

Wayfarer binary is coming close to 80MB, so I'd estimate it needs about 128MB free RAM to start. Adding tabs is relatively cheap, but obviously depends on how heavy the websites are.

Quote:

Perhaps at a later stage.

Flash should've been killed 10 years ago. They are way too late, but thats still better than never

Quote:
Adobe announced back in 2017 that Flash has reached end of life status and all download options will be removed from their website by the end of 2020.

Consequently, all major browser vendors have also announced plans to remove Flash support some time this year.

So what benefit does the "hibernate Tab" context menu option offer, i.e. RAM released? Or is it more of a 'gimmick'/fun feature? Thanks for your additional work on Wayfarer to accomplish this.

Any further along with audio/video implementation, or is that going to be addressed at a later stage in development?

Is the implementation we use of "flashplayer" likely to see any improvement for Wayfarer?

By the way, is it possible to have realised by now if there now likely to be a 'fix' in Wayfarer for the RAM lock we suffer from, with OWB, due to the JavaScript tying up valuable RAM and not getting released until the browser is quit?

Is a JIT JavaScript engine likely to be a feature, to keep our PPC CPU overheads to a minimum?

How much base RAM is required to load up Wayfarer, and how much RAM is generally required for each additional Tab that is activated, if you have an amount you can average out?

I mean if a MacMini has a max of 1GB, then how much RAM is going to be required to get it started, and any subsequent Tabs, and is the RAM 'lock' still an issue to be borne in mind?

Will there be an editable QuickLinks feature for bookmarks in Wayfarer, as I haven't noticed much of that featured in the screengrabs so far? I know there is a screengrab on thread #127 which shows a few quicklinks, but will this be as complete a feature as it is in OWB, as I find it handy having the webpage mini-logo on the button(s).

I can tell you're busy, so by all means answer these questions when you've got more time to do so ... if that's ever going to be likely!

Quote:

I like experimenting to see how far I can take such things with MUI. Have also found it very irritating OWB has so many windows - I already have a ton of other windows opened when I'm working, so having a browser on one helps me streamline how I work on MorphOS (never been a fan of separate screens). Anyway, you can always popup a new window with just the settings tab if that works for you.

Quote:

Not sure if Wayfarer will end up on 3.14 ISO, but it will be made public on the day 3.14 is out.

> the settings/Prefs load into a Tab, rather than as a MUI Window - is that correct?

Yes, see his comment #153.

> [...] what I assume is the browser identifier

User agent (string) is the general term for this, as used in the Wayfarer settings.

So the settings/Prefs load into a Tab, rather than as a MUI Window - is that correct?

If so, was that a specific decision to choose that way?

Many browsers opt for this "Tab" approach it seems, like Firefox, though I do like the separate MUI window as a separate entity that gets loaded to change the prefs with OWB, and previous Amiga-like browsers did historically.

However, I can easily get used to this way as it is a much more common approach, and if we get any newer users then they would probably expect the browser to load Options/Prefs in this way.

Any success or in-roads into getting audio and video implemented as yet?

Thanks for the screenshot of your considerable work, and thanks for the work itself, you are amazing at the efficiency level you seem to work at!

I did notice the "MorphOS; PowerPC 3_14" in what I assume is the browser identifier. So, is that what you are aiming for - a release of a useable version of Wayfarer in MorphOS v3.14?

Some new settings. Did a little bit of tweaking in WebCore to enable throttling - which basically means lowering refresh frame rates and DOM timer frequencies. This should help reduce CPU usage on heavier websites. I've also added basic Arexx support so that Wayfarer can be set as default web browser.

Looking good. I cant wait to try it out!

Took some time to re-write the drawing code. Odyssey would normally repaint whenever WebCore requested an update, while my old code aggregated WebCore changes into a biggest common rectangle. The new code splits the visible area into 64x64 tiles (just like Enhanced Display, by the way). This is very efficient when dealing with multiple damaged areas in one redraw pass. This has also let me use ScrollWindowRaster for vertical scrolling, greatly improving scroll's performance.

Also, figured I may as well enable sub-pixel antialias...

Quote:

Well that is good to hear, that the maintenance won't be a big burden for you and any others that offer to help you. It's a bit surprising to read that, as I thought maintaining a web browser, with the constant changes that keep happening, would be more difficult and time consuming. I'm also glad to see that you have mentioned the specific area you could use some help with, as that increases the chances of finding someone to help out (chances have now gone from 0.5% chance of finding anyone, to 1.5% chance of finding helpers). I wish I had the programming skills to provide help with this or any other part of MorphOS development, but by the time my programming skills get anywhere near yours, I'll be so old I won't be able to remember what I did 15 minutes ago (hmmm, what did I do 15 minutes ago???). I was asked to help with documentation for MorphOS years ago, but not having any previous experience with how to document software, I failed to even understand what was being asked of me.

Thanks again for all the work you have done and continue to do on this and all other MorphOS development. I'll send more pizza and beer money when I can.