Recommended Posts

Here's my current shellstyle (based on Stolen VS):

shellstyle.png.xs.jpg

And as requested, this is my foobar config and the required plugins... It's just a mod of the one made by em3 so the instructions are the same...

m4.pui / default.pui

foobar_01.png.xs.jpg foobar_02.png.xs.jpg

(To download the files, click on "request download link" and then on "download file"...)

I'm using the latest version of PanelsUI and the window title didn't change when I loaded this config. To fix it I added the following in Preferences -> Panels UI -> User Globals:

$settitle([%artist% - ]['['%album%[ CD%discnumber%][ #%tracknumber%]']' ]%title%)

^Black didn't look as nice. And since there already is blue text in the theme, I thought it would look nice to use that for a active button as well. If I use black more the theme would look to plain and depressing. The checkmarks in the checkboxes etc. have to stand out more then text and such, just like the active button. If they are black they look disabled.

@Capric0rn: Very nice work, only one little thing: the entries in the context menu 'sent to' in Explorer are nearly unreadable.

edit: Attachments

I ported this Theme into WB5 and modied the Startmenu slightly and changed the highlighted text color which got rid of the invisible text. The shellex is a Vista shell that I'm experimenting with.

post-3332-1182009402_thumb.jpg

Like I said on Deviantart (I'm MystShadow20xx):

Nice theme, but the Shellstyles SHOULD be made for this. It may look better without them, but some people like the functionality of Shellstyles, like myself. Other than that bug, it's a very acceptable theme that I'd use for a long time.

Like I said on Deviantart (I'm MystShadow20xx):

Nice theme, but the Shellstyles SHOULD be made for this. It may look better without them, but some people like the functionality of Shellstyles, like myself. Other than that bug, it's a very acceptable theme that I'd use for a long time.

Not to sound all arrogant and stuff but I'm seeing a TON of misuses of the term 'bug".

A bug is something in the skin that is either not functioning properly, causes something else to not function properly, or is an overall problem that the original themer did not intend. If the themer INTENDED to have something in the VS than it is a feature. Just because some people do not like that particular feature does not mean that the skin is broken or there is a bug.

I personally think that the buttons look fine as they are but the blue active button is really nice. I'm really not to fond of the black one. It's really nice looking but does look like it's inactive and if the skin has so much black than it really makes things boring.

Just my eight cents :)

Like I said on Deviantart (I'm MystShadow20xx):

Nice theme, but the Shellstyles SHOULD be made for this. It may look better without them, but some people like the functionality of Shellstyles, like myself. Other than that bug, it's a very acceptable theme that I'd use for a long time.

There are many Shellstyles in other VS's matching LE Black. We should take LE Black as it is. Capric0rn did a great Job on this Theme and it's his Decision about the Shellstyle.

Regards

maddox

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

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!