Copyright &
. All Rights Reserved. 如果侵犯您的隐私,请来信通知,!E-Mail:当前位置：&&&&&&&&&
iPhone8什么时候上市 iphone8尺寸大小、外观、新功能
来源：深圳攻略&|& 18:07&编辑：邱川芷
导语：网上曝光了iPhone 8概念机，首次弃用金属外壳，而引入3D玻璃设计，并引入加工成本更高的金属中框。iPhone8什么时候上市？传iphone8将巨变。
今天小编要告诉大家一个好消息，还没把肾捐给iPhone7的朋友走运了，虽然iPhone7S还没出，但iPhone8却备受瞩目，今年是iPhone推出的10周年，iPhone8作为苹果十周年的纪念，将采用不同以往的全新设计！
大量的渲染图和曝光都表明，极具纪念意义的iPhone8将要诞生！
那么iphone8什么时候上市呢？
iPhone 8将于明年秋季发布，据称iPhone 8还将首次引入更薄、功耗更低的OLED屏，其由三星供货。iPhone 8将会采用玻璃材质机身。预计2017年秋季9至10月之间 &&iPhone 8 and iPhone 8 Plus
目前iPhone主要分为4.7英寸和5.5英寸两种尺寸，明年iPhone 8将会增加第三种尺寸，即5英寸。至于为何推出5英寸iPhone，消息人士强调，苹果这么选择是为了让那些觉得5.5寸太大用户买单。还有可能iPhone 8plus手机屏幕降提升至5.8英寸。
目前iPhone主要分为4.7英寸和5.5英寸两种尺寸，明年iPhone 8将会增加第三种尺寸，即5英寸。至于为何推出5英寸iPhone，消息人士强调，苹果这么选择是为了让那些觉得5.5寸太大用户买单。还有可能iPhone 8plus手机屏幕降提升至5.8英寸。
据透露，苹果将在iPhone8上进行大刀阔斧的革新，这点是毋庸置疑的，如果改动依旧平平，恐怕十周年产品也只是噱头，伤了大部分果粉的心，让他们失望。新特性可能包括以下几个方面：全玻璃机身设计；无线充电；OLED/AMOLED显示屏；5.8英寸显示屏、A11处理器；英特尔7360LTE调制解调器；iOS 11系统；无Home键设计等。
现在已经传出有10多款原机模型正在测试中，看来苹果公司现在是势在必得，相对于平庸的iPhone7，十周年的iPhone8将会带来这样的惊喜
1.重新回归玻璃后盖+金属中框的设计
这次iPhone8将致敬乔布斯四代不再采用铝质金属背盖，而是改用两面强化玻璃、中间为金属边框的设计，重新回归了玻璃后盖和金属中框的设计，非常有当年 iPhone 4 的感觉。
2.屏幕升级为OLED屏幕
首度采用双曲面OLED屏幕，可以提高屏幕的亮度、画质更加生动，同时也赋予苹果更大的设计空间。除此，采用虚拟按键来代替Home键。
听说可能还有曲面屏版本，不管真假，有点期待还是好的
3.手机面板一体化，摄像头做平
后置摄像头不凸出，可谓突破以往设计，是有强迫症朋友的福利！
还有猜测iPhone8仍为4.7寸单摄像头，iPhone8 Plus则是双摄像头配置，iPhone8 Plus将会对双摄像头进行升级，使两个摄像头将都配备光学防抖音圈马达。
4.双卡双待
随着国产手机在研发、技术积累方面的成果显著，苹果渐渐处于劣势，所以苹果瞄准了我们国产手机的主打功能双卡双待技术。
除了双SIM卡技术之外，苹果还提出了通过监听端口调度等方式降低双卡能耗的新技术方案。
5.支持无线充电
有消息称，与苹果关系密切的配件商Dialog与Energous均已推出新款无线充电组件，苹果也申请了无线电专利，进一步表明iPhone8将支持无线充电功能。
6.防水等级升级到IP68
有消息传出，iPhone8的防水等级可望提升到IP68，能与现在的Galaxy S7持平，在水下5英尺停留30分钟不进水。
最后还有猜测iPhone8为5英寸。
不过看完预测的iphone8，你会买吗？
下一篇：没有了
的相关阅读:
窗花有话说
网友评论仅供其表达个人看法，并不表明深窗立场。
深窗公众平台iOS8所有iPhone屏幕尺寸及设计 - CSDN博客
iOS8所有iPhone屏幕尺寸及设计
/project.php?id=30294
先来张直图：
These guidelines describe how to design apps that follow the official HIG for iOS by Apple, not what you can do with custom controls. Sometimes it makes sense to break the rules. The purpose of this document is to guide you, not to provide solutions for complex
and unique design problems.
This unofficial documentation will be updated and extended regularly. Last update: November 11, 2014.
Resolutions and Display Specifications
Portrait (px)
Landscape (px)
iPhone 6+
1080 x 1920
750 x 1334
1334 x 750
iPhone 55, 5S, 5C
640 x 1136
1136 x 640
iPhone 44, 4S
iPhone1st, 2nd & 3rd Generation
iPad Air / Retina iPad1st & 2nd Generation / 3rd & 4th
1536 x 2048
2048 x 1536
iPad Mini2nd & 3rd Generation
1536 x 2048
2048 x 1536
iPadMini, 1st & 2nd Generation
768 x 1024
1024 x 768
Difference between Points and Pixels
Pixels are the smallest physical element that we can control on a digital display. The more pixels can be fitted into a specific screen size, the higher the PPI (pixels-per-inch), and the clearer the rendered content becomes.
Points are a resolution-independent measurement. Depending on the screens pixel density, a point can contain multiple pixels (e.g., 1 pt contains 2 x 2 pixels on a regular retina display).
When you are designing for various display types, you should think in points, but design in pixels. This means you will still need to export all your assets in 3 different resolutions, no matter in which resolution you are designing your app.
As long as it is not stated otherwise (by appending ,,px“ to a value), this guide always refers to points when it comes to specific dimensions. If you need the value in pixels, just multiply by 2 for Retina screens or by 3 for Retina HD screens.
Asset Resolution
Display Size
iPhone 6+
iPhone 55, 5S, 5C
iPhone 44, 4S
iPhone1st, 2nd & 3rd Generation
iPad Air / Retina iPad1st & 2nd Generation/ 3rd & 4th
iPad Mini2nd & 3rd Generation
iPad Mini1st Generation
iPad1st & 2nd Generation
Downsampling on iPhone 6+
Rendered pixels and physical pixels are equal on all iOS devices, with one exception: the Retina HD screen of the iPhone 6 Plus. Because its screen has a lower pixel resolution than what would be a natural @3x resolution, the rendered content is automatically
resized to approximately 87% of the original size (from 2208 x 1242 pixels to fit the display resolution of 1920 x 1080 pixels).
difference between displays of iPhone 5S, 6 and 6+. More in-depth information&.
AppStore Icon
iPhone 6+
180x180 px
120x120 px
iPhone6, 5S, 5, 5C, 4S, 4
120x120 px
Old iPhones1st, 2nd, 3rd Generation
Retina iPadsMini 2 & 3, Air, 3 & 4
152x152 px
Old iPads1, 2, Mini 1
Automatically applied effects
App icons assets are generally added to the application package as plain, squared PNG files in various dimensions. When rendered on a device, iOS applies various effects to app icons.
ROUNDED CORNERS
The old simple radii values for rounded corners are gone. Since iOS 7, app icons have been using the shape of a superellipse. Since Apple did not release an official template of the shape, you will have to use one of the&&out there that replicate the shape in more or less accurate ways.
The rounded corners should not be included in the final exported assets, but you might need them in your design process if you want to add effects, such as a stroke or shadows, that are aligned to the corner of the icon.
If you are masking your icon asset with the superellipse shape because you want to apply effects aligned to the corners, make sure not to use any transparency for the area outside the mask. Transparency is not supported at all for app icons and instead is rendered
as plain black. If your mask is not 100% accurate, users will see small black fragments on the rounded edges. It’s recommend to set the background of the canvas to be the same as the app icon background.
BORDER STROKE (IN SOME SITUATIONS)
If the app icon you are using has a white background, a 1 pixel gray border stroke will be applied to make it easier to recognize the edges of the icon. This is only done in the settings app (if your application is listed there) and the AppStore.
LEGACY EFFECTS (IOS 6 AND PREVIOUS VERSIONS)
On older iOS versions, these effects are applied automatically: rounded corners (not the same shape as iOS 7+ icons are using), drop shadows on the home screen and a gloss effect that can be disabled.
Grid system
Apple developed a golden ratio grid system that can be used to size and align elements on your icon correctly. Nevertheless, even Apple designers are not following the grid system very strictly with the native apps’ icons. Feel free to break the rules if your
icon simply works better without aligning all elements strictly to the grid.
Typography
The default system font on all iOS versions is Helvetica Neue. Since iOS 7, Apple has been using a slightly modified version of the font, but using the original Helvetica Neue for your design process is totally fine. In addition to the default font, many alternative
font faces are available to use. You can find a complete list of pre-installed typefaces&.
Custom Fonts
Technically, any True Type Font (.ttf) can be used within an iOS app, but be careful about licenses. It should be safe to use fonts that are completely free for commercial usage. App licenses for commercial fonts are rarely available, and if they are, securing
them can turn out to be somewhat expensive.&&currently offers the biggest collection of fonts that can be licensed for mobile app usage.
Color Palette
Since iOS 7, Apple has been using a vibrant color palette for the interface of the OS and pre-installed apps. While you can use the default iOS color palette listed above, you can also (and probably should, if you want to stand out) use your own colors.
Iconography
In iOS apps, icons have always been a great way to support text labels with a visual relationship to the performed action or to replace text completely (often for very common actions such as ,,New“, ,,Delete“, etc.). Usually, we are dealing with icons that are
part of the Navigation Bar, Tool Bar or Tab Bar.
Bar Button Icons
Icons used in bars should always have two different states: the default state in outlined style with a stroke width of 1 or 1.5pt and the active state with a solid color fill.
You should never include any additional effects such as a drop-shadow or inner shadows on button icons because these are relicts from previous iOS versions (before the iOS 7 redesign). Button icons should be drawn in one solid color on a transparent background—the
shape of the icon is used as a mask, and the color will be applied programmatically.
Activity View Icons
Icons in the Activity View (also known as Share Popover) used to be designed in outline style, but since iOS 8, Apple has reverted back to solid fill icons on a plain white background.
Commonly used design elements
iOS offers a great collection of ready-to-use views and controls that allow app developers to quickly build interfaces. Some elements can be customized to a certain level, but other cannot and probably also should not be. When designing an application for iOS,
you should know your set of tools and stick to them whenever possible. However, in some cases, it might be worthwhile to build a custom control because you need a more custom look or want to change the functionality of an already existing control (danger zone).
Almost anything is possible,and sometimes it makes sense to break the rules, but always think twice before doing so.
Status Bar
The Status Bar contains basic system information such as the current carrier, time, battery status and more. It’s visually connected to the Navigation Bar and makes use of the same background fill. To match the style of your app and guarantee readability, the
content of the status bar comes in two different styles: dark (black) and light (white).
It is possible to hide the Status Bar, but think twice before doing so. For example, users might be interested in knowing if they are connected to a WiFi network when the app regularly downloads web content or if Bluetooth is enabled when the app requires a
Bluetooth link to third-party hardware. A valid reason to hide the Status Bar is when you want to remove all distractions from a single element, for example, when displaying full screen content such as an image gallery.
The navigation bar contains the controls for navigating through the applications views and optionally to manage the content of the current view. It will always appear at the top of the screen, right below the status bar. By default, the background is slightly
translucent and blurs content underneath the bar. The background fill of the bar can be set to a solid color, a gradient or a custom bitmap-pattern.
Navigation Bar on iPhone 6 in portrait mode.
Navigation Bar on iPhone 4S in landscape mode. The height
of the bar is reduced by 12pt, except on iPads. It's also a common practice to hide the status bar in landscape mode.
The elements should always following a specific alignment pattern.
Back button should always be aligned to the left side.Title of the current view should always be centered in the bar.Action buttons should always be aligned to the right side. If possible, there should never be more than one primary action to avoid missed clicks and to maintain simplicity.
A toolbar contains a set of actions for managing or manipulating the content of the current view. On the iPhone, it will always appear aligned at the bottom edge of the screen, while on the iPad, it can also be displayed aligned at the top of the screen.
Similarly to the navigation bar, the background fill of toolbars can be modified, is translucent and blurs the underlaying content by default.
Toolbars should be used when a specific view requires more than three primary actions that would hardly fit or would look messy in the navigation bar.
Search bars come in two different styles by default: prominent and minimal. Both versions do have the same functionality.
As long as no text was entered by the user, a placeholder text is shown inside the bar, and, optionally, a bookmarks icon that can be used to access recent or saved searches.Once a search term is entered, the placeholder disappears, and a clear button to delete the entered value appears on the right edge.
Search bars can make use of a prompt — a short sentence to introduce the functionality in the context of the search. For example, ,,Enter a city, zip code or airport.“
Prominent search bar style, without and with a prompt.
Minimal search bar style.
To provide even more control over a search query, it is possible to chain the search Bar with a scope bar. The scope bar will use the same style as the search bar and might be useful when there are clearly defined categories for the search results. For example,
in a music app, the search results could be filtered again by interpreters, albums or songs.
The tab bar is used to allow the user to quickly navigate through the separate views of an application, and it should only be used for this purpose. It always appears at the bottom edge of the screen. By default, its slightly translucent and uses the same system
blur for underlaying content as the navigation bar.
A tab bar can only contain a fixed maximum number of tabs. Once there are more tabs than the maximum count, the last tab displayed will be replaced by a ,,More-tab“ that will lead to a list of hidden tabs, with an option to re-order the displayed tabs.
While the maximum amount of tabs displayed is five on iPhones, it’s possible to display up to seven tabs on the iPad while avoiding a more-tab.
To notify users about new information on a view, it sometimes makes sense to apply a badge count to a tab bar button. If a view is temporarily disabled, the related tab button should not
instead, it should be faded out to visually communicate
the disabled state.
Table View
Table views are used to display small to large amounts of list style information in a single or multiple columns and with the option to divide several rows into separate sections or to group them.
There are two basic table view types that should be used, depending on the type of data you are presenting.
A plain table contains a number of rows that can have a header on the top and a footer after the last row. It’s possible to display a vertical navigation on the right edge of the screen to navigate through the table, which makes sense when presenting a big
data set that could be sorted in some way (e.g., alphabetically descending).
A grouped table allows you to organize rows in groups. Each group can have a header (best used to describe the context for the group) as well as a footer (good for help text, etc.). A grouped table needs to contain at least one group, and each group needs to
contain at least one row.
For both table view types, a few styles are available to present the data in a way that allows users to easily scan, read and probably modify it.
A table row in default style has an optional image aligned on the left and a title.
WITH SUBTITLE
The subtitle table style enables a small subtitle text underneath the row title. It is useful for further explanations or short descriptions.
WITH VALUE
The value table style allows you to display a specific value that is related to the row title. Similar to the default style, each row can have an image and a title that are both aligned to the left. The title is followed by the right aligned label for the value,
which is usually displayed in a slightly more subtle text color than the title.
Modals, Popovers and Alerts
iOS provides various styles of temporary views that can be used to display, edit and manipulate data in a way that fits best in a given situation. While each temporary view exists for a very specific purpose and each one looks different, all temporary views
still have one thing in common: When displayed, it’s the highest index layer on the current view (they appear on top of everything else), and content underneath is overlayed by a translucent black background.
ACTIVITY VIEW
An activity view is used to perform specific tasks. These tasks can be default system tasks such as share content via the available options, or they can be completely custom actions. When designing icons for custom task buttons, you should follow the same guidelines
as for the active state of bar button icons — solid fill, no effects, on a transparent background.
Action Sheets are used to perform one single action from a list of available actions and to force the user of an app to confirm an action or cancel it.
In portrait mode (and on small landscape screen resolutions), actions are always displayed as a list of buttons sliding in and staying at the bottom edge of the screen. In this case, an action sheet should always have a cancel button to close the view and not
perform any of the listed actions.
When there is enough space available (e.g., on iPad screens), action sheets visually transform into&. A button to close the view is not required anymore
because tapping a target anywhere outside the popover will close it automatically.
The purpose of alerts is to inform the user about critical information and optionally to force the user to make a decision about some action.
An alert view does always contain a title text, which should not be longer than one line and one (for pure informational alerts, e.g., ,,OK“) or two (for alerts that require a decision, e.g., ,,Send“ and ,,Cancel“) buttons.
Also, you can add a message text, if needed, as well as up to two text input fields, one of which can be a masked input field, which is appropriate for sensitive information like passwords or PINs.
The Edit Menu allows users to perform actions such as Copy, Paste, Cut, etc., when an element is selected (text, images, others). While it is possible to control which operations the user can choose from, the visual appearance of edit menus is set and not configurable
unless you build your own completely custom edit menu.
Popovers are useful when a specific action requires multiple user inputs before proceeding. A good example is adding an item, which has a few attributes that need to be set before the item can be created.
In a horizontal environment, popovers reveal underneath the related control (such as a button) with an arrow pointing to that control while opened. The background of a popover uses a slightly reduced opacity and blurs the content underneath, just as many other
UI elements have done since iOS 7.
A popover is a powerful temporary view that can contain various objects such as its own navigation bar, table views, maps or web views. When a popover grows in size due to the number of contained elements and reaches the bottom edge of the viewport, it is possible
to scroll within the popover.
Modals are a useful view for tasks that require multiple commands or inputs by the user. They appear on top of everything else, and, while open, block interaction with any other interactive elements underneath.
The typical modal usually provides:
a title a button to close the modal without saving or performia button to save or submit any andvarious elements for user input in the modal body.
There are three different modal styles available:
Full screen: covers the entire screen.Page sheet: In portrait mode, the modal covers the underlaying content only partially, leaving a small portion of the parent view visible underneath the translucent black background. In landscape mode, the page
sheet modal acts just like a full screen modal.Form sheet: In portrait mode, the modal appears in the center of the screen, keeping the surrounding content of the parent view visible underneath the translucent black background. The position of the modal
adjusts automatically when a keyboard needs to be displayed. In landscape mode, the page sheet modal acts just like a full screen modal.
iOS provides a wide range of controls for basically any required input type you can think of. Listed below you will find the most important (commonly used), but for a full list of the available controls, you should look at the&.
Probably the most used control overall is the good old button. Since iOS 7, the default button design hasn't really looked like a button anymore, but rather more like a plain text link. The button control is highly customizable and allows you to style everything
from text style, drop shadows and color to an icon that is either prepended or centered if there is no text label, as well as fully custom backgrounds.
Keep in mind that a button can have several states, which should be communicated with visual language: default, highlighted, selected and disabled.
Pickers are used to select one value from a list of available values. The web equivalent would be a select box (which the picker control is also used for when touching a select in Safari). An extended version of picker is the datepicker, which allows the user
to scroll through a list of dates and times and select values for (configurable) day, month and time.
Left: datepicker displayed inside a table view, right: picker
as keyboard.
Except for the background color, it is not possible to change the visual style or size (same as keyboard) of a picker control. Most often, they appear at the bottom of the screens, where keyboards appear as well, but it is possible to use them in other positions.
SEGMENT CONTROLS
A segment control contains a set of segments (at least two) that can be used for things like filtering content or to create tabs for clearly categorized content types.
Segment control without and with icons.
Each segment can contain a text label or an image (icon), but never both. In addition, using a mixed set of segment types (text and images) in one segment control is not really recommended. The width of one segment changes automatically based on the number
of segments (two segments: 50% of total control width, 5 segments: 20% of total control width).
The slider control allows the user to choose one specific value from a range of allowed values. Since choosing a value works pretty smoothly and without any steps, sliders are recommended for selecting an estimated, but not exact, value. For example, a slider
would be a good control for setting the sound volume, since the user can hear the difference and can see the difference between loud and very loud, but a text input to set an exact dB value would be impractical.
Slider control without and with descriptive icons.
It is possible to set icons for the minimum and the maximum value, which are displayed on the start and end edge of the slider control, thereby allowing you to visually embrace the purpose of the slider.
Steppers should be used when the user should enter an exact value from a limited range of possible values (e.g., 1-10). A stepper always contains two segmented buttons, one for lowering and one for raising the current value.
Visually, the stepper control is highly customizable:
you can use your own iconswhen maintaining the native iOS look, you can customize the color of borders, background and icons by using a tint color, which automatically sets the color for ea andif you want to go further, you can use completely custom background images for the stepper buttons as well as for the separator.
A switch allows the user to quickly toggle between two possible states: on and off. It’s the checkbox for iOS apps. It is possible to customize the color for the on and off states, but the appearance of the toggle button and size of the switch are set and cannot
be changed.
There are various keyboard types available to provide the best possible keyboard for a specific text input. While it is possible to build your own completely custom keyboard, default keyboards cannot be customized in style or size.
Further Reading and Resources
These guidelines only provide basic information to get you started with iOS design. Once you dig deeper, you might be interested in more details. These articles and resources should help you.
==================================================================================================
教你iOS APP设计一稿支持iPhone5/iPhone6/Plus
app开发中设备尺寸适配问题，过去只属于Android头疼事儿，很多设计师选择性地忽视android适配问题，只出一套iOS平台设计稿。随着苹果发布新尺寸的大屏iPhone 6，iOS平台尺寸适配问题终于来了，移动设计全面进入“杂屏”时代。
加上Android生态中纷繁复杂的各种奇葩尺寸，现在APP设计开发必须考虑适配大、中、小三种屏幕。所以如何做到交付一套设计稿解决适配大中小三屏的问题？设计和开发之间采用什么协作模式？一个基本思路是：
1、选择一种尺寸作为设计和开发基准；
2、定义一套适配规则，自动适配剩下两种尺寸；
3、特殊适配效果给出设计效果。
第一步，视觉设计阶段，设计师按宽度750px（iPhone 6）做设计稿，除图片外所有设计元素用矢量路径来做。设计定稿后在750px的设计稿上做标注，输出标注图。同时等比放大1.5倍生成宽度1125px的设计稿，在1125px的稿子里切图。
第二步，输出两个交付物给开发工程师：一个是程序用到的@3x切图资源，另一个是宽度750px的设计标注图。
第三步，开发工程师拿到750px标注图和@3x切图资源，完成iPhone 6（375pt）的界面开发。此阶段不能用固定宽度的方式开发界面，得用自动布局（auto layout），方便后续适配到其它尺寸。
第四步，适配调试阶段，基于iPhone 6的界面效果，分别向上向下调试iPhone 6 plus（414pt）和iPhone 5S及以下（320pt）的界面效果。由此完成大中小三屏适配。
为什么选择iPhone 6作为基准尺寸？
当面对大中小三种屏幕需要适配的时候，很容易想到先做好一种屏幕，再去适配剩下两种屏幕。第一个决定是到底以哪种屏幕作为设计和开发的基准尺寸。我们选择中间尺寸的iPhone 6（750px/375pt）作为基准，基于几个原因：
1、从中间尺寸向上和向下适配的时候界面调整的幅度最小。375pt下的设计效果适配到414pt和320pt偏差不会太大。假设以414pt为基准做出很优雅的设计，到320pt可能元素之间比例就不是那么回事了，比如图片和文字之间视觉比例可能失调。
2、iPhone 6 plus有两种显示模式，标准模式分辨率为，放大模式分辨率为（即iPhone 6的1.5倍）。可见官方系统里iPhone 6和iPhone 6 plus分辨率之间就存在1.5倍的倍率关系。很多情况下这两种尺寸可以用1.5倍直接等比适配。
3、这个奇葩的数值是苹果官方都不愿意公开宣传的一个分辨率，不便于记忆和计算栅格。640×1136虽然是广泛应用的一个分辨率，但是大屏时代依然以小尺寸为设计基准显然不合时宜，设计师会停留在小屏的视角做设计。
所以，iPhone6的750×1334是最适合基准尺寸。
只交付一套设计稿，默认用什么规则来适配？
前文提到适配策略是先选择iPhone 6作为基准设计尺寸，然后通过一套适配规则自动适配到另外两种尺寸。这套适配规则总结起来就一句话：文字流式，控件弹性，图片等比缩放。
本文已收录于以下专栏：
相关文章推荐
关注公众号
在公众号里回复“”秘密“”两个字
http://task.csdn.net/m/task/home?task_id=398 领取奖励
提示：根据公众号里的自动回复，完成...
观察者模式在实际项目中使用的也是非常频繁的，它最常用的地方是GUI系统、订阅——发布系统等。因为这个模式的一个重要作用就是解耦，使得它们之间的依赖性更小，甚至做到毫无依赖。以GUI系统来说，应用的UI...
LinearLayout xmlns:android=&/apk/res/android&
xmlns:app=&http://schema...
JavaEE 6及以上版本的web.xml问题？MyEclipse JavaEE 6版本开始web.xml突然消失不见？没这回事，只是不太必须而已，有需要的项目可以自行进行添加或在创建项目的时候点击n...
注：本文的高斯模糊只能显示，如果想要保存模糊后的图片，请参考另一篇文章：http://blog.csdn.net/fan7983377/article/details/
初代iPhone
2007年，初代iPhone发布，屏幕的宽高是 320 x 480 像素。下文也是按照宽度，高度的顺序排列。这个分辨率一直到iPhone 3GS也保持不变。
那时编写iOS的App...
他的最新文章
讲师：宋宝华
讲师：何宇健
您举报文章：
举报原因：
原文地址：
原因补充：
(最多只允许输入30个字)}