Thursday, July 2, 2009

Changing cats

As I probably told in my earlier posts, MacBook is not the only one Mac in my household. Actually, it is not even the first Apple computer, but third - after two (almost) identical Minis.

Yesterday, I visited my local Apple dealer and upgraded my 3 years old Mini (that's first Intel-based Mini model), putting 2 GB of RAM instead of 1GB I had on board from the beginning. But besides the hardware upgrade, I also decided to get latest software titles, so I bought a Mac Box Set, which includes Leopard, iLife '09 and iWork '09.



Coming back to my place, I did a full backup of Tiger partition to external hard drive to ease my paranoia, and in the evening I was ready to fire Leopard install. This was the first experience of installing Mac OS for me, because before, I always bought a new computer with OS coming pre-installed. To be honest, installation (at least upgrade from Tiger to Leopard) is pretty boring comparing to Windows install. The latter tells stories about OS features - at least something changes on screen, but the former shows just giant letter X and a progress bar.

In less than hour, (which felt much longer,) I was greeted by already familiar Leopard screen with nebula on the background and a new shiny Dock. I finally disabled PathFinder application from automatic starting up on login, and started checking old applications for functioning. Here where we got some surprises.

At first, Upgrade to Leopard broke Mail application. It shown a folder structure, but not a singe mail message. Fortunately, the first URL returned by Google about how to fix this problem was very helpful. It seemed that during OS upgrade, Mail received some strange defaults that prevented him to display information correctly. After cleaning up bad defaults, Mail prompted for importing old mailboxes, and after 2 attempts and ca 40 minutes, all 10 thousand messages were in place.

Next failed application was NeoOffice (native port of OpenOffice for Mac). when asked to open some DOC file, it loaded up himself, but then did not want to do anything. Trying to open the same document by choosing Open from File menu also did not have any effect. To cure this, I put old version of NeoOffice to Trash and got a new version off the web. After that, document became loadable, but few minutes later I inserted a CD with iWorks and hopefully this will make me forget about OpenOffice, either native or X-version of it, whatsoever.

Upgrading an OS was also a good reason to give a boot to software titles that were rarely or never used, as well as downloading new versions of "good" programs. FireFox 3.5, newest Google Earth. There were no newer Picasa, and the old one is still crashing as badly on Leopard as it did on Tiger. But well, I have hopes on iPhoto '09 which will get installed later today.

Safari 4.0 needed OS X 10.5.7, while Leopard that comes in Mac Box Set has version number 10.5.6. So I could install it after running Software Update and rebooting.

Thursday, January 1, 2009

Happy New Mac-Year!

Well, technically, Year of the Mac is close to its end. With the change of last digit in year number I can say I am not Mac-beginner anymore. I was quite poor advocate of the platform during last year and did not convert anyone to Mac-world, but this wasn't the point of this blog. I am glad if my posts were useful for anyone, but they were written for myself in the first place. Occasionally, I will continue to publish some new thoughts about using my Macbook. Happy new year!

Friday, October 24, 2008

iPhoto Performance

My next post tells about the issue I went through, and which is happening with lots of people out there, as I can judge from Google search results for "iPhoto performance". Yeah, that's it - at some point of time people realize that they have more pictures in their library than iPhoto can easily handle. I dug enough and I found some heplful advices addressing cure for this problem. Now I am much wiser and can share my experience with others.

So, let's begin. In our household, the main photo library lives on Mac Mini that we have in our living room. It has beautiful matching external HDD from Lacie (when I bought it, 250G seemed so large number. No, after almost two years, we are constanty searching for something to be deleted in order to have some space left) where we store photos, music and movies. iTunes is still rocking - it handles more or less finely about 80G of music, and I just see how it evolves with every version. Unfortunately enough, iPhoto is not automatically updated in the same way as iTunes, so I am forced to cope with iPhoto 06 version (unless I am ready to buy iLife '08 - and I think I could use that money wiser).

Note: iPhoto'06 is installed by default on all Tiger machines. Leopard comes with iPhoto'08 by default. So, this post is for Tiger users. Leopard users have more advanced iPhoto not only in terms of features, but also of internal structure, so the following recipe will not work for it anyway.

In 4 years we got about 20 thousands photos. Finally, iPhoto started to use all resources of machine when used. Computer started to swap frequently and become barely responsive for some times during the day. It clearly needed some action.
First very quick googling on subject suggested splitting a library into several parts and showed some software titles for helping with this. I downloaded some and started playing. Freeware or not, software was not able to pick up photos for moving to new libraries by any useful criteria except album-by-album. This one is great, but I wanted to split libraries by year. That was not possible. Selecting albums that belong to one year or another would be a tough task, and besides that, not every picture from the library ends up in some album.

So, I went a hard way of not using third-party library splitters. In the end, this way was not very much harder in terms of work to be done. If you have the same problems that I had, then read further, but before specify the criteria, by which you will split your library. Sticking to these criteria is the only thing that you really need. I selected year of making a photo to be the only criterium.

Before you split your library, I would recommend to back it up somewhere. DVDs will not suffice, so youd better copy iPhoto lirary to some external USB drive of reasonable capacity.

The process of splitting the iPhoto'06 library in two parts consists of the following steps:

1. Find out where is your iPhoto library located. This should be a folder for the library that holds all the information (photos, their midifications, tags, thumbnails, albums etc) inside. You will need to memorize where this folder is located (you will need it in futher steps. You also need to find a place for a new library (since you are splitting the old library, it means that you will just move some of information to a new library) - memorize or right it down for use on next steps. Locating iPhoto folder is easy - right-click on whatever photo in your library, and choose "Show File" from the menu. Finder window will open with the file selected. Now if you right-click the title bar of the finder window, you will see the full path of the image file, which will of course also include the iPhoto library folder itself. On this step, you might also want to do the backup of the old library as I suggested above.

2. Create new, empty library. You don't need any third party software for that - just hold the Alt key while starting iPhoto. This will not start loading the whoe library, but gives a simple dialog, that has allows either choose a different library, or create a new one. Choose "Create Library...". You will be asked where to put it. After you provide a name and path for new library, you will have a new folder where all library files will be stored. If you divide your library by year, just give a name like iPhoto2006. New empty library will be loaded and presented to you. That's ok. Now, close iPhoto.

3. Run iPhoto with holding Alt key again - this time press "Choose Library... " button and navigate to the folder you memorized during the step 1. You can see your old library - now take a look at the very top of the list of albums, where we have photos already sorted by year by iPhoto. In brackets after the year number, you can see how many photos you have from these years. If you are like me, you might have 2-5 thousands of photos per year. That's the amount of photos that iPhoto easily handles, and that's why it would be a great idea to have just one year per library. If you are a photomaniac, and have more than 10 thousands of photos in one year, I would still recommend to create a separate library for each year, and then divide them even further until the sizes of libraries will be ok for iPhoto to handle. Write down how many photos are for each year, and decide if you will put some years together. Close iPhoto.

4. Now you are ready to split the library in two parts. If you created a new library for photos of year 2006 during the step 2, you need to copy these copies to a new iPhoto library folder. For that, copy all files except Data, Modified and Originals folder to a new library's root folder. For these excluded folders, create their empty counterparts in new library's root folder, and then copy only 2006 subfolders from old library to a new one. Be sure you are not moving the files - if both old and new libraries locate on the same hard drive, then OSX will by default move files if you drag and drop them. Since you created a new library with iPhoto, there were already some files in new library's folder - it's ok to overwrite them.

5. Now you have all the photos for the year 2006 copied to a new place, as well as information about ALL photos of your old library. So now, we need to fix this mismatching. Run iPhoto with holding Alt key and choose the new library. It will open as if it would have all the photos from the old library, but instead of thumbnails, you will see empty boxes for each photo which is not made in 2006. And that's ok, because we copied all iPhoto files from the old library. Now return to the sidebar where you have information about distribution by years. If you click any folder except 2006, all you get is set of empty boxes. Mark all empty boxes with Cmd-A and press Delete. This will remove _references_ to photos that should lay at Data, Modified and Originals folders. After we remove these references, albums listed below will be updated with real number of photos. If you see that album is empty (zero in brackets after the name of the album), you can safely delete it, too. After you did this, you are done with making a new library

6. Now after new library is ready, you might clean up your old database from photos that were moved to a new library. Remove 2006 folder from Data, Originals and Modified folder for old iPhoto library and then clean library from the references in the same way as I described in 5.

7. Repeat steps 2, 4, 5 and 6 for all other years you want to fork to new libraries. You can even skip step 2 if you create a folder for new library manually. You can just create a library root folder in desired location, and proceed with copying files. When copying files, be sure that you take them from the library that knows everything about photos that will be moved to a new library.

That's it. I hope this instruction helped someone

No news is good news

Well, readers of this blog might be surprised with my long silence, or even dismissed the idea to read new posts.
Really, I have been out of reach for some months - but that's actually very good to explain my MacBook experience. It is became a really handy working computer, which allows me to do everything that I need in my daily work. I just use it so extensively that I don't have any time left to share this with outer world.
I think I have no anything new to add about my experience with hardware - it is still fast enough after so long time, it is still in good condition (I have just my keyboard a bit dirty and touchpad and some keys on keyboard too much polished with my fingers), it is still quiet (my PC-laptop started to be very noisy after month or so of usage). Windows is still working happily inside the virtual machine. Everything is just fine.
So, probably they won't be too much of hardware posts in the future. Come back to read my adventures in Mac's software world. :)

Wednesday, July 23, 2008

PHP development

The one thing that keeps me busy with my MacBook is PHP development. Before I bought it, I guessed that XCode (Apple's own IDE) is a great thing and that many open-source items are pre-installed on Leopard... But after some time I gave it a try and configured my machine for local PHP-MySql development. MySql was missing, but Apache was also conviniently preinstalled, so I had my MAMP workstation ready in less than a day. Before that, I even tried RoR, but decided to stick to my own PHP framework.

I was so eager to test how PHP development looks like that I even started re-design of the framework, throwing out the only part that wasn't programmed by me (and it was an MVC framework knows as Fusebox). Before, I had my development on hosting server. Now, I have ultra-fast development environment with all the components running on my own machine. I even started to think about such things as performance (oddly enough, my own MacBook executes my scripts much faster than my hosting server does).

XCode is great tool, especially for its price tag, which is, as you know, zero. IT may be lacking some features of Eclipse and Visual Studio, but I would not use those features anyway, they are too difficult for me. There are no intellisense, breakpoint debugging and refactoring for PHP, but ultra-responsive IDE with code folding and syntax coloring covers all my needs. The one thing that bugs me a bit is that I did not find a way to have Tabbed interface for open documents, the way like Eclipse and Visual Studio are doing, but I used to this. I am now much more creative than on Windows before.

Appearance and built quality

I have not written for ages to this blog. This is not because I stopped to get new experiences, but maybe because using a Mac became some sort of routine when you lose the feeling what could excite readers of the blog. I switched to using Mac for some months, and my previous laptop, which is Dell, is just occupying a space on my desk, and I really infrequently open its lid just to log in to have my machine listed in the domain...

Well, using the machine for 8+ hours a day, I can now tell you guys how machine withstands my usage. In brief: pretty fine, but I can notice it's not brand new anymore. Touchpad became shiny in the center, buttons of the keyboard are a bit grey instead of white, and some plastic next to keyboard degraded and a small chink emerged. Other than that, chassis is still solid, details are attached to each other as on the day 1, there are no arbitrary detaching accumulator as on my estonian-made PC laptop. There are no even ugly scratches on the chassis, despite the fact I don't have a fancy bag for it and put it straight to my backpack.

What is great, is that battery life is still normal. Even with Wifi turned on, MacBook achieves 4+ hours of working time. I never take my AC adapter with me when I go home. I just don't spend enough time behind the computer screen at home so its battery life never ends as a surprise.

Monday, March 17, 2008

Tiger to Leopard

I already owned a Mac before Leopard jumped over IT world. I had Tiger running on two Minis. I wasn't inclined to updrage this machines to Leopard, as many people did with their old hardware the day when Leopard arrived. But after I've got MacBook with Leopard preinstalled, I can say that new cat is definitely more advanced than its predecessor.

I like new sidebars in Finder and Mail. I love the new Preview with Cover Flow. I kinda like how the new Dock looks like. Transparent menu bar is reminding me Vista's Aero, but it is still less annoying. I don't use a Time Machine, because with standard hard drive it is meaningless (and I suppose that synchronizing VmWare's virtual machines is not what I really want). But some new features are really, really slick.


As much as I was addicted to Exposé and Dashboard in Tiger, I was instantly hooked by Spaces and Stacks. These two concepts are not at all new, they were done many times before Leopard, but in Leopard, they are as polished as only Mac app can be. No bloat, maximum comfort, aesthetic pleasure. Now if they only could implement something Quicksilver-like ;)


And out-of-the-box support for Ruby and RoR in Xcode is really surprising. It makes the fact that RoR developers are mostly Mac users pretty unsurprising :)