반응형

한 가지 뜻을 세우고 그 길로 가라.

잘못도 있으리라.

실패도 있으리라.

그러나 다시 일어나서 앞으로 나아가라.

반드시 빛이 그대를 맞이 할 것이다.

- 칸트 -

반응형
반응형

http://jqueryui.com/slider/#side-scroll

 

jQuery UI

 

jQuery UI Demos


jQuery UI offers a combination of interaction, effects, widgets, utilities, and themes designed to work well together or on their own. Play with the demos, view the source,build a theme, read the API documentation and start using jQuery UI today.

Interactions

Interactions add basic mouse-based behaviors to any element. You can create sortable lists, resizable elements, drag & drop behaviors and more with just a few lines or code. Interactions also make great building blocks for more complex widgets and applications.

Widgets

Widgets are full-featured UI controls that bring the richness of desktop applications to the Web. All widgets provide a solid core with plenty of extension points for customizing behavior, as well as full theming support.

Effects

Effects add support for animating colors and class transitions, as well as providing several additional easings. In addition, a full suite of custom effects are available for use when showing and hiding elements or just to add some visual appeal.

Utilities

Utilities used by jQuery UI to build interactions and widgets.

반응형
반응형
모든 용기는 문턱과 같다.
문턱 앞에서 우리는 선택에 직면한다.
아이를 살리기 위해 불이 난 건물 안으로
들어갈지 말지, 결단을 내려야 한다.
"선택의 여지가 없었어요.
그 아이를 구하려면 불타는 건물
안으로 들어가야 했습니다."
내 삶도 이런 받아들임의 연속이었다.


- 마크 네포의《고요함이 들려주는 것들》 중에서 -


* 어머니는
선택의 여지가 없습니다.
아이를 위해서는 물불을 가리지 않습니다.
불타는 건물 안을 맨 몸으로 뛰어듭니다.
자기 삶의 여정에서도 마찬가지입니다.
선택의 여지가 없을 때가 있습니다.
모든 것은 오직 하늘에 맡기고
불구덩이에 몸을 던집니다.

반응형

'생활의 발견 > 아침편지' 카테고리의 다른 글

암을 이기는 법  (0) 2013.03.25
내 마음의 꽃밭  (0) 2013.03.23
어디로 가야 할지 알 수가 없다  (0) 2013.03.21
기꺼이 '깨지는 알'  (0) 2013.03.20
'꿈춤'  (0) 2013.03.19
반응형

일은 결코 힘들고 피곤한 괴로움이 아니다.
부지런히 일하면 오히려 정신이 맑아지고
인격 수양에도 도움이 된다.
어떤 일이든 자기 일을 해 나감이 곧 수행이고(諸業卽修行),
수행을 통해 자아발전을 완성하게 된다.
-이시다 바이간

일이 즐거울 때 인생은 기쁨이고,
일이 의무일 때 인생은 노예가 됩니다.(막심 고리끼)
자기 직분에서 즐거움을 느끼고 보람을 찾는 사람은
틀림없이 성공하게 됩니다.(헨리 포드)
주인처럼 일하면 주인이 됩니다. (정주영)

반응형
반응형

자기 자신이 해낸 것을 즐기는, 그리고 자기 자신이 하고 있는 것을 즐기는 사람은 행복한 사람이다. - 괴테 -

 

반응형
반응형

날씨가 흐리다.

슈슈는 감기때문에 오늘도 결석.

5시 50분에 나와서 6시 5분 입수.

체조 잠깐 하고.

자유형 4

배영 킥 3

배영 4

배영 4

접영 4

접영 6

접영 4

한바퀴 걷고

스타트 자유형 10?

스타트 평영 6

 

출석률이 좋다.

 

반응형

'운동일지 > 수영' 카테고리의 다른 글

2013.03.25 수영일지  (0) 2013.03.25
2013.03.23 수영일지  (0) 2013.03.23
2013.03.21 수영일지  (0) 2013.03.21
2013.03.20  (0) 2013.03.20
2013.03.19 수영일지  (0) 2013.03.19
반응형

최신 에러 페이지 모음

 

http://ui-patterns.com/explore/collections/error-pages

 

 

반응형
반응형
Choosing a mobile development strategy

 

 

Mobile Programming Models

Web
Web applications on mobile devices developed using the web model are accessed using a mobile browser.

A primary advantage of the web model is its multiple platform support, allowing your app to reach the broadest audience of mobile users. The code written using standard web application development languages can deliver a similar end user experience across multiple devices and operating systems. The web model approach also permits your development team to be more agile in addressing and fixing problems. Updates to the mobile application can be made easily over the web as opposed to having to release an update through the App Store for iOS apps and Google’s Market Place for Android apps.

Despite the potential of web technology in the mobile arena, there are limitations. One challenge facing developers is emulating the user interface and experience of a native application within the browser and providing cross browser compatibility. It is worth noting, however, there is a growing ecosystem of third party tools and frameworks such as Dojo Mobile, jQuery Mobile, Zurb Foundation, Less Framework 4, and ResponsiveJS providing developers with solutions to common interface problems. Web apps cannot access all of the device’s hardware and software, such as the address book or the notifications in non-webkit supported browsers. Creating a hybrid application, discussed in the next section, can circumvent these disadvantages.

A web approach is ideal if you are trying to reach the largest audience and not isolate a subset of your user base. The web model is also optimal if development and maintenance costs are paramount. Web development skills are more common than native development skill sets. Many organizations already possess in-house developers with experience in web application development.

Hybrid
Hybrid applications are programmed using the same web technologies as the web model, but are packaged and distributed as native applications. A hybrid application is essentially a web application wrapped in a native shell. Hybrid applications can leverage a Web Developer’s existing skillset and tap into a limited subset of the device’s native hardware. Several popular mobile web application frameworks are PhoneGap, Sencha Touch, and Appcelerator Titanium.

There is a caveat, hybrid applications must still be compiled and deployed through the target platform’s method of distribution. For instance, to distribute your app through the Apple App Store, you would need to build and compile your application using XCode and adhere to Apple’s guidelines and clandestine approval process. To target Android devices, you would further need to compile and distribute your application using Eclipse and the Android SDK then distribute your application in Google’s Market Place. It is worth noting, Adobe’s PhoneGap Build system enables developers to upload their assets (HTML5, CSS, JavaScript) to Adobe’s Cloud service and have their apps compiled using the latest PhoneGap SDK.

A hybrid approach is recommended if your application requires access to native functionality such as the device’s address book, or file system and it is essential for your application to target multiple platforms in addition to long-term maintenance and feature enhancements.

Esri’s ArcGIS API for JavaScript can be used to build hybrid applications. The same workflow for building your application using the web model can be applied to the hybrid model. You would import the compact build of the Esri JS API and any additional libraries (Dojo, jQuery, etc). Cascading style sheets can still be used to apply styles to your application’s user interface. Testing your hybrid application would require running it in a simulator or a device.

Native
Native applications are binary executable programs installed on the device. There is a different SDK for each mobile operating system. Native application development must use a language specific to the platform in which the application is deployed.

Although the native model excels in performance and low-level device hardware access, a critical disadvantage of native development is portability. Code written for one mobile operating system cannot be reused for another mobile operating system. A team would need to learn multiple programming languages, software development kits (Esri offers the iOS, Android, and Windows SDK) and manage several codebases. This makes development and maintenance potentially costly and time consuming.

The native model may be the best approach for your organization if the user interface requirements are strict and the native functionality essential.

Another scenario would be a case where organizations intend to only release their app to a subset of the target audience, and therefore target only a single mobile OS. For example, consider a private internal application only available to employees issued a specific mobile device (i.e. iPhone). This would be an instance where it may not make sense to develop for multiple platforms.

The following table summarizes some of the benefits and limitations of each of the three models and also serves as a decision matrix in helping you chose the most appropriate model for you application.

반응형

+ Recent posts