Another iOS, new SDK and new features. Users are happy, and developers are ready to dig into APIs.
Answer by Aasim Naseem Siddiqui:
Well .. this is really a controversial piece of hieroglyph in the temple of
Abydos. Some people (who claim that Egyptians had some contact with aliens) believe that this hieroglyph is real and in original form.
Some other says that the carving was altered by the successors of Ramses II (may be Merneptah). It was a common practice among Pharaohs of Egypt to destroy the symbols and glory of their forefathers, in order to showcase themselves. Example is Hatshepsut’s temple at Deir el Bahri, where statues and wall paintings were destroyed by her own son.
The temple of Abydos was build by Seti-I and finished by his son Ramses II, greatest of all Pharaohs. So it is natural that his successors tried to erase the trans of RamsesII from the mind of common people, and brought their own image at front.
My personal believes are, even if the hieroglyph were re-carved, the exact resemblance of modern tools/weapons in more then five different shapes leaves too many questions to explore. Merely saying it is a result of re-carving doesn't justify the situation. There is lot more to explore.
Few days back, I was on visit to #WalledCity of #Lahore, and I stayed at historical #Badshahi Masjid. The glory of this masterpiece again forced me to take my cam to capture few clicks.
You can find rest of the photos on my Flick album Ever Lasting Art of Badshahi Masjid Lahore Pakistan
Waiting for your comments there (:
If you are having following issue on new interface of iTunesConnect
“Redundant Binary Upload. There already exists a binary upload with build version ‘1.0’ for train ‘1.0’”
then you are not alone like forever alone guy. Like me and you, many others are facing this issue. But no worries, the solution is pretty simple.
More than one binary may be uploaded to iTunesConnect if the the Build number (Select the Target, then Xcode -> General -> Build, see the picture below) is increased by adding
.1, i.e. if the version is
3.75, then increase it to:
3.75.1, but the Version is still `3.75 for the App (also in iTunesConnect). The build number just has to be unique for each binary that is loaded up to iTunesConnect.
After a new binary is uploaded and processed (~ 10 min), then you can select the new binary and submit it for review. In the picture below you may see the old and the new binary listed in iTunesConnect in the Build section of the current App version (you click the plus sign). Then the new binary is selected ->
Submit for Review. (Sometimes an error comes when submitting, then just try after a few mins or upload a new binary).
For those inclined to do this automatically with an Xcode script, here is a description of making an automatic script for updating Build numbers Better way of incrementing build number?
Note: The content of this post is extracted from this question over stakeoverflow.
Alhumdulillah first printed edition of LAFZ magazine is out now. We worked really hard to make this moment possible today. Whole team, specially Yaseer Ali Choudhar (@yac_ali on Twitter) deserves big claps.
My article also made his place in this edition. This is about empress Nur Jahan of the Mughal Empire (1577 – 1645).
You can find my other articles in LAFZ magazine about
- Masjid Wazir Khan, Lahore Pakistan. Issue – 12, Page 148 to 167
- Empress Razia Sultan (1236 -1240) Issue – 5, Page 80
- Empress Mehr-un-Nisaa (1577-1645) Issue – 3, Page 136
- Princess Zēb-un-Nisā Makhfī (1638 – 1702) Issue – 2, Page 76
Stay blessed …
So I have finally moved to #Flickr, for all my photography stuff. It was no doubt a long journey with #Picasa but after much consideration I finally vote for Flickr. Leaving Picasa was a sad moment as I always prefer to use #Google products (all solutions in one box) but due to some constraints Picasa wasn’t fitting with my needs.
The main reason was storage capacity. After having Canon EOS 100D as my professional camera, the need of more storage was inevitable. 1 terabyte of Flickr vs 15GB of Picasa is a huge difference, and this thing gave me really a breath of relax. As advertised over Flicker home page, 1 terabyte = 537,731 6.5 megapixel photos, and even if I chose high resolution photos of my cam .i.e. nearly 13 to 14mb per photo, even then there are 218,453 photos with 16.0 megapixel that I can upload over 1TB of free space. Waoooo … incredible.
You can find some of my click at https://www.flickr.com/photos/114820437@N08/sets … though they need to organize a bit more right now.
One interesting things is, I’m still using Picasa desktop tool to organize and edit all of my photos. There isn’t any match of Picasa desktop tool with any other photo organizer+editor. Here Picasa takes the stage.
Don’t you think that editing and organizing them in Picasa and uploading them over Flickr is something injustice with Google!!! ((:
Sometimes, I feel like this.
Hey .. how’s work going? It’s good Han !!! … good good … So you have done with your release and verified with QA after some bug fixing; That’s great; You done a good job;
Now Its time to share the Adhoc with client; Ok … so what would you do? You will probably generate an IPA and attach it in email along with release notes.. right ??? Or you will upload it over some ftp/dropbox to let the client download and install it via iTunes … han??
Well… orite .. that’s fine.. but you know what? In both cases when client has an IPA file, he/she has to use the iTunes to sync your app in device, and in case he is away from his desk (or wants to reinstall it after deleting the old installation) he is stuck ..
Listen .. you are missing one thing here … when you have IPA files and iOS version > 4.0, you should use the web-based, wireless distribution of Adhoc apps and the ability to embed provisioning profiles right into the IPA bundle; Your test users can now install the builds without ever using iTunes at all; Doesn’t it sound good? Read the rest of this entry »