懒人A的自救计划之做一个事...- 网站保险开发人员不可缺少...- 怎么创建一个ipa How to create an IPA (Xcode 4.3)

当前位置: 编程技术>移动开发

本页文章导读:

▪懒人A的自救计划之做一个事件揭示程序懒人A的自救计划之做一个事件提醒程序你们好，我是懒人A，懒人A就是我。我确实很懒，为了使我不再那么懒也为了过上好日子我决定开始我的自救计划。计划第一步: 提醒自己该做什.........

▪ 网站保险开发人员不可缺少的火狐插件网站安全开发人员不可缺少的火狐插件 hackbar：一些常用的sql注入语句等的工具。firebug：调试css和javascript等不可缺少的工具，这个应该算是网页开发人员不可缺少的。poster：可以发送一些.........

▪ 怎么创建一个ipa How to create an IPA (Xcode 4.3) 如何创建一个ipa How to create an IPA (Xcode 4.3) With the release of Xcode 4.3, Apple has made it even easier to generate an IPA. However, some of these changes have caused some confusion with some users. This tutorial will walk you through the.........

[1]懒人A的自救计划之做一个事件揭示程序

来源: 互联网发布时间: 2014-02-18

懒人A的自救计划之做一个事件提醒程序

你们好，我是懒人A，懒人A就是我。我确实很懒，为了使我不再那么懒也为了过上好日子我决定开始我的自救计划。

计划第一步: 提醒自己该做什么事情--我决定做个应用放到手机上, 每天中午12点告诉我还有什么任务没有完成。

黄天不负有心人, 经过几天的奋战应用已经基本完成，先上图

1.首页--查看未完成的任务

2.点击添加按钮--添加新任务

3.点击具体任务--任务详细

4.编辑任务--编辑任务描述

5.切换任务类型--查看已完成任务

关于技术选型

1.air on android。 UI部分使用Starling实现

2.考虑到flash弄输入框不方便, 所以输入框采用ane实现, 也就是说输入框是一个android的Activity

3.数据存储, 使用了LiteSQL。我对SQL语句十分不熟悉, 所以进行了一下封装弄到了一个DBSaver类中

4.关于每天12点通知, 这个也是采用ane实现。

最后是附件, 包括ane方android的项目, ane的打包项目, 以及as3项目。

不过有件坏事是: 我没写什么注释(请记住我是个懒人).

有意见和建议望交流, 希望你们成为我脱懒的一部分. 谢谢

[2] 网站保险开发人员不可缺少的火狐插件

来源: 互联网发布时间: 2014-02-18

网站安全开发人员不可缺少的火狐插件
hackbar：一些常用的sql注入语句等的工具。
firebug：调试css和javascript等不可缺少的工具，这个应该算是网页开发人员不可缺少的。
poster：可以发送一些http数据包后可以返回一些代码，这个可以发送任何的模拟包，可以查看网站对任何包返回的代码。
live http headers：可以用来实时监测发起的http请求和响应，也可以修改请求参数之后重新发起请求
tamper data：可以修改发送的一些数据，比如referred和x-forwarded-for等
refcontrol：可以使得任何浏览也都是使用某一个referred即来源页
Modify Headers：可自己增加一些浏览器的头部信息
x-forwarded-for：可以修改浏览者的x-forwarded-for，有一些程序根据这个判断IP，这样可以达到隐藏自己的IP
noscript：可以让哪些域名的js能够运行，哪些js不能运行，即能够让只有指定的js运行
Web Developer：开发网站的必须工具，这里面功能比较多，有js、css、cookies、java等的开关以及其他的即能够让特定的运行或者禁止运行。
autoproxy 0.4b2.2013051811：一款比较智能的服务器代理器，能够让指定的网站代理，符合规则的网站用指定的代理服务器
Cookies Manager+：比较好的cookies编辑器，能够删除或者直接编辑某些存在的cookies。
User Agent Switcher：能够直接替换自己浏览器的标头。替换成IE6、IE7、百度蜘蛛等
XSS-Me ：简单的检查自己的网站是否存在xxs的漏洞
SQL Inject-Me：简单的检查自己的网站是否存在sql注入漏洞。

[3] 怎么创建一个ipa How to create an IPA (Xcode 4.3)

来源: 互联网发布时间: 2014-02-18

如何创建一个ipa How to create an IPA (Xcode 4.3)

With the release of Xcode 4.3, Apple has made it even easier to generate an IPA. However, some of these changes have caused some confusion with some users. This tutorial will walk you through the easiest way to generate an IPA as well as some more advanced configurations. We will be using a sample project which will walkthrough creating the project to IPA generation.

NOTE: this tutorial only covers how to configure your project in order to package the application as an IPA. It does not cover how to create or migrate a project with or without 3rd party libraries.

NOTE: You will need an Apple Developer or Enterprise account to prepare an .IPA to be distributed.

Creating the Basic Application

Choose a template for your new project. For this sample application, we will be creating a Single View Application.

Enter your product name, company identifier, and other configuration options. The product name and company identifier will be combined to generate the Bundle Identifier. This will be used later to determine which provisioning profiles can be used when building and sharing the application.

In the file list on the left side of the window, select your project and your target. On the Summary tab, notice the Bundle Identifer has been generated based on the values entered in step 2.

Scroll down and expand the Entitlements section in the Summary tab. In previous versions of Xcode, you were required to create an Entitlements file and create a get-task-allow key. This is no longer necessary. Unless your application requires special permissions surrounding iCloud or Keychain Access, you are not required to create this file. Leave the Enable Entitlements checkbox unchecked.

Go to the Build Settings tab and scroll down to the Code Signing section. For the two default build configurations (Debug and Release), select your Development Provisioning Profile for Debug and your Ad Hoc Provisioning Profile for Release. Leave Code Signing Entitlements blank.

In the dropdown in the top left, select Edit Scheme. You will notice that the default build configurations have already been configured based on the build action being performed. If you are performing a Run action (Product -> Run) to test your application on the iOS Simulator or on your device, your app will be built using the Debug configuration, which in turn signs your app with the Development Provisioning Profile. If you are performing an Archive action (Product -> Archive), your app will be built with the Release configuration, which in turn signs your app with your Distribution Provisioning Profile (either Ad Hoc or App Store).

Generate the IPA

The easiest way to generate an IPA, which can be uploaded to TestFlight, is to archive your applications and share it from the Xcode Organizer.

Change the build target from iPad/iPhone Simulator to iOS Device.

Under the Product menu, select Archive. This will build your application and code sign it using the Distribution (Ad Hoc or App Store) profile setup in step 5 of the “Creating the Basic Application” section. Once the build has completed the Organizer window will appear. If it does not, open it using CMD-Shift–2 or Window -> Organizer. If you see a message popup saying “codesign wants to sign using key ”privateKey“ in your keychain.”, select Allow or Always Allow.

Go to the Archives tab in Organizer and select your application, if it was not automatically selected, and choose the archive you wish to share.

Click the Distribute button. In the next window select “Save for Enterprise or Ad-Hoc Deployment”, and click Next.

In the Code Signing Identity drop down, select the same Distribution Provisioning Profile specified in the Release configuration from step 5 of the “Creating the Basic Application” section, and click Next. NOTE: When generating an IPA for distribution on TestFlight, you should always use an Ad Hoc Distribution Provisioning Profile for both the Archive and Distribute options.

Select where you would like to save your IPA and upload to TestFlight.

Specifying Entitlements

Entitlements allow you to specify specific capabilities or security permissions for your application, such as configuring iCloud. Every application has a default set of values for certain entitlements. By enabling entitlements you are overwriting those default values. In previous versions of Xcode, the most common entitlement set was setting get-task-allow to false. This caused an enormous amount of confusion. In Xcode 4.3 this entitlement is automatically set based on whether the app was built using a Development or Distribution Provisioning Profile. To setup specific entitlements for your application:

Create your application using the same basic setups in the “Creating the Basic Application” section.

Go to the Summary tab for your Target. Check the Enable Entitlements checkbox. This will create a .entitlements file and add it to your project.

You can setup specific iCloud entitlements and Keychain Access Groups for your application as needed.

For more information on specific entitlements, check out the Entitlements documentation on Apple’s developer website. NOTE: if you will be enabling iCloud for your application, you must enable iCloud for your Application ID on the developer portal.

Commonly Asked Questions

Q: Why must I use the same provisioning profile when archiving and generating my IPA?
A: When your application is compiled, information from the provisioning profile used to codesign your application is embedded in the application executable. When you generate your IPA, your application is codesigned again and the provisioning profile used to codesign is added to the IPA as the embedded.mobileprovision file. If there is a mismatch in certain pieces of information between the profile info in the executable and the profile info in the embedded.mobileprovision, this can cause the install to fail.