아이폰 사용자라면 반드시 알아야할 아이폰 단축키 12선

 

1) 전원버튼과 홈버튼을 10초 이상 누르면 공장출고상태로 초기화 됩니다.

2) 프로그램 다운시 홈버튼을 6초이상 누르면 프로그램을 강제 종료합니다.

3) 메모나 메세지 등의 문서 작성시 아이폰을 흔들면 실행취소 버튼이 나옵니다.

4) 웹서핑시 .com 버튼을 누르고 있으면 .co.kr 이나 .net 등의 도메인을 선택할 수 있습니다.

5) 화면이 잠겨있는 상태에서 홈버튼을 두번 누르면 iPod가 실행되며 음악을 재생할 수 있습니다.

6) 화면이 잠겨있는 상태에서 홈버튼을 길게 누르면 음성 제어 화면으로 변환됩니다.


7) 음악 청취 중 아이폰을 흔들면 랜덤으로 다른 음악이 재생됩니다.

8) 음악 청취 중 이어폰을 뽑으면 음악이 일시 정지 됩니다.

9) 문자 입력시 글자 부분을 누르고 있으면 돋보기가 나와 커셔를 쉽게 옮길 수 있습니다.


10) 문자 입력시 $ 버튼을 길게 누르고 있으면 다양한 부호를 입력할 수 있습니다.

11) 웹페이지에서 링크를 지속적으로 누르고 있으면 새창으로 열립니다.

12) 전화 수신시 볼륨키를 한번 누르면 무음모드(진동모드아님)로 전환됩니다.

신고

'Programming > Phone' 카테고리의 다른 글

iPhone 4G 소개 동영상 (아이폰 4세대)  (0) 2010.06.08
iPhone Durex baby  (0) 2010.06.04
아이폰 Tip 단축키 모음  (0) 2010.01.14
[아이폰] iPhone SDK Tutorial in a UIImageView Part 1  (1) 2010.01.06
[아이폰] X Code 개발 강좌 동영상  (0) 2010.01.06
Object-C 입문서  (0) 2010.01.04
by Hazard 2010.01.14 00:36
신고

'Programming > Phone' 카테고리의 다른 글

iPhone Durex baby  (0) 2010.06.04
아이폰 Tip 단축키 모음  (0) 2010.01.14
[아이폰] iPhone SDK Tutorial in a UIImageView Part 1  (1) 2010.01.06
[아이폰] X Code 개발 강좌 동영상  (0) 2010.01.06
Object-C 입문서  (0) 2010.01.04
아이폰 SDK 튜토리얼 링크모음  (0) 2010.01.03
by Hazard 2010.01.06 19:33
신고

'Programming > Phone' 카테고리의 다른 글

아이폰 Tip 단축키 모음  (0) 2010.01.14
[아이폰] iPhone SDK Tutorial in a UIImageView Part 1  (1) 2010.01.06
[아이폰] X Code 개발 강좌 동영상  (0) 2010.01.06
Object-C 입문서  (0) 2010.01.04
아이폰 SDK 튜토리얼 링크모음  (0) 2010.01.03
Cocoa 3.1 tutorial  (0) 2010.01.03
by Hazard 2010.01.06 14:19
아이폰으로 개발하려고할때 꼭 한번은 보고 넘어가야하는 Object-C의 입문서 입니다

http://iaudien.googlecode.com/files/ObjC.pdf


신고

'Programming > Phone' 카테고리의 다른 글

아이폰 Tip 단축키 모음  (0) 2010.01.14
[아이폰] iPhone SDK Tutorial in a UIImageView Part 1  (1) 2010.01.06
[아이폰] X Code 개발 강좌 동영상  (0) 2010.01.06
Object-C 입문서  (0) 2010.01.04
아이폰 SDK 튜토리얼 링크모음  (0) 2010.01.03
Cocoa 3.1 tutorial  (0) 2010.01.03
by Hazard 2010.01.04 09:26
http://code.google.com/p/iaudien/downloads/list
좋은 자료 많음 ...
신고

'Programming > Phone' 카테고리의 다른 글

아이폰 Tip 단축키 모음  (0) 2010.01.14
[아이폰] iPhone SDK Tutorial in a UIImageView Part 1  (1) 2010.01.06
[아이폰] X Code 개발 강좌 동영상  (0) 2010.01.06
Object-C 입문서  (0) 2010.01.04
아이폰 SDK 튜토리얼 링크모음  (0) 2010.01.03
Cocoa 3.1 tutorial  (0) 2010.01.03
by Hazard 2010.01.03 10:54
자 이제 코코아 프로그래밍 시작해봅시다.
http://cocoadevcentral.com/d/learn_cocoa/
신고

'Programming > Phone' 카테고리의 다른 글

아이폰 Tip 단축키 모음  (0) 2010.01.14
[아이폰] iPhone SDK Tutorial in a UIImageView Part 1  (1) 2010.01.06
[아이폰] X Code 개발 강좌 동영상  (0) 2010.01.06
Object-C 입문서  (0) 2010.01.04
아이폰 SDK 튜토리얼 링크모음  (0) 2010.01.03
Cocoa 3.1 tutorial  (0) 2010.01.03
by Hazard 2010.01.03 10:10
http://www.youtube.com/watch?v=v_UyVmITiYQ&feature=player_embedded
신고

'IT NEWS' 카테고리의 다른 글

Google Wave 소개 동영상  (0) 2009.10.12
최신모델 PSP  (0) 2009.01.28
북미 규격  (0) 2009.01.13
ISO paper Size 2  (0) 2009.01.13
ISO paper size  (0) 2009.01.13
Canon EOS 400D / Digital Rebel XTi overview  (0) 2009.01.12
by Hazard 2009.10.12 09:36
신고

'Programming' 카테고리의 다른 글

Star UML  (0) 2009.06.15
by Hazard 2009.06.15 19:33
When I read this article, I was so impressed.
About bad code... ...

------------------------------------------
 I know of one company that, in the late 80s, wrote a killer app.
It was very popular, and lots of professionals bought and used it.
But then the release cycles began to stretch.
Bugs were not repaired from one release to the next.
Load times grew and crashes increased.
I remember the day I shut the product down in frustration and never used it again.
The company went out of business a short time after that.

 Two decades later I met one of the early employees of that company and asked him what had happened.
The answer confirmed my fears.
They had rushed the product to market and had made a huge mess in the code.
As they added more and more features, the code got worse and worse until they simply could not manage it any longer.
It was the bad code that brought the company down.

please ... be careful... :)

-hazard-
신고
by Hazard 2009.04.15 16:19

Component Life Cycle

In general, the Component architecture in 2.0 will "just work." It's been designed to handle most of the management of components transparently to the end developer. However, there will come a time when something needs to be customized, or a Component needs to be extended. That's when a thorough understanding of the Component life cycle will become quite helpful. Following are the most important stages in the life cycle of every class based on Component:

Initialization
  1. The config object is applied
    Classes that extend Component do not need to (and usually should not) provide a separate constructor. Component's constructor will not only apply any config passed into its subclasses, it also provides all of the following steps.
  2. The base Component events are created
    These are events that can be fired by any Component, and they are enable, disable, beforeshow, show, beforehide, hide, beforerender, render, beforedestroy, destroy (see the Component API docs for complete details).
  3. The component is registered in ComponentMgr
    As such it will always be available via Ext.getCmp.
  4. The initComponent method is called
    This is the most important initialization step for subclasses, as this is a template method intended to be implemented by each subclass to provide any needed constructor logic. The class being created is called first, and each class in the hierarchy back up to Component is expected to call superclass.initComponent. This method makes it easy to implement and, if needed, override the constructor logic at any step in the hierarchy.
  5. Plugins are loaded (if applicable)
    If this Component has any plugins specified in the config, they will be initialized at this time.
  6. State is initialized (if applicable)
    If the Component is state-aware, its state will be reloaded if available.
  7. The component is rendered (if applicable)
    The component is rendered immediately if either renderTo or applyTo is provided in the config, otherwise rendering is deferred until the Component is explicitly displayed in code or is told to render by its container.
Rendering
  1. The beforerender event is fired
    This is a cancelable event, giving any handler the ability to prevent the Component from rendering if needed.
  2. The container is set
    If no container is specified, the parent node of the Component's underlying DOM element is set as the container.
  3. The onRender method is called
    This is the most important rendering step for subclasses, as this is a template method intended to be implemented by each subclass to provide the needed rendering logic. The class being created is called first, and each class in the hierarchy back up to Component is expected to call superclass.onRender. This method makes it easy to implement and, if needed, override the rendering logic at any step in the hierarchy.
  4. The Component is "unhidden"
    By default, many components are hidden using special CSS classes like "x-hidden". If the autoShow config value is true, any "hide" classes are removed from the component at this time.
  5. Custom class and/or style applied
    All Component subclasses support the special config properties of cls and style which are a custom, user-defined CSS class and rule respectively that will be applied to the DOM element underlying this Component. Specifying the cls value is the preferred method for visually customizing a Component and its constituent parts. Since the class will get applied to the topmost wrapper element of the Component's markup, any sub-elements of the Component can be adjusted using standard CSS inheritance rules.
  6. The render event is fired
    This is a notification that the Component has been successfully rendered at this point. You can safely assume that its DOM elements are now available to your code if needed. If you attempt to access a Component prior to rendering, it won't be available and you'll get an error.
  7. The afterRender method is called
    This is another template method for subclasses that can be implemented or overridden to provide any special post-rendering logic that may be needed. Each subclass is expected to call superclass.afterRender.
  8. The Component is hidden and/or disabled (if applicable)
    The hidden and disabled config values are applied at this point.
  9. Any state-specific events are initialized (if applicable)
    State-aware Components can declare special events that are specific to loading and saving state. If supplied, any such events will be added.
Destruction
  1. The beforedestroy event is fired
    This is a cancelable event, giving any handler the ability to prevent the Component from being destroyed if needed.
  2. The beforeDestroy method is called
    This is another template method that can be implemented or overridden to provide any special pre-destruction logic that may be needed. Each subclass is expected to call superclass.beforeDestroy.
  3. Element and its listeners are removed
    If the Component has been rendered, its underlying Element's event listeners are removed and the Element itself is then removed from the DOM.
  4. The onDestroy method is called
    This is another template method that can be implemented or overridden to provide any special post-destruction logic that may be needed. Each subclass is expected to call superclass.onDestroy. Note that the Container class (and any Container subclasses) provides a default implementation of onDestroy that automatically loops through its items collection and calls destroy on each child Component recursively.
  5. Component is unregistered from ComponentMgr
    It will no longer be available via Ext.getCmp.
  6. The destroy event is fired
    This is simply a notification that the Component has been successfully destroyed at this point and is no longer available in the DOM.
  7. Event listeners on the Component are removed
    The Component itself can have event listeners separately from its underlying Element. If any exist, they are removed.
신고

'Programming > ExtJS' 카테고리의 다른 글

Extjs Life Cycle  (0) 2009.03.16
ExtJS Link  (0) 2009.01.28
ExtJs and Flash  (0) 2009.01.28
by Hazard 2009.03.16 08:46
| 1 2 3 4 5 6 |