Skip to main content

Best Leopard Feature

I received my copy of Leopard today, and promptly installed it.  Aside from having to dig up some serial numbers, it went off without much hassle.

While most of the media is focusing on features such as Time Machine, Spaces and the new UI, I found one lesser-known one that is sure to put a smile on any Mac user's face.

Not only did Leopard seek out and find potential Windows shares, it has a very, shall I say, "appropriate icon" to represent them:

Comments

Pete Scott said…
Wow! - and today's the day I order my new Mac Book Pro...
Just hope it will work with all my new colleagues' virtual machine demos written to run on Tiger.
Scott said…
Pete,

VMWare Fusion RC1.1 is designed to work with Leopard. I'd recommend upgrading to it. My existing VMs worked without a hitch once I installed it.

Thanks,

- Scott -
Anonymous said…
Hi Scott,

Did you go for an upgrade or a fresh install?

John.
Scott said…
I did a clean install, more because I wanted to clean up a lot of unused apps than anything else.

If you opt for this route, make sure that you backup EVERYTHING - iCal & Address Book are not compatible between Tiger & Leopard, so export to iCal and you will be OK. Same goes for Stickies.

Even small things, such as the custom display that you use for Adium for example, should be backed up or at least noted.

Good luck!

- Scott -
Anonymous said…
Funny, indeed :-)

But perhaps this will wipe the smug smiles off the faces of Mac users:

http://discussions.apple.com/thread.jspa?threadID=1195031&tstart=15
Scott said…
No one said Apple was perfect. Also, a blue screen is different than a blue screen of death...

It also goes to show that technology is technology; ALWAYS back up data before doing anything major to your system. Unfortunately, most people don't do this and learn the hard way...

- Scott -
Anonymous said…
That is so funny....
I can't believe they kept it there too! I have 4 computers in my house and 3 of them are windows computers. So now i have 3 BSOD on my screen :)

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p