Dev Story..

http://www.cocos2d-javascript.org/demos/tile-maps

애니메이션 캐쉬를 사용하면 쉽게 구현 가능할 듯.

What’s New?

Sencha Touch 2.1 is our next release of the Sencha mobile framework. This release includes the following key upgrades: significant performance improvements, an advanced list component, enhanced native support through the Sencha Mobile Packager and an integrated charting support.

Improved Performance

In Sencha Touch 2.0 some of our developers experienced nested layout performance issues. Our investigations found that by isolating panels and providing more known layout information to the browser the framework and your application will perform faster. We have included this solution in the Touch 2.1 release. The API impact of the change is minimal, but the performance improvement is dramatic.

Advanced List component with Infinite scrolling

new List component is included with this release. This implementation replaces the old list component and is no longer bound one-to-one between a store and DOM elements. This means that the length of the list will no longer have a bearing on it's scrolling performance. In addition, lists can use components if you specify them with an itemConfig and itemTpl will be converted to an itemConfig dynamically if you specify one. Due to these changes, the DOM structure was altered for lists, and you may need to change some CSS selectors to add appropriate styling for your lists. Typically, you need to change the selector from '.x-list-item' to '.x-list-item > .x-dock-vertical > .x-dock-body' for any padding or margins you may have added. We changed the TouchTweets example with the new implementation; instead of using a component based DataView, it now uses the new List. It’s a good example of using the new List component with dynamic large lists.

Enhanced Native Support through the Sencha Mobile Packager

The Sencha Mobile Packager is included in the the Sencha Cmd, previously known as the SDK tools. In this release, we have enhanced native support. For iOS, you can configure your Sencha Touch apps to use the iOS in-app purchase system and native push notifications. Also, you can open another installed application directly within a Sencha Touch app through an open URL call. In previous releases, the native packager allowed you to deploy the app directly to the iOS simulator. We have now added the capability to directly deploy apps to the iOS devices. For Android, you can configure your app upgrade without version changes using the new versionCode key. And for both iOS and Android, you can now access the native contacts API. The packager config also lets you pass in "raw" data to the iOS info.plist and Android AndroidManifest.xml through the rawConfig key. We also heard your feedback about non-admin access to the native packager, and we have updated the setup so admin accounts aren’t required. Another major enhancement is that we’ve given you the ability to write plug-ins for the Sencha Mobile Packager, so you can extend the packager capabilities to fit your needs.

Sencha Touch Charts

We have extended Sencha Touch Charts support in Sencha Touch 2.1. Please refer to the Sencha Touch Charts article for more exciting news about Sencha Touch Charts.

Availability

Sencha Touch 2.1 is in beta. Please give it a try and let us know if you have any feedback. Watch the Sencha Touch Forum for any release update.

보시다시피 기존에는 리스트 컴포넌트에서 store에 데이터와 dom을 1:1 매핑 시켰기 때문에 데이터가 늘어나면 느려지는 현상이 있었는데 dom은 제한 시키고 재사용함으로써 성능을 향상시킨다고 하네요.

또 터치챠트도 2.1에선 호환되게 만든다고 하는군요..

리스트쪽이 느려서 계속 쓸지 말지 고민했는데 지켜봐야겠네요:)

관련 주소는 여기를 참조.

http://www.sencha.com/blog/whats-coming-in-sencha-touch-2-1?mkt_tok=3RkMMJWWfF9wsRokuazPZKXonjHpfsX87O8pUKazlMI%2F0ER3fOvrPUfGjI4ESsN0dvycMRAVFZl5nR9dFOOdfQ%3D%3D

베타 다운로드는 여기를 참조.

http://www.sencha.com/forum/announcement.php?f=105&a=36

오랜만에 토비 스프링을 다시 보다가 Class.forName(String value)이라는 구문이 눈에 들어왔고..

평소에는 그냥 아 이렇게 쓰는거구나하고 넘겼는데..이게 뭔지 갑자기 궁금해졌다.

그래서 찾아보니..

forName을 하게 되면 해당 클래스를 동적 로드하게 되는데..이 때는 생성자는 실행하지 않고

static 필드 부분만 실행하게 된다.

고로 "com.oracle.jdbc.OracleDriver" 이 클래스 안에는 static { 솰라솰라} 가 있을테고

DriverManager 안에도 static으로 driver 멤버 변수가 선언되어 있을 것이며, OracleDriver가 로드 될 때

DriverManger안에 세팅을 해주는 방식으로 구현이 되어있다. 이제 궁금점이 풀렸군..