ziggythehamster

$ curl -A "mozilla/5.0" -v http://itunes.apple.com/us/app/the-far-islands-by-john-buchan/id327765949?mt=8
* About to connect() to itunes.apple.com port 80 (#0)
*   Trying 63.97.127.24... connected
* Connected to itunes.apple.com (63.97.127.24) port 80 (#0)
> GET /us/app/the-far-islands-by-john-buchan/id327765949?mt=8 HTTP/1.1
> User-Agent: mozilla/5.0
> Host: itunes.apple.com
> Accept: */*
> 
< HTTP/1.1 200 OK

ziggythehamster

From 7f36f1aefe5aea73cf3e01890740f4005f808fb8 Mon Sep 17 00:00:00 2001
From: Keith Gable <ziggy@ignition-project.com>
Date: Thu, 22 Dec 2011 23:28:31 -0600
Subject: [PATCH] Support SGH-I997 Infuse 4G in UDEV rules.

---
 heimdall/60-heimdall-galaxy-s.rules |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/heimdall/60-heimdall-galaxy-s.rules b/heimdall/60-heimdall-galaxy-s.rules

ziggythehamster

• TIMOB-6300 - getLogicalDensityFactor not documented. Needed to support advanced positioning across all Android phones.
• TIMOB-2229 - animate does not change properties. WONTFIX. I understand that values that aren't numerical (pixels) can't be changed and have it behave sanely, but that's why CSS has getComputedStyle. None of my coworkers thinks the official behavior makes sense at all without something like getComputedStyle.
• TC-447 - Maybe I'm a documentation snob (RDocs kick ass), but Ti.Android.currentActivity should be listed as a property.
• TIMOB-1910 - There needs to be a removeAllChildren because iterating the view's children and remove()ing them does not work.
• TIMOB-1650 - items property of Toolbar undocumented. Fixed in 1.8, I

ziggythehamster

@Appcelerator #Titanium #Sucks no. 1: Child view wider than a parent view breaks out of the parent. It should get cut off by the parent.

If you have a box that's 40x40, and position another 40x40 box within it, with top=20 and left=20, you expect to see a 40x40 box containing a 20x20 box, not two 40x40 boxes.

Titanium sucks because...

If you put a view within a view on any widget toolkit, HTML, etc. and then move the subview around within its parent, the subview should never extend beyond the boundaries of its parent. That is, it should be clipped by its parent. At least by default. This is all OK if it's supposed to work this way, but several Q&A posts suggest this exact method as a way to crop a photo. So did it get broken at some point? Are there not unit tests to determine when behavior like this is reversed? Is some way that I'm inserting this view causing it not to work consistently? Why do I see code that is exactly equal to mine

ziggythehamster

Grant R.: Let me take the hassle out of your housing search.  :) Where do you want to live? | urban squared realty | Grant Riley | 515 S. Congress, Suite 103. Austin. TX. 78704 | 512.761.7181 | www.fbook.me/gwr

foursquare_tip_id: 4d0575b092288eec1ef39be0
foursquare_user_id: 2838635
photo_url: http://playfoursquare.s3.amazonaws.com/userpix_thumbs/SOQVCR5HQWTFCRSL.jpg
name: Grant R.