Warning: file_get_contents(/home/www/settings/mirror_forum_db_enable_sql): failed to open stream: No such file or directory in /var/www/html/content/Forum/functions.php on line 8
...I had stopped using it because it was difficult to look at. ...
Me too.
The new site feels like being locked in a closet full of concert posters that are so close that you need to back up to focus/read them... but can't.
I scaled the browser to 70%, and it finally didn't feel "oversized".
Doing websites is a lot harder than it seems, and I don't enjoy "attacking" the work of others (who I don't know). I also appreciate that there is some legacy structure that they seem unwilling or unable to update (this forum for one). That said...
The creation of the new site feels like it's being done by someone who hasn't done many of them, and who is making changes without a vision for how the UX should feel. It's disjointed, and has a bunch of unexpected results... clicking takes you to places that you might not expect and don't want to be.
There is just an odd lack of refinement. It's like everything is trial and error. The hamburger navigation for everything went away, and now there is a more random assortment of navigational buttons in the header than there is in the current site? The "auto-popup" scroll-over on the current site is effective. It's been replaced with 7 specific buttons (not menu headers) and 1 rollover sub-menu? It just feels lost.
That's why I think people stopped commenting on the site. When change isn't refinement, are you just wasting your time for something that you can't ultimately influence... so why bother?
__________________________
Separate comment (sorta)....
I think the site needs to figure out what it wants to be. Music server. Chat room. Art gallery. Blog.
For instance, the home page has "Stuff to Read" followed by "Stuff to Inspire". Is the reading not inspirational? When I click on the "Inspire" I still have to read. Stop being so "creative" and tell me what you're asking me to be a part of. Everything is "code". For instance, one of the blocks says: "Take RP online or off. It's free!" That statement makes no sense? It's a link to "Ways to Listen"...which is persistent in the header. It's almost like there are 100 navigational clicks to 10 pages. The page would feel better with blank space there, but every inch is filled (within the confines of the 2612.97Ã1778.77 box they built on the page. The site has no relative scaling, which makes it feel 15+ years old before it goes live.
Back to the beginning....trapped in the maze/closet with no way out.
I don't see a reason to change the site, but I have no idea if there are "bigger" back-end issues that they are looking to address. Ultimately, the only thing that matters is the experience of users, and I don't think that improves with the demonstrated direction of the new site.
I have been using the testing site the last several days and I like that way the channel playlist color looks. Feel like you can see the artists and songs better with the color. It is nice to have the song playlist on the left side. Also really like that the Track section, or what is playing, is still there because I like to see what is currently playing on each channel without having to play anything. It seems much cleaner that the current site. Overall I like the way the site looks and look forward to when it replaces the current site.
Thanks. Yes, if I set the browser to full-screen size (or set the screen zoom to 67% or lower) then the menu is visible in Chrome. Full size for Firefox doesn't show it, but setting the screen zoom to under 70% will show it.
I very seldom set my browsers to full-screen size.
2 things....
- they are obviously working on this now (thus testing.rp)... so last nights comments may no longer be accurate (asking for feedback and then providing none as the "host" isn't a great way to engage a user base...but....)
- The responsive design settings right now are very poorly set. I can go full screen on an 1800 x 1169 MacBook Pro with an XDR display...and I still need to zoom.
Got an expensive laptop? Or a 27'' iMac? Or are you surfing from your new electronic kitchen sink control device, or from your smartwatch?
It burns down to this:
It is a browser-window width issue in the programming of the webpage. If you narrow down the width enough, the hamburger will eventually appear and the menu line will be gone at the same time. Opposite happens if you widen the browser window enough to change what is displayed (again).
When you have the browser in fullscreen mode on your device it becomes a screen-resolution issue of your device. It naturally differs from other devices, as they have other screens, big and small.
Process that, and class dismissed.
(Om Peace Om)
YES! Set the window in Edge and Opera to 90%, the hamburger goes away and the menu appears!
Aye Sire, yes of course.
That is your machine's software emulating some graphic resolution that might not even be within your hardware capabilities.
This can sometimes result in things becoming more or less blurred, especially if hard- and software aren't 100% compatible.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
mannixj wrote:
...
Watching color tv the first time as a kid, I instantly dreamt of smellable tvs! Imagine your favorite cooking show, and you can smell the dishes. Or things not mentioned... I eventually decided to assign less importance to that idea.
Decades later, I found my spirit at the time had been channeling Marshall McLuhan. Or had he been channeling me?
It had been the late sixties.
...
Marshall McLuhan - Understanding Media
The Extensions Of Man
Ch. 1 - The Medium Is The Message ...
Website programming:
The percents differ from screen to screen. Browser window width is traditionally coded in pixels, not in percent.
...we could go deeper into the matter, lol.
Anecdote:
Watching color tv the first time as a kid, I dreamt of smellable tvs! Imagine cooking and you smell it. Or things not mentioned...
Yes, I didn't mean the browser window width or depth (which is in pixels), I meant the "Zoom" settings, which are accessed under the "Settings" drop-down menu. Those are indicated in percentages.
Thanks. Yes, if I set the browser to full-screen size (or set the screen zoom to 67% or lower) then the menu is visible in Chrome. Full size for Firefox doesn't show it, but setting the screen zoom to under 70% will show it.
I very seldom set my browsers to full-screen size.
Website programming:
The percents differ from screen to screen (+ resolution). Browser window width is traditionally coded in pixels, not in percent.
...we could go deeper into the matter, lol.
Anecdote:
Watching color tv the first time as a kid, I instantly dreamt of smellable tvs! Imagine your favorite cooking show, and you can smell the dishes. Or things not mentioned... I eventually decided to assign less importance to that idea.
It is a browser-window width issue in the programming of the webpage. If you narrow down the width enough, the hamburger will eventually appear and the menu line will be gone at the same time. Opposite happens if you widen the browser window enough to change what is displayed (again).
When you have the browser in fullscreen mode on your device it becomes a screen-resolution issue of your device. It naturally differs from other devices, as they have other screens, big and small.
Thanks. Yes, if I set the browser to full-screen size (or set the screen zoom to 67% or lower) then the menu is visible in Chrome. Full size for Firefox doesn't show it, but setting the screen zoom to under 70% will show it.
I very seldom set my browsers to full-screen size.
Yeah, I don't see any menu across the top, just the burger menu at the upper-left. Chrome, Brave, Firefox, Epic browsers. Desktop, Windows 11 O/S.
Got an expensive laptop? Or a 27'' iMac? Or are you surfing from your new electronic kitchen sink control device, or from your smartwatch?
It burns down to this:
It is a browser-window width issue in the programming of the webpage. If you narrow down the width enough, the hamburger will eventually appear and the menu line will be gone at the same time. Opposite happens if you widen the browser window enough to change what is displayed (again).
When you have the browser in fullscreen mode on your device it becomes a screen-resolution issue of your device. It naturally differs from other devices, as they have other screens, big and small.
Nope. Still just the hamburger in both Opera and Edge.
Wow... I sit corrected.
Works for me on Firefox and Zen (my primaries). Failed on Chrome, Safari, and edge.
I decided to ask AI, and came back with this that I'm posting for the dev group (just in case)....
Zen is built on Firefox, so both use Mozilla's Gecko engine. Chrome, Edge, and Safari are all WebKit-derived â Chrome and Edge run Blink (a WebKit fork), and Safari runs WebKit proper. So you're not looking at five different behaviors, you're looking at one: Gecko renders it one way, the WebKit/Blink family renders it another.
That almost always points to a feature that WebKit/Blink supports but Gecko doesn't (or implements differently). The usual suspects:
A -webkit- prefixed CSS property with no standard or Gecko fallback. Things like -webkit-box layout, certain -webkit-mask/-webkit-background-clip: text tricks, or -webkit-font-smoothing silently do nothing in Firefox/Zen. This is the single most common cause.
Scrollbar styling â ::-webkit-scrollbar and friends work in the WebKit/Blink browsers but are ignored by Gecko, which uses scrollbar-width / scrollbar-color instead. If your scrollbars look custom in Chrome but default in Firefox, that's it.
backdrop-filter, -webkit-line-clamp, or other partially-supported features where Gecko's behavior lags or differs (some of these have converged recently, so it depends on browser versions).
Default form-control / input rendering, especially date pickers, range sliders, and appearance, which the engines style very differently out of the box.
To pin it down, the fastest path is to tell me what's actually different â layout breaking, colors/effects missing, scrollbars, fonts, a control looking wrong? Or if you can paste the relevant CSS/HTML, I can usually spot the engine-specific line. Open DevTools in both Firefox and Chrome and the one where the rule shows struck-through or unsupported is your culprit.
Good catch. I am constantly changing the width of the browser so the on/off/on/off couldn't have been more obvious but I still missed it.
