waika

I regard CCleaner 5.00.5050 as a pleasant move away from skeuomorphism, there are still some minor eye sores that defeat the purpose of getting away from skeuomorphic design; ergo: · greater ease in avoiding mixed design metaphors that are confusing · avoiding color chaos lacking functional design cues · limitations of poor layout that offer no form that follows function · different pseudo depth effects with no continuity applied do same depth elements · conflicting pseudo light and gradient effects with ostensibly the same pseudo light source Only the last two are still conspicuously present on CrapCleaner 5.00.5050 in breaking the Windows 8.x 'Modern' interface; the Escher like overlap on the left button bar being the most obvious -- ouch! One of the benefits of non-skeuomorphic design is the eye fatigue of false (and often conflicting) depth and light cues endemic to skeuomorphic design can be completely avoided; there's plenty of R&D and testing that shows this not only works when executed properly it works very well. Some may not feel it's as 'pretty' but it's a lot easier on the eyes in terms of your brain making sense out of what it's seeing that will lead to less eye fatigue; this is why all mission critical and military displays and MFD interfaces avoid skeuomorphic design like the plague. While the Windows 8 (NT 6.2) interface is not the high watermark in interface design, it does offer a substantial improvement in reconciling many of issues that are endemic to the Windows 7 (NT 6.1 and previous) interface failings, it's obviously a direction Microsoft intends to continue, and the design guidelines are well researched, exhaustively tested, with literally millions spent on the R&D. Why not benefit from that? Like it or not a disparate and contrasty interface design is not, and never has been good branding, attractive, or a successful marketing tool -- most in-depth marketing research shows that software that looks like it's an integrated part of the platform has been found to be more appealing and sells better where all other things are equal. It's not difficult to understand why this is in fact the case when the actual BRAND (logo, company and/or product name) becomes the locus and focus of user attention, and is not buried in a confusing Kafkaesque interfaces with absurdly large and histrionically embellished control layout that is more of a trip to anxiety for most Users they want to close as soon as their done using then interface, then a solution that looks like part of the OS, and warms them to a brand. Raise the bar of integration, follow the MS Guidelines, turn the sidebar in to an expandable context sensitive Windows Explorer style 'Ribbon' that organizes and exposes CCleaner's features heuristically. These are the controls and interface language that your future Users will be most familiar with; and those new to discover applications inspired by Windows 9.x Taligent inspired interface design will regard that approach is unfamiliar, old, and cumbersome...

Well taking your questions in order; there are substantial advantages to be had with regard to security to using portable applications that are natively portable; ergo do NOT write to the Windows Registry (don't require a wrapper to redirect Registry i/o) and whatever local directories they store anything in is immaterial as long as the permissions are properly managed. That said I have all my Opera data hard-linked to a RAM disk, so the application is in effect 'sandboxed'...

No Nergal, I'm not cousfued, I use the same kind of path statement. You seem to have missed the point that I am referencing portable installations of the 64-bit editions of Opera and Opera Next -- you appear from your path data appear to be using the 32-bit version... Edit: I finally got it to work, though I've been using the same path statement all along, added quotes and removed them from the path, used truncated short file names etc: CustomLocation1=OPERA|C:\Program Files\Opera x64\profile\cache When I added 'cache' to the string it was finally detected... And that's why there's veracity in having this as a native feature of Crap Cleaner, a lot of people aren't going to be as patient as I am...

Yes, I understand that -- but when you use custom locations there's no audit display of the path being cleaned in Crap Cleaners output display...

Thanks Nergal -- though it would be nice if Crap Cleaner could reconcile this and do it automatically as the native detection gives nice audit confirmation of what was cleaned vs. the 'custom locations' method. What's more, the x64 builds of Opera have for some months been at feature parity and have surpassed the 32-bit versions for stability and performance -- and are seeing a substantial up-tick in use.

I don't see any 'custom location' entries in my ccleaner.ini or winapp2.ini... What's the exact syntax that should be used? And how is it that on a 32-bit install of Windows 7, CCleaner detects and cleans a portable installation of Opera, but can not detect the 64-bit installation Opera portable (or 64-bit portable installation of Opera Next ) on a 64-bit installation of Windows 7? Please advise?

I'd like to vet support for the 64-bit portable installation of Opera as well; it appears there is support for the 32-bit version of a portable installation of Opera, but this doesn't work with the 64-bit version...