If you wondering how reach the WatchKit contextual menu (associated with the current interface controller) using the iOS Simulator, just click and hold the screen for 2 seconds and the menu will appear. yay!
If you wondering how to change your Personal Hotspot name on your iOS device, you basically need to change the name your device (iPhone, iPad or iPod).
Today I was using Django 1.3 with an existing Oracle database and got the following Oracle error in Django Admin when trying to save a form that updates a model class that refers to a BLOB type column:
ORA-01465: invalid hex number
The afforementioned model was using a simple models.TextField that works fine to display the BLOB data (currently holding XML data). So my approach to fix this problem was to create a custom column Field for my model that extended this class models.TextField. I’ve used the following code:
class OracleBlobField(models.TextField): def get_placeholder(self, value, connection): return "UTL_RAW.CAST_TO_RAW(%s)"
With this code, your model’s SQL UPDATE will convert the String you are submitting into a raw value in Oracle that saves the data correctly.
Then on you Django Model just use it, such as:
object_blob = OracleBlobField()
Hope it helps.
Great! iOS 4.3 is out with this new Personal Hotspot thing which enable you to share your iPhone internet connection via Wifi, to devices around you. Something some Android versions and MIFy could do it for some time now.
As usual with Apple it’s really easy to use, as to just turn it on the from the Settings app, Personal Hotspot menu.
It will start sharing your internet connection with a given password via Wifi and USB at the same time, if you have the iPhone connected to your Mac. There’s also a 3rd option to share it via Bluetooth only, as well.
Although very easy to use, you can’t change the Wifi name SSID, at least on the phone (bummer..). This name is taken from your iPhone name in iTunes.
So my tip, in order to rename your Wifi SSID you need to change your iPhone Name on iTunes. Just take a look at the screenshot on the left.
Easy, now your Personal Hotspot Wifi name is renamed to whatever you want.
It’s been a month since I’ve upgraded to the new Canon 7D from a Canon 450D (Rebel XSi), so I it’s time to share a small review about it.
I am a starter passionate photographer therefore I’m orienting this post to a very simple review more focused to the user experience with the camera and not so much the ISO comparison and pixel peep you will find in many other reviews. That said, I will present you some of the features I really love in the Canon 7D that are more than worth the upgrade from a Canon 450D.
The Canon 450D was my very first DSRL and bought it almost on the first month it came out. I loved it and still do! But the 7D is another level.
Since every single feature from the 7D compared with the 450D was so much better, I’ve decided it was worth the upgrade. This is in fact the only reason the upgrade started to look more appealing. Comparing to the new 500D (Rebel XTi) wasn’t worth the investment just solely based on supporting video.
Together with the camera I’ve also extended the upgrade from my Slingshot 100AW to the 200AW version.
Never had the chance to hold a Canon 7D on a store. They were released recently and none of the camera shops I usually visit in Portugal had it available. Only FNAC had one in exhibition behind a store window. So I’ve extrapolated that it would much feel like the Canon 50D in terms of hand holding but probably better built.
Ordered online and received it at home early December, together with a Sandisk Extreme (60MBps) 16GB CF card and a Slingshot 200AW.
Unboxing products is always an exciting experience, and my very first contact with the camera was mind blowing: This is camera body is really rugged, extremely solid and you feel like a pro holding it. It felt like owning a crappy Dell plastic notebook and upgrade it to a sexy aluminum Macbook Pro.
I’ve hold the review for about a month to let my brain rewire completely to this camera. Reading and rereading the whole manual is crucial to understand what you can do with it. Works a bit differently from the Canon 450D (nothing to much), but pretty similar to the 50D.
The first improvement I had to adapt was the presence of two Dials, crutial to control Shutter Speed and Aperture very quickly.
Other one was that now those easy access features you have on the right-side of your 450D LCD (AF-Drive, WB, etc) now are controlled on the top of the camera, over the smaller 7D LCD.
After one week of shooting every day, all controls started to feel more natural and easier to use.
All features from the 450D are present on the 7D, but let me talk you about some of the best that are worth the upgrade and some that can be improved.
This camera is almost perfect to me (there is always room to improve :) ). Definitely worth the upgrade in every single way because it beats the 450D feature by feature, and it does what I want.
Build quality, features and image quality are stunning for a cropped sensor camera with 18 Megapixels. If I was canon I would stick with a “only” 12 Megapixel sensor. But I understand the marketing pressure to deliver more and more megapixels. Well, it’s really useful for Sports or Nature photography with fast long lenses where cropping is king.The downside goes to the RAW filesize for being around 30 MBytes, but acceptable since disk space is now cheap.
Canon 7D ISO6400 looks equivalent to ISO1600 from the 450D, which is usable. One feature I expect Canon to implement is the ability to define a maximum ISO in the Auto ISO. I would like that my pictures won’t surpass ISO1600 in Av mode. Currently ISO3200 is the static maximum automatic ISO and cannot be changed.
Other feature it could have is an internal focus light to focus under low light conditions. Using the flash to achieve this purpose is not feasible in a strobist multi-setup flash. You can always use a flashlight to achieve the same functionality but it would a nice plus to have. (Humm, maybe I can disable the internal flash completely, never though of that :) ).
That’s it. I’m really very happy with the Canon 7D, and hope this small review helps you for your choice.
Leave feedback if you liked.
P.S: I’ve left aside all the polemic issues as some of bad body copies, miss-configured AF systems, diffraction due to smaller pixel size, front/back focusing, etc., because honestly I haven’t experience any of the problems some guys are praying. Dig into dpreview and you’ll get the whole discussion.
Have you ever tried Internet Sharing in Mac OS X for Ubuntu clients, using WEP? Did it work for you at the very first time? If not this post is for you… :)
I own a 3G HSDPA internet card for my Macbook Pro and I need to share my connection to my Ubuntu laptop.
Easy, you goto System Preferences, select Sharing icon and click “Internet Sharing” for computers using Airport. If you don’t use WEP to encrypt your Wireless connection you’ll have one open Access Point to the world. So I need to use WEP to secure my network since Mac OS X Leopard does not create wireless networks with encryption other than WEP… damn!
Ok, lets create the wireless network and place a password. The problem with this “password” is that when you try to use Ubuntu NetworkManager it simply doesn’t work. Still don’t know why, but I believe it’s a Mac OS X problem, since my Windows box doesn’t work either.
So instead of typing a simple password, use a hexadecimal WEP key. Let’s consider you choose a WEP key in hexadecimal form 1234567890. You need to create your network in Mac OS X with the following key: $1234567890
The “$” tells Mac OS X the key is in hexadecimal and not a simple pass phrase. Hexadecimal keys must be 10 chars wide for 40bit WEP or 26 chars wide for 128bit WEP.
Now use the same key in Ubuntu and NetworkManager but without the “$“.
If everything went fine you’ll be able to share your internet connection.
Today I needed that my bridged interface for my Linux Virtual Machine in VMWare Fusion was bind to the Airport network card instead of the wired ethernet card. I wanted that may wireless hosts could access my VM in the wireless network from other hosts.
By the way this was an Ad-Hoc network created with Internet Sharing option in Mac OS X system preferences, so that I can share internet to my home.
In order to VMWare Fusion start to bind your virtual bridge interfaces you need to edit the file at:
/Library/Application\ Support/VMware\ Fusion/boot.sh
Locate in the file the following code:
# vmnet-bridge puts itself in background (daemon mode) # Bridge to host network interface 'en0'. #"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0 # Bridge to the primary host network interface (which can change over time). "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''
And change to this:
# vmnet-bridge puts itself in background (daemon mode) # Bridge to host network interface 'en0'. "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en1 # Bridge to the primary host network interface (which can change over time). # "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''
Notice I’ve change the en0 interface (the wired NIC) to en1 (the Airport).
Restart VMWare services, including vmnet-bridge by issuing the following command:
sudo /Library/Application\ Support/VMware\ Fusion/boot.sh --restart
Yeahh.. Now my VM discovered an IP address on the wireless network. (DHCP was running on the Airport interface since I was using Internet Sharing in Mac OS X Leopard).
So today I’ve been struggling with MacPorts in order install Git with Perl 5.10 and not perl 5.8 (since I have already installed Perl 5.10 and I don’t want two different version of Perl in my system). After reading something about it I came up with a simple solution by overriding the Portfile from the Macports installation. Its easy as:
1. Edit your /opt/local/etc/macports/sources.conf and place the following line on top of the file:
file:///Users/< your username here >/.ports/ [nosync]
this will make “.ports” directory the local repository for the MacPorts.
2. Create directory structure for “git-core” package:
$ mkdir -r /Users/< your username here >/.ports/devel/git-core
3. Download the Portfile for git-core into the created dir:
$ cd /Users/< your username here >/.ports/devel/git-core $ wget http://trac.macports.org/projects/macports/browser/trunk/dports/devel/git-core/Portfile
4. Change the runtime dependency from perl5.8 to perl5.10 by editing the file Portfile and changing the depends-run directive. It should look like:
depends_run port:openssh port:rsync port:perl5.10 port:p5-error
Also remove the patchfiles directive because the patch does not exists anymore:
patchfiles patch-Makefile.diff patch-http.h.diff
5. Run the portindex command in “.ports” dir. You will be presented with an output like:
Creating software index in /Users/Braceta/.ports Adding port devel/git-core Total number of ports parsed: 1 Ports successfully parsed: 1 Ports failed: 0
6. Now install the “git-core” normally as you usually do, but now the dependency is fixed:
$ sudo port install git-core
If you look at the steps here you can also learn more from the MacPorts packaging system and override other package definitions it you want to! Hope it helps :).
What’s cool about my previous post is that it still works for Aperture 2 :).
I bought myself during this Christmas a Canon Digital IXUS 860 IS compact cam (a personal review will come in further posts).
This my new hobby made me realize I need some photo management software. I own iLife 08 from Apple, which includes iPhoto 08 (simple for basic tasks) but I’m really considering use another app more powerful. I came across to the, yet sometimes flame war, discussion between LightRoom and Aperture.
While trying to install Aperture 1.5.6 (trial version, btw) I received the following message:
“Your video card does not meet the minimum requirements to run this software”.
Howcome is this possible, if the Aperture Compatiblity Checker app certifies successfully my laptop?
Looking into Aperture hardware minimum requirements I have ensured in Apple site that it should work on my laptop, which is a:
After tinkering around with the Aperture installer I have found a way to overcome the installation checks in order to install it on every Mac you own (I won’t guarantee your hardware can run Aperture, but at least you can now install it. :) ):
Cool! You will be able to install Aperture without verifying hardware requirements first.
Poking into the installationCheck() script, the GeForceGo 5200 seams to be blacklisted by Apple (still don’t know the reason). Even thouhg it does not perform extremely fast, it works fine to me. No problems found yet.
Hope it helps :).