- On Mac, all the apps that I’d want to open are in the /Applications directory and for the most part all have a.app extension, so we can get their names using something like this: d = '/Applications' apps = list(map(lambda x: x.split('.app')0, os.listdir(d))) List the directory and remove the extension.
- The menu bar has been a fixture on the Mac since it launched in 1984, but since OS X El Capitan, you can hide the menu bar. Open System Preferences, go to General, then click 'Automatically hide.
- Cool new features like WebRTC (webcam support) and speech input. Better automated UI testing via the DevTools remote debugging protocol and ChromeDriver2. Faster access to current and future Web features and standards. This document introduces the general concepts involved when developing an application using CEF3. Getting Started.
These operating system versions were tested in-house. Operating system/platform Versions; Windows Server: 2012 R2 2016 2019. Mac OS is not supported with NFS v4.1. Supported virtualization platforms for device. Both hot and cool tiers are supported. Supported storage types. Here is a list of the supported storage types for the device. Current version is v0.983 build 248 (April – 2021) AmigaLive is available for 64-bit Windows, MacOS and Linux. It works cross-platform and is packaged with the “FS-UAE/FS-UAE Launcher”.
Cool Blob Future Mac Os Catalina
CCC 5.1.23+ can make bootable backups of Big Sur on Intel-based Macs.
Update Nov 24:CCC 5.1.23 can now make bootable backups of a Big Sur startup disk on Intel-based Macs. Support for System volume cloning on Apple Silicon Macs is disabled for now because Apple's APFS replication utility does not currently work on that platform. When Apple fixes that, we'll post an update to CCC that restores support for making bootable backups on Apple Silicon Macs.
CCC is a native application on Apple Silicon and is 100% compatible with Apple Silicon Macs
CCC will automatically proceed with a Data Volume backup when backing up an APFS Volume Group on Apple Silicon Macs — that's a complete backup of your data, applications, and system settings. If you would like to make your Apple Silicon Mac backup bootable, you can install Big Sur onto the CCC Data Volume backup. Please keep in mind, however, that your CCC backup does not have to be bootable for you to be able to restore data from it.
CCC will automatically proceed with a Data Volume backup when backing up an APFS Volume Group on Apple Silicon Macs — that's a complete backup of your data, applications, and system settings. If you would like to make your Apple Silicon Mac backup bootable, you can install Big Sur onto the CCC Data Volume backup. Please keep in mind, however, that your CCC backup does not have to be bootable for you to be able to restore data from it.
Pictures at an exhibition mac os. With the announcement of macOS Big Sur, Apple has retired Mac OS X (10) and replaced it with macOS 11. As with every upgrade since the original release of Mac OS X, we have to make changes to CCC to accommodate the changes in this new OS. As the numeric change would suggest, though, this is the biggest change to macOS since Apple introduced Mac OS X roughly 20 years ago. The system now resides on a 'Signed System Volume'. This volume is cryptographically sealed, and that seal can only be applied by Apple; ordinary copies of the System volume are non-bootable without Apple's seal. To create a functional copy of the macOS 11 System volume, we have to use an Apple tool to copy the system, or install macOS onto the backup.
Does this mean that we can no longer have bootable backups?
I can certainly understand why people are concerned about the future of this solution. Thanks to these massive system changes and some bugs in the version of Big Sur that Apple intends to ship, nobody can make a proper copy of the System volume right now, not even with Apple's proprietary utilities. Based on that statement alone, and a suggestion from one of my competitors to just give up and use Time Machine instead (which does not make bootable backups, nor back up the System), someone could falsely conclude that it's impossible to have a bootable backup.
Buddy up! mac os. I think that pessimistic conclusions are also fostered by a concern that Apple is trying to turn macOS into iOS, or otherwise merge the two platforms. On top of that we're in the midst of a pandemic, and one would hope that Apple would cool their jets and defer these massive changes for a year. But no, we're not just getting a massive new OS this year, we're getting a new hardware platform too! We're seeing a lot of change at a time where we could really use some stability.
The changes in Big Sur definitely present some new logistical challenges, butyes, you can have a bootable backup of macOS Big Sur. Right now you can install Big Sur onto your CCC backup to make it bootable, and in the future we'll use Apple's APFS replication utility (ASR) to clone the Big Sur System volume. Apple has assured us that they are working towards fixing the problems in ASR that prevent it from cloning the Big Sur System volume.
Does my CCC backup have to be bootable for me to restore data from it?
No. Bootability is a convenience that allows you to continue working if your startup disk fails, but it is not required for restoring data from a CCC backup. You can restore individual folders and older versions of files (i.e. from snapshots) using CCC while booted from your production startup disk. CCC backups are also compatible with Migration Assistant, so you can use Migration Assistant to restore all of your data to a clean installation of macOS (e.g. on a replacement disk).
Here's why I'm really stoked about this new, 'proprietary' macOS, and optimistic about the future of bootable backups
Every year we spend hundreds of hours making changes to CCC to accommodate the new OS. Every year. CCC isn't like other apps that can easily roll with the changes; our solution is tied so closely to the logistics of the startup process, and that happens to be something that Apple has been changing a lot since the introduction of APFS. The logic changes required to accommodate APFS volume groups alone are mind blowing. All of that time spent is subtracted from the time we can spend on feature work. To put it plainly, we spend about a quarter to half of our year just making CCC work with the next year's OS. That's not a shiny new feature that users can swoon about (and pay for!), it's typically thankless work, and – fair or not – work that users have come to expect us to provide for free.
What if we didn't have to take the responsibility of making the startup logistics work on the backup disk? What if Apple provided that part of the solution? What if all we had to do was make the best backup of your data, apps and system settings, and then let Apple handle the logistics of the System? We'd be dreaming, right?
In fact, Apple has been making key parts of the startup process proprietary for years, but they've also been developing functionality within macOS that handles the proprietary parts. All the way back to the beginning of Mac OS X, in fact, we'll start with the 'bless' utility, which makes changes to the volume headers to make a volume bootable. We've been using bless for 20 years! Over that time bless has been adapted to the changing OS and hardware landscape, because Apple uses it too. With the introduction of APFS, we've had to leverage more Apple utilities; primarily diskutil, a command-line version of Disk Utility. We really started leaning on diskutil in Catalina for the manipulation of APFS volume groups. Finally, in macOS 10.15.5 we got the 'opportunity' to field test another Apple utility that has lurked in macOS since Mac OS 9: Apple Software Restore (ASR). ASR is a utility that Apple has used in factories to 'stamp' the system image onto every Mac, and more than a decade ago I developed a mass deployment solution around that utility. Like with the bless utility, Apple has been adapting ASR for APFS, and Apple is going to make ASR work with Big Sur too.
In the near future, I expect to be able to leverage ASR within CCC (again) to clone the Big Sur System volume, and then use our own file copier for maintaining backups of the data that actually matters – your data, applications, and system settings. That would create the perfect division of responsibility: Apple is responsible for the copying of its proprietary OS, and CCC is responsible for the backup of your data. All of this, though, will be neatly wrapped in the Carbon Copy Cloner bootable backup solution.
We need to share our concerns productively with Apple
It's easy to complain about how things don't work the way they used to (go ahead and get me started on Big Sur's new alert dialogs and progress indicators!). Rather than complaining, or giving up, though, we need to make it clear to Apple that we want these solutions, and we need to make it clear when they don't work. We can do that with bug reports, and to that end, we've been very transparent about our bug reports to Apple on issues within macOS that affect CCC, e.g.:
But we can also send a clear message to Apple with our choices. If Apple ships macOS Big Sur without fixing the underlying utilities that facilitate creating a bootable backup, you can choose to defer the upgrade. There is no urgency, no impetus to upgrade to macOS Big Sur. If we defer the upgrade choice, that sends a clear message that we're willing to wait for Apple to deliver quality software, rather than hitting an artificial deadline with an OS that's not ready.
In the meantime, if you're an early adopter by choice or by profession, you can still make your CCC backups bootable. CCC will automatically handle the logistics of making a complete backup of all of your data, applications and system settings. Once you have that, simply install Big Sur onto your backup to make it bootable. Again, we're planning to automate that part of the procedure in the future, but we've tested this scenario extensively and we're prepared to support it.
CCC 5.1.22 is qualified for use on macOS Big Sur, and this update is free for all current CCC v5 license holders. We have some additional resources that folks should check out as well as they consider the Big Sur upgrade:
10.3: Enable the floating Exposé blob | 38 comments | Create New Account
Cool Blob Future Mac Os Update
Click here to return to the '10.3: Enable the floating Exposé blob' hint |
The following comments are owned by whoever posted them. This site is not responsible for what they say.
How bizarre!
There's some other mysterious preference keys, such as:
[code]wvous-tl-corner
wvous-tr-corner
wvous-bl-corner
wvous-br-corner[/code]
No idea what these are, but the Dock set wvous-br-corner equal to 5 by itself. I have no idea what it means.
There's also:
[code]wvous-showcorners
wvous-floater-style
wvous-maindisplay
wvous-olddesktop
wvous-spring-delay
wvous-spring[/code]
I've tried setting wvous-showcorners, wvous-floater-style, wvous-spring-delay, and wvous-spring with no obvious effects. Can anybody else figure out what these are?
There's some other mysterious preference keys, such as:
[code]wvous-tl-corner
wvous-tr-corner
wvous-bl-corner
wvous-br-corner[/code]
No idea what these are, but the Dock set wvous-br-corner equal to 5 by itself. I have no idea what it means.
There's also:
[code]wvous-showcorners
wvous-floater-style
wvous-maindisplay
wvous-olddesktop
wvous-spring-delay
wvous-spring[/code]
I've tried setting wvous-showcorners, wvous-floater-style, wvous-spring-delay, and wvous-spring with no obvious effects. Can anybody else figure out what these are?
D'OH!
Note to self: READ the preview before submitting!
Note to self: READ the preview before submitting!
top left corner
bottom left corner
top right corner
bottom right corner
Looks like those keys store hot corner settings.
bottom left corner
top right corner
bottom right corner
Looks like those keys store hot corner settings.
I figured that's what the abbreviations meant, but hot corners for what? Also, the key that the Dock stored by itself was the bottom-right cornet set to 5? What does that mean?
I Ran the command in Terminal and also from terminal 'killall Dock' Since then I logged out last night and in the morning I saw something strange!!!
There was a finder window open floating under the Login List window. I noticed that the Home Folder was labeled Root, and I Could run apps as Root! When I logged in as a user I never recieved the desktop, and Still Had my Finder window. When I ran an app, it Ran as that User. When going to Logout (from the Apple) I would see either log out 'System Administrator' or log out '(the user's name)' depending on the Application I was currently Running. After Logging out then Back in as another User, I recieved it's desktop items, and Everything looks back to normal.
I grabbed a screen shot, but do not know how to post it.
Very Interesting!!!!!
There was a finder window open floating under the Login List window. I noticed that the Home Folder was labeled Root, and I Could run apps as Root! When I logged in as a user I never recieved the desktop, and Still Had my Finder window. When I ran an app, it Ran as that User. When going to Logout (from the Apple) I would see either log out 'System Administrator' or log out '(the user's name)' depending on the Application I was currently Running. After Logging out then Back in as another User, I recieved it's desktop items, and Everything looks back to normal.
I grabbed a screen shot, but do not know how to post it.
Very Interesting!!!!!
Go to
http://www.imageshack.com/
and upload it there. Post the URL it gives you here.
http://www.imageshack.com/
and upload it there. Post the URL it gives you here.
..Wow. I just looked at the pictures again and realized that you did something with iTunes I never knew was possible!
Apparently trying to shrink the minimized version will get rid of the status fields entirely!
Maybe there should be a hint about that..
Apparently trying to shrink the minimized version will get rid of the status fields entirely!
Maybe there should be a hint about that..
haha! You and I both got two-for-one hint!
You should get a copy of Kelby's Jaguar Killer Tips, or just look through it in the bookstore. The teeny iTunes window tip is there. In 'mini window mode', just grab the resize handle (lower right corner) and resize.
Ahhh! That screenshot! It's Rover from 'The Prisoner'! Run away!
(I can't find a decent picture of Rover to link to, but this page does a decent job of explaining the reference and conveying the imagery almost as well as the original :-)
---
--
DO NOT LEAVE IT IS NOT REAL
--
DO NOT LEAVE IT IS NOT REAL
Oh wow, you're right!
Ok, I did some playing around an this is what I found. This will make little gray semi-circles appear in the corners
These refer to the exposé corners: tl=Top Left, tr=Top Right, bl=Bottom Left, br=Bottom Right Replace 'tl' with what corner you want, and 'x' with a number between 1 and 6. The number is the action that is performed by exposé 1=Nothing, the semicircle will disappear 2=All Windows 3=Application windows 4=Desktop 5=Start Screen Saver 6=Disable Screen Saver All these can be set from the Exposé preference pane.
This will change the Desktop effect. Instead of moving all the windows to the edges of the screen, it puts them all in a small box that can be dragged around the screen. Anyone had any luck with the others?
---
Do it today because tomorrow it may be illegal.
Do it today because tomorrow it may be illegal.
When I set wvous-olddesktop to 'no' to get the hyperzoomy effect, as soon as I zoomed to desktop then back, all metal windows stopped responding to mouse clicks - including Finder! So apparenly that effect was disabled because of some really weird interaction with the window server or something.
It's a shame, too, because that effect is much cooler than the windows all flying to the edge of the screen, and it could probably be argued that it's better for usability too (since it preserves spatial memory and so on).
Also, when I enabled the semicircles, the entire UI froze up as soon as I tried any Expose action (though iTunes kept on playing).
It might make a difference that I'm just running on a G4/450 with a Rage 128. (I'm getting a Radeon soon, honest!)
It's a shame, too, because that effect is much cooler than the windows all flying to the edge of the screen, and it could probably be argued that it's better for usability too (since it preserves spatial memory and so on).
Also, when I enabled the semicircles, the entire UI froze up as soon as I tried any Expose action (though iTunes kept on playing).
It might make a difference that I'm just running on a G4/450 with a Rage 128. (I'm getting a Radeon soon, honest!)
Wow, I love the olddesktop effect!
BTW, metal windows work perfectly fine for me after using it.
Erm, nevermind. The Preview button just stopped working until I scrolled the scrollbar manually (scroll wheel didn't work). But it's working now after trying the exposé effect again. Weird.
BTW, metal windows work perfectly fine for me after using it.
Erm, nevermind. The Preview button just stopped working until I scrolled the scrollbar manually (scroll wheel didn't work). But it's working now after trying the exposé effect again. Weird.
Actually, I know the problem now. It leaves an invisible window (I assume) in the area where the windows shrink to that sucks up all clicks in that area. So wherever you place the tiny window, you can't click. Turning olddesktop back on fixes it, though.
I figured out wvous-spring and wvous-spring-delay.
By default, if you drag a file (or probably any drag, but only tested with files from the Desktop) to an Exposé'd window (i.e. start drag, start Exposé, drag to window) and hover over a window for 1 second, it will flash and select itself. Just like spring-loaded folders (Space works for selecting the window as well).
If you do <tt>defaults write com.apple.Dock wvous-spring -bool false</tt> and restart the Dock, this behaviour disappears. To restore, do <tt>-bool true</tt> instead (or do a <tt>defaults delete com.apple.Dock wvous-spring</tt>).
To change the delay before the spring, set wvous-spring-delay. The value is an integer in milliseconds (i.e. 1000 1 second). For example, to set it to 2 seconds, type <tt>defaults write com.apple.Dock wvous-spring-delay -int 2000</tt>.
By default, if you drag a file (or probably any drag, but only tested with files from the Desktop) to an Exposé'd window (i.e. start drag, start Exposé, drag to window) and hover over a window for 1 second, it will flash and select itself. Just like spring-loaded folders (Space works for selecting the window as well).
If you do <tt>defaults write com.apple.Dock wvous-spring -bool false</tt> and restart the Dock, this behaviour disappears. To restore, do <tt>-bool true</tt> instead (or do a <tt>defaults delete com.apple.Dock wvous-spring</tt>).
To change the delay before the spring, set wvous-spring-delay. The value is an integer in milliseconds (i.e. 1000 1 second). For example, to set it to 2 seconds, type <tt>defaults write com.apple.Dock wvous-spring-delay -int 2000</tt>.
D'OH! I did it again. The relevant code snippets were:
I´ve had bad luck with the small box feature: resulting in mouse clicks were not recognized at the screen position of the small box - Whenever i was clicking in some app window around that area the small box would reside nothing happened.
This was driving me crazy for i had to shift the windows to get the mouse click working, and i was seeking some weeks to find the reason why..
So i got back to the old fashined way again.
This was driving me crazy for i had to shift the windows to get the mouse click working, and i was seeking some weeks to find the reason why..
So i got back to the old fashined way again.
Sure, it's the easy way - but fact is, The Blob, from crabby apple software, allows a set and forget blob. . . .of your own design! I'm always on a Powerbook, thus forever obsessing over screen real estate - but maybe you don't like overly-large glossy blue circles either.
Drop any graphic on The Blob's window. Now I have about a half-inch unobstrusive, pale blue green square in the corner below A-Dock's trash. That's plenty large as mouse/trackpad target.
Yeah, you have to enable the blob in Cocktail, Onyx, shell, whatever. Try the 'desktop square' option. . very cool.
Drop any graphic on The Blob's window. Now I have about a half-inch unobstrusive, pale blue green square in the corner below A-Dock's trash. That's plenty large as mouse/trackpad target.
Yeah, you have to enable the blob in Cocktail, Onyx, shell, whatever. Try the 'desktop square' option. . very cool.
![Cool blob future mac os x Cool blob future mac os x](https://bs-uploads.toptal.io/blackfish-uploads/blog/article/content/cover_image_file/cover_image/13650/cover-0828_AfterAllTheseYearstheWorldisStillPoweredbyCProgramming_Razvan_Newsletter-2b9ea38294bb08c5aea1f0c1cb06732f.png)
Okay, I'm a little lost, so please bear with me. I used OnyX to turn on the blob and now the windows don't go to the sides when I hit F10.
If I go to Terminal and type
'defaults write com.apple.dock wvous-olddesktop -bool true'
minus the quotes, will that fix it?
If I go to Terminal and type
'defaults write com.apple.dock wvous-olddesktop -bool true'
minus the quotes, will that fix it?
D'oh!
F11. The one that's supposed to show the desktop.
F11. The one that's supposed to show the desktop.
I tried this in Panther and not only could I not get it to work, I lost my second monitor.
So far I have not been able to get it (the monitor) to come back. If I reboot into 10.8 which I have on another drive the monitor is still off but if I re-power it if comes back and works fine, until I start up in Panther again when it disappears.
I have a G4 mirrored drive door that is original except for two extra internal drives.
So far I have not been able to get it (the monitor) to come back. If I reboot into 10.8 which I have on another drive the monitor is still off but if I re-power it if comes back and works fine, until I start up in Panther again when it disappears.
I have a G4 mirrored drive door that is original except for two extra internal drives.
10.8? What are you, part of some super-secret developer program from the future? :D
When you said 10.8, did you mean 10.2.8? Expose is only a feature in 10.3 and higher.
If you added information to your com.apple.dock and you are using Jaguar, I'm guessing that you are going to have to remove it somehow. And I'm afraid I don't know how to go about doing that.
Does this affect all users, or just your current user?
I hope this helps, if only a little.
If you added information to your com.apple.dock and you are using Jaguar, I'm guessing that you are going to have to remove it somehow. And I'm afraid I don't know how to go about doing that.
Does this affect all users, or just your current user?
I hope this helps, if only a little.
Future Mac Products
robg.. Looks like you've got a secret (software engineer) admirer:
http://www.versiontracker.com/dyn/moreinfo/macosx/21323
-Jesse
http://www.versiontracker.com/dyn/moreinfo/macosx/21323
-Jesse
Does changing the images change its size, or is there another way?
I would find this feature really nicely useful if I could make the blob a little smaller and toss it in a rather specific place on my screen (currently unoccupied) but it is too big right now.
I would find this feature really nicely useful if I could make the blob a little smaller and toss it in a rather specific place on my screen (currently unoccupied) but it is too big right now.
Put the blob mostly offscreen in a corner and then you have a little blue semi-circle that when clicked triggers expose as noted in the hint. I put it off the bottom-left corner. Just a simple way to make the blob smaller. I like it. Of course you can set the corners to trigger expose just by moving to the corner, but I find that with such settings I frequently accidentally trigger expose. Gets annoying. The blob off the corner works much better for me. I wish I could set the default action to be show all windows instead of current apps windows. Any way to do that?
---
--- What?
---
--- What?
![Mac Mac](https://img.17qq.com/images/gdjhdojz.jpeg)
I thought this would be pretty slick, but alas, when I enabled the Blob, and then tried to move it, I couldn't get the mouse pointer to drop the blob anywhere. The Blob stayed glued to the pointer. The keyboard could still talk to the computer, but the mouse was worthless (except as a Blob Bellboy).
Now, here's the setup for what it's worth: an AGP 400 with a kensington pocket mouse.
I'll just stick to slamming the mouse into the lower left corner..
Now, here's the setup for what it's worth: an AGP 400 with a kensington pocket mouse.
I'll just stick to slamming the mouse into the lower left corner..
I pulled the images out and shrunk them by 50% - works much better for me. Like others mentioned, the original was just too big.
I have panther, and I have enabled the blob, however I can't get rid of it. I've tried restarting after setting the bool value as me, and as root, and killall Dock. Nothin. If anyone has any advice let me know.
Time mysteries: inheritance mac os.
Time mysteries: inheritance mac os.
Ok, I fixed my problem by going to System/Library/CoreServices and then opening the dock package, then deleting the floater images. I archived them incase I want it back..but if anyone else had this problem that is a way to fix it.
I wish I had never seen this page. Right after typing that blue blob line into Terminal, my Kensington MouseWorks stopped working. I typed the 'false' line to get rid of the blob, but MouseWorks still isn't working. I uninstalled, reinstalled both the latest beta and the older final, to no avail. I think it did something to the dock, because as the system boots up, the MouseWorks drivers ARE working (the mouse moves very smoothly), and only cuts back to normal mouse movement when the Dock comes back up.
So my question is: what can you do to restore the Dock to the way it was before I typed anything into Terminal?
So my question is: what can you do to restore the Dock to the way it was before I typed anything into Terminal?
TransparentDock from
http://www.freerangemac.com
has a prefs selection to turn this puppy on and off
http://www.freerangemac.com
has a prefs selection to turn this puppy on and off
How come the Desktop effect on desktop is being ghost to the montior? When I click or drag anything on my desktop in same location as Desktop effect is at and it acted like the screen is locked into exact same form as Desktop effect..
---
www.artistz.tk
---
www.artistz.tk
This is all great. I love the blob - my favorite way to activate Exposé. However, one question: how do I make the default action when I click on it the arrange-all-open-windows rather than the application windows of the current app? I would rather have all windows be the default and use the Option-Click combo for the other. (Too bad right-clicking with a two-button mouse doesn't do this!)
---
iMac 17, OS 10.3
---
iMac 17, OS 10.3
This works well if you setup an AppleScript or Platypus app to turn it on and off. More info on Platypus here http://sveinbjorn.vefsyn.is/platypus .
to make a Platypus app I used TextEdit to make two one-line scripts. One to turn the blob on, and one to turn it off. Put the following line in TextEdit:
defaults write com.apple.dock wvous-floater -bool true; killall Dock
(change true to false for the script to turn it off.) From TextEdit's Format menu choose Make Plain Text. Save the script, then drag-and-drop it into Platypus and click 'Create'. Do the same for the script to turn it off, then put your Platypus apps in your Utilities folder, or where ever you may want to keep them.
Likewise, in AppleScript, this script will run the command in a terminal (if you don't want to mess with Platypus):
tell application 'Terminal'
activate
do script with command 'defaults write com.apple.dock wvous-floater -bool true; killall Dock'
end tell
to make a Platypus app I used TextEdit to make two one-line scripts. One to turn the blob on, and one to turn it off. Put the following line in TextEdit:
defaults write com.apple.dock wvous-floater -bool true; killall Dock
(change true to false for the script to turn it off.) From TextEdit's Format menu choose Make Plain Text. Save the script, then drag-and-drop it into Platypus and click 'Create'. Do the same for the script to turn it off, then put your Platypus apps in your Utilities folder, or where ever you may want to keep them.
Likewise, in AppleScript, this script will run the command in a terminal (if you don't want to mess with Platypus):
tell application 'Terminal'
activate
do script with command 'defaults write com.apple.dock wvous-floater -bool true; killall Dock'
end tell
It still works beautifully with Tiger
my blob disappeared.. 10.3: Enable the floating Exposé blob
Running 10.4.10 on a new iMac; I got the blob to appear ONCE, when I tried to click and drag to another part of the desktop, it zipped way off to the upper left of the screen, so that only a slice of it was still showing; when I clicked on that, it disappeared entirely, never to return (despite multiple attempts using defaults write com.apple.dock wvous-floater -bool true and false) -- any suggestions??? I would love to have it back..