Recommended Posts

I'll do some more investigating, but it looks like your approach is the only one working at the moment(at least if you're wanting to keep the 22px tab bar). I would however reduce the height to 23px since its the minimum necessary to keep a 16px icon. Then again I thought the 15px icon looked aesthetically better.

you did notice that it's all the tab icons; whether they're in pinned or normal tabs is irrelevant?

The odd thing is that using ".tab-throbber, .tab-icon-image min-height: 16px" or ".tabbrowser-tab[pinned] min-height: 24px" the icons remain 16x16 in the 22px tabs. Only pinned tabs when alone they are 16x15.

And right now I discovered another problem. When scrollbox is activated, the pinned tabs is messed up showing 24px and overlapping nav-bar.

I think "pinned tabs", "pinned tabs only" and "tabs" have different css. But in browser.css I found nothing.

Maybe I should accept to live with the 23px.

I'm not a programmer and do not like to code, css etc, I am like old fashion graphic designer, so my skill is low on that. But it seems to me that the UX team is a mess with css. Many redundancies and many peculiarities that looks like patches upon patches.

The odd thing is that using ".tab-throbber, .tab-icon-image min-height: 16px" or ".tabbrowser-tab[pinned] min-height: 24px" the icons remain 16x16 in the 22px tabs. Only pinned tabs when alone they are 16x15.

And right now I discovered another problem. When scrollbox is activated, the pinned tabs is messed up showing 24px and overlapping nav-bar.

I think "pinned tabs", "pinned tabs only" and "tabs" have different css. But in browser.css I found nothing.

Maybe I should accept to live with the 23px.

I'm not a programmer and do not like to code, css etc, I am like old fashion graphic designer, so my skill is low on that. But it seems to me that the UX team is a mess with css. Many redundancies and many peculiarities that looks like patches upon patches.

try this :

#tabbrowser-tabs:not([overflow="true"]) .tabbrowser-tab[pinned] {
	min-height: 23px !important;
}

#tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
	height: 22px !important;
}

I tried it and the icon size didn't change even though the tab was resized on overflow.....:hmmm:

It'll be better if it is non-transparent.

my code isn't transparent. You need to add a background to #PersonalToolbar.

oops, my fault. Working now, anyway, what do I need to change so that it will only appear when I hover on the address bar and not when I'm hovering on the tabs?

use

#nav-bar:hover ~ #PersonalToolbar[collapsed="false"],
#PersonalToolbar:hover {

instead of:

#navigator-toolbox:hover > #PersonalToolbar[collapsed="false"]

nice, thanks! everything is set on my browser now (I think), since I can't figure out how to have the persona skin for the autohide bookmarks toolbar, what I did is to crop a screenshot of my persona and used it as the bookmark's background :p

thanks a lot foxxy :D

Edit: Just one more, what do I need to change so that while I'm hovering at the bookmarks, it will not fade out?

nice, thanks! everything is set on my browser now (I think), since I can't figure out how to have the persona skin for the autohide bookmarks toolbar, what I did is to crop a screenshot of my persona and used it as the bookmark's background :p

thanks a lot foxxy :D

Edit: Just one more, what do I need to change so that while I'm hovering at the bookmarks, it will not fade out?

#nav-bar:hover ~ #PersonalToolbar[collapsed="false"],
#PersonalToolbar:hover {

#PersonalToolbar:hover prevents that from happening. If you're having problems with that, post the entire modified code you're using.

here it is:

/*App Menu*/
#main-window[sizemode="maximized"] #appmenu-button .button-icon {
  list-style-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAOCAYAAAAmL5yKAAAB5klEQVQoz3WSu04bQRSGBwShAFFAiiClBCE6Kpo0PAEEpcsDEJkCiYoKCoQQTwBPQBeFClFE6WiDBDZSJBvZ67vXF3m9vq0968l3Vl5kEB7p11zOP/85559RitHtdr+pkdHr9abBp3DfbrcnwXqn09mDG2G9OspXzWbT4vBcax2BsN/v96Ng6Q1nFs534k/AZb0VBBqNxgQbhwuGrIa14IYLH9Q7A/6867r3rVbLIeGG8jxvRy6iGlwmYCAwtbKVSuVqjMiW4ziGpEfS/w29hZkDsM+ABTVmkPlYEsH5JQYlRGCIQbVa9Sj/msrWxwmQ+VyqljJVvV5PS/<< racial epithet >>qlurFYzCQSiY/jLsP7Av4OBSqqVCo9cOCLQDab1el02liW9cj6JJfLXYJ/hUJhd+RJv1KhL0nBH0XwFFNcOSBgarWawbyzZDLZyWQydj6f/8E8NfwvK+BUkgmfKg5VPB5fRkRs94aqgh6ZDnB6JsyMJ2sgClwEnoXD+nMQROSCUuVz+AgNQiGINme3EO/IpuWMtcQteBcvxiAwh3H39O+Xy2VNG5p2+mAQlhv+EdnzT6Jg/pW7GLfIK/xmFjMNvRsM9ovForZtO/BGPg+vds28+O4TITBBK9vgJwIW0PijEUrJrwSbb+/8B7t0QamEFz2OAAAAAElFTkSuQmCC);
}

#main-window[sizemode="maximized"] #appmenu-button {
  padding: 0 2px 1px !important;
  min-width: 0 !important;
}

#main-window[sizemode="maximized"] #appmenu-button .button-text {
  visibility: collapse;
}



/* Addon bar */
/*
#addonbar-closebutton {
  display: none;
}

#browser-bottombox {
  position: fixed;
  bottom: 0;
  background: none !important;
}

#addon-bar {
  position: fixed;
  bottom: -22px;
  right: 0;
  border: 0 !important;
  opacity: 0;
  -moz-appearance: none !important;
  -moz-transition: bottom .5s 1s ease-in, opacity .5s 1s ease-in;
  padding-top: 22px !important;
}

#addon-bar:hover {
  bottom: 0;
  opacity: 1;
  -moz-transition: bottom .5s .4s ease-out, opacity .5s .4s ease-in;
}

#addon-bar > #status-bar {
  margin: 0 1px 1px 0 !important;
  padding: 0 2px 0 2px;
  border-radius: 4px 0 0 0;
  border: 0 !important;
  border-left: 1px solid rgba(0,0,0,.30) !important;
  border-top: 1px solid rgba(0,0,0,.30) !important;
  background: -moz-linear-gradient(#FBFCFD, #E6F0FA 50%, #DCE6F4 51%, #DDE9F7) padding-box !important;
}
*/

.tabbrowser-tab:not([selected="true"]) {
	background-image: -moz-linear-gradient(rgba(190,190,190,.55), rgba(120,120,120,.55), rgba(50,50,50,.7)) !important;
}
.tabbrowser-tab:not([selected="true"]):hover {
	background-image: -moz-linear-gradient(rgba(255,255,255,.55), rgba(230,230,230,.55), rgba(120,120,120,.7)) !important;
}
.tabbrowser-tab[selected="true"] {
	background-image: -moz-linear-gradient(rgba(255,255,255,.75), rgba(255,255,255,.55), rgba(255,255,255,.55)) !important;
}
/*New Tab*/
#appcontent,
#content > tabbox > tabpanels {
  background: url("file:///D:/My%20Pictures/Wallpapers/firefox.jpg");
  background-color: transparent !important;
  background-position: center;
}

#main-window[stylish-url="about:blank"]:not([onclose="PrintUtils.exitPrintPreview(); return false;"]) #content browser{ 
opacity: 0 !important;
}

/*Animated Add-on Bar and Find Bar fixes*/
/*Remove/comment this block if you prefer add-on Bar always showing*/
#addonbar-closebutton {
  display: none;
}
#navigator-toolbox:not([customizing]) ~ #browser-bottombox {
	position: fixed;
	bottom: 0;
	left: 0;
}
#navigator-toolbox:not([customizing]) ~ #browser-bottombox #addon-bar {
	-moz-appearance: none !important;
	padding: 2px 10px 0 10px !important;
	margin-bottom: -1px !important;
	border: none !important;
	border-radius: 2px 2px 0 0 !important;
	margin-right: 25px !important;
	background-image: -moz-linear-gradient(rgba(255,255,255,.8), rgba(200,200,200,.8)) !important;
	box-shadow: 0 0 0 1px rgba(0,0,0,.25) inset, 0 0 0 2px rgba(255,255,255,.5) inset !important;
	position: fixed;
	bottom: -7px;
	left: 0;
	opacity: 0;
	-moz-transition: bottom 0.25s 0.5s ease-in, opacity 0.1s 0.65s ease-in;
}
#addon-bar .toolbarbutton-1 {
	padding-bottom: 4px !important;
}
#navigator-toolbox:not([customizing]) ~ #browser-bottombox #addon-bar:hover {
	bottom: 0;
	opacity: 1;
	-moz-transition: bottom .25s .25s ease-out, opacity 0.1s 0.25s ease-out;
}
#FindToolbar {
	border: none !important;
}
#FindToolbar .findbar-container {
	margin-bottom: -2px !important;
	margin-left: -2px !important;
	border-radius: 0 2px 0 0 !important;
	background: -moz-linear-gradient(rgba(255,255,255,.8), rgba(200,200,200,.8)) !important;
	box-shadow: 0 0 0 1px rgba(0,0,0,.25) inset, 0 0 0 2px rgba(255,255,255,.5) inset !important;
}
#FindToolbar .find-status-icon[status="notfound"] + .findbar-find-status, #FindToolbar .find-status-icon[status="wrapped"] + .findbar-find-status {
  	padding-right: 5px !important;
}
#FindToolbar .find-status-icon[status="notfound"], #FindToolbar .find-status-icon[status="wrapped"] {
 	 margin-left: -1px !important;
}
#FindToolbar .find-status-icon:not([status="notfound"]):not([status="wrapped"]) + .findbar-find-status {
 	 display: none !important;
}
/*Adjust tab size*/
/*
.tabbrowser-tab:not([pinned])[fadein] {
  max-width: 130px !important;
}
*/
#main-window[sizemode="maximized"] #TabsToolbar[tabsontop="true"] {
        margin-bottom: -2px !important;
        background: none !important;
        background-image: none !important
}

/*Bookmarks Toolbar*/
#navigator-toolbox:not([customizing]) #PersonalToolbar {
	position: fixed !important;
	top: 80px !important;
	left: 0 !important;
	right: 0 !important;
	background-color: rgb(207, 219, 236)!important;
	border-bottom: 1px solid !important;
	-moz-border-bottom-colors: threedshadow threedhighlight !important;
	color: #000 !important;
	text-shadow: none !important;
	visibility: collapse !important;
	opacity: 0 !important;
	-moz-transition: visibility .9s, opacity .9s ease-out !important;
	-moz-transition-delay: 1.25s!important;
}

#main-window[sizemode="normal"] #PersonalToolbar {
	top: 73px !important;
	border-radius: 0 !important;
}

#main-window[tabsontop="true"] #PersonalToolbar {
	top: 54px !important;
}

#main-window[sizemode="normal"][tabsontop="true"] #PersonalToolbar {
	top: 75px !important;
}

#main-window[stylish-url="about:addons"] #PersonalToolbar {
	display:none !important
} 

#personal-bookmarks {
background:url("file:///D:/My%20Pictures/Wallpapers/test.JPG");
	width: 100% !important;
	padding-left: 4px !important;
	padding-right: 4px !important;
}

#nav-bar:hover ~ #PersonalToolbar[collapsed="false"],
#PersonalToolbar:hover {
	visibility: visible !important;
	opacity: 1 !important;
	-moz-transition: .2s ease-in !important;
	-moz-transition-delay: 1.25s!important;
}

Hope you can help me. Thanks :D

I commented some parts of the code that I don't use but may use later.

here it is:

Hope you can help me. Thanks :D

I commented some parts of the code that I don't use but may use later.

To fix the bookmark toolbar hover change #navigator-toolbox:not([customizing]) #PersonalToolbar to #PersonalToolbar:not([customizing])

For some reason I'm having difficulty displaying tabs in the title bar only when Firefox isn't maximized. I've tried a few of the suggestions in this thread but they seem to do nothing but adjust the spacing between the first tab and the menu button.

Also, would there be a way to adjust the opacity and font color of the Awesome and Search bars? If I could also somehow remove everything but the icons themselves and their dividers from the minimize, maximize, exit buttons in the top left, that'd be great.

Thanks in advance.

post-372898-0-19823700-1297755651.png

For some reason I'm having difficulty displaying tabs in the title bar only when Firefox isn't maximized. I've tried a few of the suggestions in this thread but they seem to do nothing but adjust the spacing between the first tab and the menu button.

Also, would there be a way to adjust the opacity and font color of the Awesome and Search bars? If I could also somehow remove everything but the icons themselves and their dividers from the minimize, maximize, exit buttons in the top left, that'd be great.

Thanks in advance.

Normal Window Tabs In Titlebar

url/search bars

#urlbar, #searchbar .searchbar-textbox {
       background-color: rgba(0,0,0,0.5) !important;
       color: #ccc !important
}

I don't think it's possible to modify the caption buttons like that with css

try this :

#tabbrowser-tabs:not([overflow="true"]) .tabbrowser-tab[pinned] {
	min-height: 23px !important;
}
#tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
	height: 22px !important;
}

I tried it and the icon size didn't change even though the tab was resized on overflow.....:hmmm:

This did the job! Thank you very much.

Style has been updated Drifus - Firefox 4 project - aero clean

Changelog:

- feb.15.2011

* Fixes, due to the latest Firefox trunk (Add-on Bar and tabs)

* Removed tweaks of the tabbar buttons and scrolls buttons - Firefox UX team did a great update there.

Normal Window Tabs In Titlebar

url/search bars

#urlbar, #searchbar .searchbar-textbox {
       background-color: rgba(0,0,0,0.5) !important;
       color: #ccc !important
}

I don't think it's possible to modify the caption buttons like that with css

Thanks so much!

How can I get rid of the "bottom border" that appeared some builds ago under the navbar (see attached pic)? it doesn't seem to be the "bottom-border" of any object, and I can move it only by changing the margin of the navbar or personal toolbar in CSS. Is it some background image? of which element?

post-311154-0-63253300-1297877312.png

How can I get rid of the "bottom border" that appeared some builds ago under the navbar (see attached pic)? it doesn't seem to be the "bottom-border" of any object, and I can move it only by changing the margin of the navbar or personal toolbar in CSS. Is it some background image? of which element?

#navigator-toolbox::after {
	height: 0px !important; 
}

#navigator-toolbox::after {
	height: 0px !important; 
}

Hey, thanks for that from me too! ;)

BTW, when is the latest beta of status 4 evar add-on going to get final? It seems like ages since I wait for the UI bugs to get fixed ... :angry:

BTW, when is the latest beta of status 4 evar add-on going to get final? It seems like ages since I wait for the UI bugs to get fixed ... :angry:

That would be a question only Bluefang can answer

Mozillazine - Status-4-Evar 2011.02.07.02b

What if I want to display status text to be how it looks like by default (lower left corner, appears only when loading), I only want to use status4eva as a substitute to fission. What do I need to change? I tried playing with the options and the best it could do is to display the status text on the addon bar, which is useless since my addon bar autohides. Hope you can help me, thanks.

What if I want to display status text to be how it looks like by default (lower left corner, appears only when loading), I only want to use status4eva as a substitute to fission. What do I need to change? I tried playing with the options and the best it could do is to display the status text on the addon bar, which is useless since my addon bar autohides. Hope you can help me, thanks.

WFM. Are you using the latest version - Version 2011.02.07.02b

post-350326-0-17491300-1298049829.png

Experts, two requests ....

First ...

I'd like to know if there's a way to color spacers added by dragging from the Customize screen.

Currently, I have all my stuff on a single row:

from left to right, New Tab icon, Home icon, Tabs, URL bar, Stylish icon, and AdBlock Plus icon.

I've put in two spacers to get some gap between the right-end of the right-most tab and the start of the URL bar.

I'm going for a minimal look (but with enough contrast). The code that I have is below but it leads to the spacers being indistinguishable

from the tabs to the left and the URL bar to the right.

My second request is for a way to make the tab-close-button a little more visible for both active and inactive tabs. It's okay

if it's not possible to make the tab-close-button appear differently on hover.

Any help will be most appreciated.

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); 
#nav-bar { display: none !important; }
#TabsToolbar { background: maroon !important; }
#TabsToolbar:-moz-window-inactive {background-color: grey !important; }

#context-openlink, #context-bookmarkpage, #context-bookmarklink, #context-setWallpaper, 
#context-setDesktopBackground, #context-viewimage, #context-blockimage, #context-back, 
#context-forward, #context-reload, #context-stop,  #context-sendpage, #context-sendlink, 
#context-sendimage, #context-undo, #appmenu-button, #search-container,  #star-button,
#go-button, .urlbar-history-dropmarker, #identity-box.unknownIdentity, #page-proxy-favicon, 
#identity-icon-label, #titlebar {display:none !important; 
	}

#urlbar {
	background-color: maroon !important;
	font-size: 16px !important;
	font-weight: bold !important;
	color: #b0b0b0 !important;
	border: none !important;
	box-shadow: none !important;
	min-width: 300px !important;
	}
.tabbrowser-tab[selected="true"] {
	background-color: maroon !important;
	background-image: none !important; 
	font-size: 14px !important;
	font-weight: bold !important;
	color: yellow !important;
	border: none !important;
	box-shadow: none !important;
	padding-left: 5px !important;
	}
.tabbrowser-tab:not([selected="true"]) {
	background-color: maroon !important;
	background-image: none !important;
	font-size: 14px !important;
	font-weight: bold !important;
	color: #b0b0b0 !important;
	text-shadow: none !important;
	text-decoration: none !important; 
	border: none !important;
	box-shadow: none !important;
	padding-left: 5px !important;
	}
.tabbrowser-tab .tab-icon-image {
	display: none !important; 
	}
/*Prevents White pre-load flash*/
tabbrowser tabpanels {
	background-color: #b0b0b0 !important;
	}
.statuspanel-label {
	border: none !important;
	background: #808080 !important;
	color: maroon !important;
	font-weight: bold !important;
	font-size: larger !important;
	}

Experts, two requests ....

First ...

I'd like to know if there's a way to color spacers added by dragging from the Customize screen.

...

This works:

toolbarspacer {background-color: green !important; opacity: 1 !important; }

though I'll see if the opacity bit is necessary.

Help still wanted for the tab-close-button !

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!